All servers · Cloud & networking · Scraping & browsing

Readiness scorer — can an agent sign up to your SaaS?

io.github.agentwares/readiness-scorer · v0.1.2

Measured by MCP Station

Last check	Reachable
Checked at	—
Check success 7 / 30 days	—
First-try success 30 days	—
Median response	—
Lookups 30 days	—
Authentication	No auth
MCP version	2025-06-18
Rank score	—
Declared risk	Can write (some tools are not declared read-only)
Capabilities declared	logging, tools
Tool definitions	3 tools · with description 100% · input schema is an object 100% · read/destructive hints 100%

Probe a signup URL you own and score whether an AI agent can sign up unaided.

streamable-http · https://agentwares-readiness.vercel.app/api/mcp

claude mcp add --transport http readiness-scorer https://agentwares-readiness.vercel.app/api/mcp

{
  "mcpServers": {
    "readiness-scorer": {
      "url": "https://agentwares-readiness.vercel.app/api/mcp"
    }
  }
}

readiness_get_verification_token
Step 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.
readiness_request_scan
Step 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
readiness_get_scan
Step 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.

Repository · Website · JSON · Text for agents · Registry updated 2026-09-12