https://agentwares-readiness.vercel.app/api/mcp ↗
Probe a signup URL you own and score whether an AI agent can sign up unaided.
Readiness scorer — can an agent sign up to your SaaS? is a remote MCP server published at agentwares-readiness.vercel.app. It has been probed 6 times since 9/12/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 297 ms, placing it among the faster endpoints. It offers a narrow, focused set of 3 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
readiness_get_verification_token — Description could clarify that this is the first step in a multi-step processreadiness_request_scan — Error handling details are insufficient (only 'DOMAIN' failure mentioned)readiness_get_scan — Description lacks explicit guidance on when to call this tool (e.g., 'after readiness_request_scan returns a scan ID')Risk: low
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
readiness_get_verification_tokenStep 1 of a readiness scan. Returns the domain-ownership token for the URL's host plus the three ways to publish it (DNS TXT record, <meta> tag, /.well-known file). The token is deterministic for the host, so calling this again returns the same value. Nothing is stored.
urlstringrequiredreadiness_request_scanStep 2. Verifies domain ownership (DNS TXT / meta tag / .well-known must carry the token from readiness_get_verification_token), then queues a Playwright probe that tries to sign up, accept the terms and mint an API key with no human. Returns the scan id and the public results URL. Fails with DOMAIN_NOT_VERIFIED (with instructions) or RATE_LIMITED (3 scans per host per day). Never solves CAPTCHAs.
urlstringrequiredreadiness_get_scanStep 3. Poll a scan by id. While status is queued/running only metadata is returned; when done you get the 0-100 score, grade, per-item rubric points with evidence, the fix list, and what could not be observed.
idstringrequiredDerived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/io-github-agentwares-readiness-scorer)<a href="https://mcpmetrics.io/servers/io-github-agentwares-readiness-scorer"><img src="https://mcpmetrics.io/badge/io.github.agentwares/readiness-scorer/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
Scan website AI readiness, understand the result and route customers to the right SYA package.
Manage your Pollen account: sync, enrich, fix, and publish your store's catalog for AI agents.
Scan any website or MCP server for agent-trust-readiness; returns a signed, verifiable scorecard.
Carrier MCP — natural language control of your MVNO/eSIM fleet. 52 tools (43 OCS API wrappers + 8 AI intelligence + 1 OCS event history), 5 prompts, OAuth 2.1 + PKCE. Streamable HTTP on Cloudflare Workers.
Agent to Agent communication Platforms, Allows every MCP compatible agent to connect
Let your AI agent hire a human for tasks it can't do — first post free.
| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-13 01:33:33 | Legacy | 400 | 506 | 200 | 288 | 2025-11-25 |
| 2026-09-12 23:31:36 | Legacy | 400 | 316 | 200 | 566 | 2025-11-25 |
| 2026-09-12 21:29:15 | Legacy | 400 | 297 | 200 | 284 | 2025-11-25 |
| 2026-09-12 19:27:29 | Legacy | 400 | 280 | 200 | 228 | 2025-11-25 |
| 2026-09-12 17:24:09 | Legacy | 400 | 265 | 200 | 302 | 2025-11-25 |
| 2026-09-12 15:21:42 | Legacy | 400 | 244 | 200 | 315 | 2025-11-25 |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Comments
Sign in to write a comment
No comments yet. Be the first.