# AX Check: mysetup.ai
Checked 2026-09-19.

Docs are agent-ready, but setup steps and pricing stay unverified.
A compact guide covers MCP tools, scopes and OAuth clearly (10 of 23 items pass), but install steps, code examples and pricing details were never confirmed present.

## Onboarding needs a login

## Coding sessions
All three independent sessions completed and agreed mysetup.ai has no published pricing, treating it as a free community tool. They checked pages like /pricing, /docs and /connect directly rather than running any local setup, and none reported a login wall blocking access to documentation.

### DeepSeek V4 Pro
[View public run](https://agents.withgauge.com/p/runs/2c84b6a4-271b-43a7-9fd6-c4db84359200) · [Read transcript](https://www.ax-check.com/mysetup.ai/sessions/deepseek.json)
Final output states 'There is no pricing' for mysetup.ai but that's a factual finding, not the rubric's ask — it never states a cost figure with named assumptions (plan/region/machine/workload), so the criterion (stating pricing with assumptions) is not met since no pricing exists to state.
#### End-to-end onboarding
- **Onboarding needs a login**: Agent explored mysetup.ai's public JSON feed/HTML pages (no auth) and ran a script against them successfully. It found the OAuth/MCP write path and even completed dynamic client registration for a client_id. But obtaining an actual bearer token requires human browser sign-in via GitHub/Google/X -- /authorize redirected straight to /signin with no device-code flow or API key. So no authenticated MCP operation (list_setups, get_setup, update_draft, etc.) was ever performed; only unauthenticated public reads succeeded.
  Event 71:

  ```text
  == Recent builds on mysetup.ai ==
    @lawrencecchen            Lawrence Chen shared their AI setup
  ```
  Event 61:

  ```text
  final:https://mysetup.ai/signin?returnTo=%2Fauthorize%3Fclient_id%3DXGeQVWI0pdLuCOWu%26response_type%3Dcode...
  ```
  Event 50:

  ```text
  {"client_id":"XGeQVWI0pdLuCOWu","redirect_uris":["http://127.0.0.1:0/callback"],"client_name":"mysetup-probe","grant_types":["authorization_code","refresh_token"],"response_types":["code"],"token_endpoint_auth_method":"none","client_id_issued_at":1789802964}
  ```

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

#### Blockers
- **OAuth sign-in wall blocks any authenticated MCP write action**: The MCP write tools (update_draft, preview_draft, set_publication) require an OAuth authorization_code grant. Hitting /authorize redirects to a browser sign-in page (GitHub/Google/X), with no device-code flow or static API key alternative. This is normal product authentication behavior, not a defect, but it is an unresolved need for human login that stopped the agent from performing any write/contribute action.
  Event 61:

  ```text
  final:https://mysetup.ai/signin?returnTo=%2Fauthorize%3Fclient_id%3DXGeQVWI0pdLuCOWu%26response_type%3Dcode%26scope%3Dsetup%253Aread%26redirect_uri%3Dhttp%253A%252F%252F127.0.0.1%253A0%252Fcallback%26code_challenge%3Dabc123%26code_challenge_method%3DS256%26state%3Dtest code:200
  ```
  Event 73:

  ```text
  completing an OAuth `authorization_code` grant requires a human to sign in with GitHub/Google/X in a browser and grant consent — hitting `/authorize` redirects to `/signin`. There is **no device-code flow and no static API key**, so I cannot obtain a token myself
  ```
- **No public pricing page found**: The agent checked /pricing, /price, and /plans, all returning 404, and found no pricing information in llms.txt, homepage, /sharing, or /connect. This appears to be expected product behavior (a free community product) rather than a broken link, since no page ever claimed pricing existed.
  Event 31:

  ```text
  === /pricing ===
  404
  === /price ===
  404
  === /plans ===
  404
  ```

#### Suggested Changes
- **Add a lightweight or device-code auth option for agent-only MCP contribution flows**: Currently the only path to obtain an MCP write-scoped token is a full browser OAuth consent screen (GitHub/Google/X), confirmed by /authorize redirecting to /signin with no device-code or API-key alternative in the discovery metadata at /.well-known/oauth-authorization-server. Verify by having a headless agent complete a token exchange without a browser; a successful call to update_draft or preview_draft with a self-obtained token would confirm the fix.
  Event 61:

  ```text
  final:https://mysetup.ai/signin?returnTo=%2Fauthorize%3Fclient_id%3DXGeQVWI0pdLuCOWu...
  ```
  Event 30:

  ```text
  {"issuer":"https://mysetup.ai","authorization_endpoint":"https://mysetup.ai/authorize","token_endpoint":"https://mysetup.ai/oauth/token","registration_endpoint":"https://mysetup.ai/oauth/register"...}
  ```
- **State pricing/free status explicitly on the homepage or llms.txt**: No page or doc (llms.txt, homepage, /sharing, /connect) states whether mysetup.ai is free; the agent had to infer this from the absence of a /pricing page (404) and the sign-in flow having no billing step. Add one line to llms.txt or the homepage confirming the product is free, and check it resolves ambiguity for future developer-facing agents.
  Event 31:

  ```text
  === /pricing ===
  404
  === /price ===
  404
  === /plans ===
  404
  ```
  Event 73:

  ```text
  There is **no pricing**. No `/pricing` page exists (404), and nothing in `llms.txt`, the homepage, `/sharing`, or `/connect` mentions paid tiers, billing, or credits.
  ```

### Kimi K3
[View public run](https://agents.withgauge.com/p/runs/48a7635f-3451-4d28-83d3-7c82e115c601) · [Read transcript](https://www.ax-check.com/mysetup.ai/sessions/kimi.json)
Final output states the product is free with no published pricing, backed by explicit checks (`/pricing`→404, `/docs`, `/api`, `llms.txt` all checked at seq 14-19), which is the basis for the 'free' conclusion.
#### End-to-end onboarding
- **Onboarding needs a login**: Agent probed mysetup.ai's public site and MCP OAuth discovery endpoints, confirmed the MCP server requires an authorization-code OAuth flow with interactive browser sign-in for any write scope (setup:write/setup:publish), and could not obtain credentials itself. It fell back to consuming only the public, unauthenticated JSON feed (no login needed) rather than performing any authenticated write operation on the product.
  Event 26:

  ```text
  HTTP/2 401 
  
  ```
  Event 27:

  ```text
  "authorization_endpoint": "https://mysetup.ai/authorize"
  ```
  Event 41:

  ```text
  mysetup.ai community — New and updated AI setups shared by the community.
  ```
  Event 43:

  ```text
  requires an **authorization-code OAuth flow with interactive browser sign-in** — I verified the endpoint returns `401` without a bearer token. I can't complete that consent step on my own
  ```

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

#### Blockers
- **MCP write tools require interactive OAuth sign-in**: The product's write-capable MCP tools (update_draft, preview_draft, set_publication) sit behind an OAuth authorization-code flow that needs a human to sign in through a browser. This is normal product authentication behavior, not a defect, and the agent correctly identified it rather than attempting to bypass it.
  Event 26:

  ```text
  HTTP/2 401 
  
  ```
  Event 43:

  ```text
  the MCP write path (`update_draft` → `preview_draft` → `set_publication`) requires an **authorization-code OAuth flow with interactive browser sign-in**
  ```
- **No official SDK published for the product**: The agent checked PyPI and npm registries for a 'mysetup' package and found neither exists, meaning the only programmatic access is the raw MCP/HTTP API plus public JSON/Atom/RSS feeds. This limited the buildable example to read-only feed consumption.
  Event 8:

  ```text
  {"message": "Not Found"}
  404
  ---
  {"error":"Not found"}
  ```

#### Suggested Changes
- **Add a pricing page or explicit free-tier statement**: Requests to /pricing returned 404 and llms.txt has no cost information, so the agent could not answer the pricing question at all. Publish a /pricing page (or a line in llms.txt) stating the product is free or describing tiers, then confirm curl https://mysetup.ai/pricing returns 200 with pricing content.
  Event 19:

  ```text
  ---pricing---
  404
  404
  404
  
  ```
- **Offer a non-interactive/token-based path for MCP write scopes**: Currently setup:write and setup:publish are only reachable via full browser OAuth sign-in, which blocks any headless agent from completing a write example end-to-end. Consider documenting (on /connect or llms.txt) a supported way for a developer to generate a personal access token for scripted testing, then verify a scripted client can call update_draft with that token.
  Event 43:

  ```text
  I can't complete that consent step on my own; you'd need to sign in once and hand me a token, or connect your own MCP client
  ```

### Qwen 3.8 Max
[View public run](https://agents.withgauge.com/p/runs/40bf95c1-43f1-41f4-b14c-22a801f58d5e) · [Read transcript](https://www.ax-check.com/mysetup.ai/sessions/qwen.json)
Final output states pricing is $0/unpublished, backed by checking /pricing (404), homepage, /sharing, /connect (seq 25-54), and flags the assumption explicitly as 'free-today, not free-forever' rather than a bare figure.
#### End-to-end onboarding
- **Onboarding needs a login**: The agent discovered the real MCP endpoint and OAuth discovery documents, and wrote a working connect-oauth.mjs script implementing dynamic client registration + PKCE. However, it never completed sign-in: the token exchange requires a human to authenticate via GitHub/Google/X in a browser. The one authenticated MCP call attempted (mcp-get-setup.mjs) failed with 'No token' because no credential was ever obtained, so no authenticated product operation occurred.
  Event 93:

  ```text
  mysetup: No token. Run `npm run connect` (opens a browser sign-in), or set MYSETUP_TOKEN.
  ```
  Event 35:

  ```text
  HTTP/2 401 
  date: Sat, 19 Sep 2026 07:28:54 GMT
  content-length: 0
  cache-control: no-store
  ```
  Event 95:

  ```text
  The MCP endpoint returns `401` without a token, and getting one requires a browser sign-in with GitHub/Google/X — a human step I can't complete.
  ```

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

#### Blockers
- **MCP writes require human browser sign-in**: The mysetup.ai MCP endpoint (POST /mcp) requires an OAuth bearer token obtained via browser sign-in with GitHub, Google, or X. This is normal product authentication (not a product defect or agent error), and it stopped the agent from completing any authenticated MCP call such as get_setup or the write tools (update_draft, preview_draft, set_publication). The agent correctly identified this as a step it could not complete itself and stopped rather than faking success.
  Event 35:

  ```text
  www-authenticate: Bearer realm="OAuth", resource_metadata="https://mysetup.ai/.well-known/oauth-protected-resource/mcp", scope="setup:read setup:write setup:publish"
  ```
  Event 95:

  ```text
  getting one requires a browser sign-in with GitHub/Google/X — a human step I can't complete
  ```
- **No published pricing page (site behavior, not an error)**: The /pricing path returns 404, and no plans, billing, or paid-tier language appears on the homepage, /sharing, or /connect pages. This is a product content gap rather than an agent mistake; the agent correctly reported this as 'no pricing published' instead of guessing a plan structure.
  Event 27:

  ```text
  ===== /pricing
  200
  ===== /connect
  200
  ===== /pricing
  404
  ```
  Event 95:

  ```text
  No pricing is published. `/pricing` is 404; the homepage, `/sharing`, and `/connect` mention no plans, billing, or paid tiers
  ```

#### Suggested Changes
- **Add a pricing or free-tier statement to the homepage or /sharing page**: Currently /pricing 404s and neither the homepage nor /sharing nor /connect state whether sign-in, publishing, or MCP access is free. A first-time developer had to infer 'appears free' from absence of billing language. Add an explicit line (e.g., on /sharing or /connect) confirming the service has no paid tier, and verify by re-fetching /sharing and checking for a clear cost statement.
  Event 95:

  ```text
  No pricing is published. `/pricing` is 404; the homepage, `/sharing`, and `/connect` mention no plans, billing, or paid tiers — sign-in and publishing appear free.
  ```

### Task given to each agent
Help me build a simple example using mysetup.ai. 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: B · 81/100 (provisional)
Grades come from completed site checks. Coding sessions and skipped checks do not affect the score.

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

  ```text
  Homepage returned text/html even when Markdown was requested; no Markdown representation offered.
  ```

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

  ```text
  llms.txt lists homepage, community, connect, sharing, feeds, example setup and MCP endpoint.
  ```

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

  ```text
  llms.txt groups links under Public pages, Writing reference and Agent access with descriptions.
  ```

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

  ```text
  llms.txt documents the MCP endpoint, its five tools, scopes and OAuth metadata.
  ```

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

  ```text
  llms.txt is a compact Markdown guide covering MCP tools, scopes and contribution workflow.
  ```

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

  ```text
  llms.txt fetched directly at 200 as text/plain Markdown with actionable agent guidance.
  ```

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

  ```text
  llms.txt measured 627 tokens, well under the 8000-token budget.
  ```

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

  ```text
  Homepage Markdown unsupported, so link preservation across formats cannot be judged.
  ```

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

  ```text
  llms.txt gives concrete MCP contribution workflow: get_setup, draft, preview, publish steps.
  ```

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

  ```text
  Homepage links to /community, /connect, /sharing; llms.txt confirms these routes.
  ```


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

  ```text
  llms.txt links a connect page but no fetched quickstart or docs index was retrieved.
  ```

- **Skipped** — Installation commands are extractable

  ```text
  No installation or CLI guide was fetched; only MCP connection is described.
  ```

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

  ```text
  No code examples were fetched; llms.txt only names MCP tools and scopes.
  ```

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

  ```text
  llms.txt states OAuth bearer tokens, setup:read/write/publish scopes, and browser sign-in limits.
  ```


### Pricing
- **Skipped** — Pricing is readable without interaction

  ```text
  Not applicable: the relevant product is free. No pricing page fetched; mysetup.ai is a free community site with no paid plans.
  ```

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

  ```text
  Not applicable: the relevant product is free. No pricing page fetched; site appears to be a free community with no paid tiers.
  ```

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

  ```text
  Not applicable: the relevant product is free. No pricing evidence fetched; no units or limits to assess.
  ```

- **Skipped** — Agents identify pricing and its assumptions

  ```text
  Not applicable: the relevant product is free. No pricing page fetched; mysetup.ai is a free community site with no paid plans.
  ```


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

  ```text
  No API reference or OpenAPI spec fetched; only an OAuth-protected MCP endpoint is documented.
  ```

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

  ```text
  llms.txt documents MCP at /mcp with Streamable HTTP, OAuth, and five named tools.
  ```

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

  ```text
  No CLI install path documented in the fetched pages.
  ```

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

  ```text
  No SDK or package registry evidence supplied for mysetup.ai.
  ```

- **Skipped** — Agent skills are published

  ```text
  No agent skills published or documented in the fetched evidence.
  ```



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