Remote MCP server that probes a signup URL you own and scores, 0-100, whether an AI agent can sign up unaided.
What you can do
Get a domain-ownership verification token for a host, with DNS TXT, meta tag and well-known file publishing options
Request a scan after ownership is verified, which queues a Playwright probe that tries to sign up, accept terms and mint an API key without a human
Poll a scan by id to retrieve the score, grade, per-item rubric points with evidence, a fix list and what could not be observed
When to use it
Use it when you want to check whether your own SaaS signup flow is agent-friendly, or to get a concrete fix list before claiming your product supports autonomous agent onboarding.
Requirements
A remote streamable HTTP endpoint; no authentication, environment variables or headers are declared. You must control the domain being scanned and be able to publish a DNS TXT record, meta tag or well-known file to prove ownership. Network access to the endpoint is needed.
Before you install
The scan drives a real browser against your signup flow, creating accounts and minting API keys, so expect side effects in your own systems. Only scan domains you own; ownership is enforced by the verification token. Scan results are published at a public results URL.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.agentwares%2Freadiness-scorer/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
Parametersurlrequired
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_NOT_VERIFIED (with instructions) or RATE_LIMITED (3 scans per host per day). Never solves CAPTCHAs.
Parametersurlrequired
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.
Parametersidrequired
Version history
1
v0.1.2LatestSep 16, 2026
Score
75%
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.