Readiness scorer — can an agent sign up to your SaaS?
REMOTE · AGENTWARES-READINESS.VERCEL.APP
Probe a signup URL you own and score whether an AI agent can sign up unaided.
Available components
Last scanned (1 hour ago)
Scores higher than 97% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 366 tokens (~122/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 10 Oct 26 +7
- Authorization: unverified → partial ▲ security
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- 7 Oct 26 +1
- Stability: 0.90 → pass security
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 12 Sept 26 0
- Server version: 0.1.1 → 0.1.2 functional
- 8 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.1.0 → 0.1.1 functional
- 7 Sept 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://agentwares-readiness.vercel.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 9c5f0e6a35c955e113044c86848e4cd5 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agentwares-readiness.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentwares-readiness.vercel.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://agentwares-readiness.vercel.app/api/mcp | HTTPS enforced | 308 | https://agentwares-readiness.vercel.app/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
readiness_get_scan ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | scan id returned by readiness_request_scan |
No output schema declared.
No examples provided.
readiness_get_verification_token ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public https URL of the SaaS signup (or landing) page, e.g. https://example.com/signup |
No output schema declared.
No examples provided.
readiness_request_scan ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public https URL of the SaaS signup (or landing) page, e.g. https://example.com/signup |
No output schema declared.
No examples provided.
How do I install the Readiness scorer — can an agent sign up to your SaaS? MCP server?
Readiness scorer — can an agent sign up to your SaaS? is a hosted endpoint at https://agentwares-readiness.vercel.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agentwares-readiness.vercel.app
claude mcp add --transport http agentwares-readiness-scorer 'https://agentwares-readiness.vercel.app/api/mcp'
What is the Readiness scorer — can an agent sign up to your SaaS? MCP server?
Readiness scorer — can an agent sign up to your SaaS? is an MCP server listed in the public MCP registry as io.github.agentwares/readiness-scorer. Probe a signup URL you own and score whether an AI agent can sign up unaided. This page covers its hosted endpoint (https://agentwares-readiness.vercel.app/api/mcp).
Is the Readiness scorer — can an agent sign up to your SaaS? MCP server safe to use?
Readiness scorer — can an agent sign up to your SaaS? scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Readiness scorer — can an agent sign up to your SaaS? MCP server expose?
Readiness scorer — can an agent sign up to your SaaS? exposes 3 tools: readiness_get_verification_token, readiness_request_scan, readiness_get_scan. Their descriptions and schemas cost roughly 308 tokens of context every time the server is loaded.
Does the Readiness scorer — can an agent sign up to your SaaS? MCP server require authentication?
No. We connected to Readiness scorer — can an agent sign up to your SaaS? without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Readiness scorer — can an agent sign up to your SaaS? MCP server still maintained?
Readiness scorer — can an agent sign up to your SaaS? is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.