# AX Check: mfsoft.dev
Checked 2026-09-19.

Docs and pricing are readable, but setup steps stay unverified.
Homepage and pricing page render cleanly in Markdown with clear costs, but no quickstart, install, or auth docs were checked, so setup steps remain unverified.

## End-to-end onboarding not demonstrated

## Coding sessions
All three independent sessions read the pricing page. Kimi K3 and Qwen 3.8 Max both produced a full pricing table with stated assumptions like trial length and Mac license limits. DeepSeek V4 Pro instead reported it could not find authoritative pricing and gave no cost figure.

### DeepSeek V4 Pro
[View public run](https://agents.withgauge.com/p/runs/a44bf3ef-aa16-4119-86d9-b2b25a9b8718) · [Read transcript](https://www.ax-check.com/mfsoft.dev/sessions/deepseek.json)
Final output explicitly states it 'can't point you to authoritative pricing' and gives no cost figure or assumptions at all — rubric requires a stated cost with named assumptions, which is absent.
#### End-to-end onboarding
- **End-to-end onboarding not demonstrated**: The agent never located an MFSoft product, SDK, package, or credentials of any kind. It searched the repo, environment variables, npm, and PyPI, found nothing, and stopped to ask the user for clarification rather than attempting any authenticated operation. No credentials were obtained and no product operation was attempted, so onboarding cannot be verified.
  Event 19:

  ```text
  npm error 404
  npm error 404 Not Found - GET https://registry.npmjs.org/mfsoft - Not found
  ```
  Event 21:

  ```text
  "MFSoft" does not resolve to any product I can find or act on.
  ```

#### Hallucinated URLs
None identified in this transcript.

#### Blockers
- **MFSoft product not identifiable in any registry or repo**: The agent could not find any trace of a product named MFSoft: not in the sandbox repo, not in environment variables, not as an npm package, and not as a PyPI package. This is a test-environment/setup issue rather than a product defect, since MFSoft was never located to evaluate. The agent correctly stopped and asked the user for the real product name, URL, or credentials instead of guessing or fabricating an SDK.
  Event 13:

  ```text
  # Keep generated and vendored files out of source diffs.
  
  # Logs / OS cruft
  *.log
  .DS_Store
  ```
  Event 19:

  ```text
  ERROR: No matching distribution found for mfsoft
  ```
  Event 21:

  ```text
  Repo: /sandbox/repo contains only a .gitignore and a single "Initial workspace" commit — no README, quickstart, SDK, or vendor docs.
  ```

#### Suggested Changes
None identified in this transcript.

### Kimi K3
[View public run](https://agents.withgauge.com/p/runs/54d148e3-8a51-4b9d-8c32-060741e08bbc) · [Read transcript](https://www.ax-check.com/mfsoft.dev/sessions/kimi.json)
Final output gives a pricing table (Community $0 / Pro $29.99 / Infra $99.99, launch vs regular) plus explicit assumptions: perpetual license for up to 5 Macs, 12 months of updates, 14-day trial and refund window.
#### End-to-end onboarding
- **End-to-end onboarding not demonstrated**: No credentials of any kind were obtained or used. The agent never attempted signup, API key generation, or any authenticated call. It concluded the product (MFCommander) is a macOS desktop GUI app with no SDK/API/CLI to onboard into, so no developer workflow existed to act on.
  Event 45:

  ```text
  No SDK or API. Nothing on PyPI, npm, or the site. The only API endpoints on the domain are `/api/buy/*` (checkout) and `/api/download`. No CLI, no scripting interface, no webhooks — it's a closed desktop GUI app.
  ```

#### Hallucinated URLs
- **No fabricated URLs used after failure**: The agent tried plausible guesses like mfsoft.com and mfsoft.io before finding the real mfsoft.dev domain via GitHub search, but it did not proceed to use these guessed domains as if they worked; it corrected course once it found the actual site. This is normal discovery, not a hallucination that misled the session.
  Event 18:

  ```text
  mfsoft.com: 000
  mfsoft.io: 000
  
  
  Command exited with code 6
  ```

#### Blockers
- **Product has no API, SDK, or CLI to build against**: After searching PyPI, npm, GitHub, and the vendor's own site, the agent found MFCommander is a closed macOS desktop GUI application with only checkout/download endpoints exposed. There is no developer-facing interface (API, SDK, or CLI) for a coding agent to exercise, so the requested example build was correctly declared out of scope. This is a product characteristic (a consumer GUI tool, not a developer platform) rather than an environment or credential problem.
  Event 6:

  ```text
  ERROR: No matching distribution found for mfsoft
  npm error 404
  npm error 404  'mfsoft@*' is not in this registry.
  ```
  Event 43:

  ```text
  href="/api/buy/infra"
  href="/api/buy/pro"
  href="/api/download"
  ```
  Event 45:

  ```text
  No CLI, no scripting interface, no webhooks — it's a closed desktop GUI app.
  ```
- **Docs page unreachable and app requires macOS hardware unavailable in sandbox**: The /docs path returned 404 and the site's sitemap does not list a docs page, while the product itself only runs on Apple silicon macOS, which the Linux sandbox cannot provide. Both are environment/product-fit issues rather than agent mistakes: the agent verified via sitemap.xml that no docs route exists and correctly noted the sandbox cannot run the app.
  Event 37:

  ```text
  === /docs
  404  Page not found Page not found That address does not exist on mfsoft.dev.
  ```
  Event 45:

  ```text
  Can't even run it here. This is a Linux sandbox; the app requires Apple silicon macOS. There is no hosted/web version to drive.
  ```

#### Suggested Changes
- **Add a working docs link to the site navigation or fix the sitemap**: The main site's nav/footer links (captured in the homepage HTML) do not include a working /docs route, and requesting https://mfsoft.dev/docs returns a 404 with a 'Page not found' message pointing back to the homepage. Since MFCommander has no API/SDK, publishing a docs or help page indexed correctly (or removing dead doc references) would prevent this dead-end for anyone probing for developer resources. Verify by curling https://mfsoft.dev/docs and confirming it resolves instead of 404s.
  Event 37:

  ```text
  === /docs
  404  Page not found Page not found That address does not exist on mfsoft.dev. If you followed a link from an email or another site, it may have been shortened or truncated. Back to MFCommander
  ```

### Qwen 3.8 Max
[View public run](https://agents.withgauge.com/p/runs/e2a10d87-60b5-4d14-b2ef-fcfdb9d74f7b) · [Read transcript](https://www.ax-check.com/mfsoft.dev/sessions/qwen.json)
Final output gives a pricing table (Community/Pro/Infra) with explicit assumptions: one-time purchase model, 14-day trial, launch pricing expiring 2026-10-31, license covers up to 5 Macs, macOS 14+/Apple silicon requirement, checkout via Polar.
#### End-to-end onboarding
- **End-to-end onboarding not demonstrated**: The agent never attempted product signup or authentication. It determined via web research that MFSoft/MFCommander is a closed-source macOS GUI file manager with no SDK, API, or CLI, and stopped without obtaining or using any credentials.
  Event 38:

  ```text
  So there's no "hosted product via SDK/API" to use here. It's a desktop app; the only programmatic touchpoint is `brew install --cask mfsoft-dev/tap/mfcommander`, which just installs a GUI I can't run or script in this Linux sandbox.
  ```

#### Hallucinated URLs
None identified in this transcript.

#### Blockers
- **No developer-facing SDK, API, or CLI exists for MFSoft**: Product research (npm registry, PyPI, docs site, GitHub org) turned up no software development kit, public API, or CLI—only a macOS GUI app (MFCommander) installable via Homebrew. This is a product-scope limitation, not an agent or environment error: the agent correctly identified there was nothing to build against and stopped per the user's own instruction to do so if no developer workflow exists.
  Event 36:

  ```text
  404 https://mfsoft.dev/docs
  ```
  Event 18:

  ```text
  {"objects":[],"total":0,"time":"2026-09-19T18:04:34.210Z"}
  ```
  Event 38:

  ```text
  No SDK — nothing on npm (`mfsoft` → 0 results), nothing on PyPI.
  ```
  Event 38:

  ```text
  GitHub org (`mfsoft-dev`) contains only a release/issue-tracker repo and a Homebrew tap — no source, no libraries, no CLI.
  ```

#### Suggested Changes
- **Add a developer API or SDK if programmatic access is intended**: If MFSoft/MFCommander is meant to support any automation or integration beyond the desktop GUI, publish an API or SDK and reference it from mfsoft.dev/docs (currently 404) or the help page's articleSection list. Verify by confirming a package appears on npm/PyPI or a docs page resolves with API reference content.
  Event 36:

  ```text
  404 https://mfsoft.dev/docs
  ```
  Event 31:

  ```text
  proficiencyLevel": "Beginner"
  ```

### Task given to each agent
Help me build a simple example using MFSoft. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop.

No product credentials were supplied and no purchases were authorized.

## Score: A · 100/100 (provisional)
Grades come from completed site checks. Coding sessions and skipped checks do not affect the score.

### Clarity
- **Pass** — Homepage answers Markdown requests

  ```text
  Homepage returned text/markdown with Accept: text/markdown, confirming Markdown support.
  ```

- **Pass** — llms.txt provides an actionable documentation index

  ```text
  llms.txt lists product, docs, support, legal pages with descriptions and Markdown routes.
  ```

- **Pass** — llms.txt provides navigation guidance

  ```text
  llms.txt groups links under Product, Documentation, Support, Legal, Endpoints headings.
  ```

- **Skipped** — llms.txt mentions offered API, MCP, and skills

  ```text
  llms.txt lists endpoints and Homebrew install but no API, MCP, or skills surfaces.
  ```

- **Pass** — A compact guide representation exists

  ```text
  llms.txt states every page is available as clean Markdown via Accept header or .md suffix.
  ```

- **Pass** — A focused guide is directly retrievable

  ```text
  llms.txt is a directly retrievable compact index linking docs, product, support and legal pages.
  ```

- **Pass** — Equivalent instructions fit a token budget

  ```text
  llms.txt is 962 tokens, well under the 8000-token budget, with usable organization.
  ```

- **Pass** — Product-docs links survive format changes

  ```text
  Homepage Markdown supported; llms.txt links to .md docs routes like help.md and pricing.md.
  ```

- **Pass** — The compact guide is independently actionable

  ```text
  llms.txt gives a compact, organized guide with product, docs, support, legal and endpoint sections.
  ```

- **Pass** — Install and next-step links resolve

  ```text
  Download, buy, and Homebrew install links resolve; download redirects to the MFCommander.dmg build.
  ```


### Onboarding
- **Skipped** — Docs lead to a relevant quickstart

  ```text
  Only llms.txt fetched; no docs quickstart page retrieved to assess.
  ```

- **Skipped** — Installation commands are extractable

  ```text
  llms.txt mentions a Homebrew cask but no installation page was fetched.
  ```

- **Skipped** — Code examples are available without interaction

  ```text
  No documentation or code example pages were fetched for MFCommander.
  ```

- **Skipped** — Prerequisites and auth boundaries are explicit

  ```text
  No help or setup page fetched; auth and prerequisites not evidenced.
  ```


### Pricing
- **Failed** — Agents identify pricing and its assumptions

  ```text
  3 of 3 sessions were judged on pricing; 1 fell short. DeepSeek V4 Pro: Final output explicitly states it 'can't point you to authoritative pricing' and gives no cost figure or assumptions at all — rubric requires a stated cost with named assumptions, which is absent. Kimi K3: Final output gives a pricing table (Community $0 / Pro $29.99 / Infra $99.99, launch vs regular) plus explicit assumptions: perpetual license for up to 5 Macs, 12 months of updates, 14-day trial and refund window. Qwen 3.8 Max: Final output gives a pricing table (Community/Pro/Infra) with explicit assumptions: one-time purchase model, 14-day trial, launch pricing expiring 2026-10-31, license covers up to 5 Macs, macOS 14+/Apple silicon requirement, checkout via Polar. This behavioural item does not affect the fast grade.
  ```

- **Pass** — Pricing is readable without interaction

  ```text
  Pricing page renders prices and edition comparison directly in fetched Markdown, no interaction needed.
  ```

- **Pass** — Prices are stated, not gated

  ```text
  Community $0, Pro $29.99, Infra $99.99 stated openly with regular prices shown.
  ```

- **Pass** — Pricing units and limits are explicit

  ```text
  Units explicit: one-time purchase, five Macs, 12 months updates, USD, 14-day trial.
  ```


### Activation
- **Skipped** — An API reference or OpenAPI spec is reachable

  ```text
  No API reference or OpenAPI spec offered; llms.txt lists only download and checkout redirect endpoints.
  ```

- **Skipped** — An MCP server is documented and well-formed

  ```text
  No MCP server documented anywhere in the fetched MFCommander pages.
  ```

- **Pass** — A CLI install path is documented

  ```text
  llms.txt documents Homebrew CLI install: brew install --cask mfsoft-dev/tap/mfcommander.
  ```

- **Skipped** — SDK packages resolve on their registries

  ```text
  No SDK or developer package registry lookup supplied; only a macOS app and Homebrew cask.
  ```

- **Skipped** — Agent skills are published

  ```text
  No agent skills published or referenced in the fetched MFCommander documentation.
  ```



[Full report data](https://www.ax-check.com/mfsoft.dev/report.json)
