# 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.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `agentwares-readiness.vercel.app`: 74/100 (this document), [markdown](https://verifymcp.io/servers/agentwares-readiness-scorer/api-mcp.md), [page](https://verifymcp.io/servers/agentwares-readiness-scorer/api-mcp)

## Channel facts

- Endpoint: `https://agentwares-readiness.vercel.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 366 tokens (~122/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

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

### Cursor

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

### VS Code

```json
{
  "servers": {
    "agentwares-readiness-scorer": {
      "type": "http",
      "url": "https://agentwares-readiness.vercel.app/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.agentwares-readiness-scorer]
url = "https://agentwares-readiness.vercel.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "agentwares-readiness-scorer": {
      "type": "remote",
      "url": "https://agentwares-readiness.vercel.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add agentwares-readiness-scorer --url 'https://agentwares-readiness.vercel.app/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  agentwares-readiness-scorer:
    url: "https://agentwares-readiness.vercel.app/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "agentwares-readiness-scorer": {
      "Transport": "http",
      "Url": "https://agentwares-readiness.vercel.app/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add agentwares-readiness-scorer -t streamable-http -u 'https://agentwares-readiness.vercel.app/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "agentwares-readiness-scorer": {
      "type": "http",
      "url": "https://agentwares-readiness.vercel.app/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 71, +1)

- [functional] Server version: 0.1.1 → 0.1.2

### 2026-09-10 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 69, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.1.0 → 0.1.1

### 2026-09-07 (score 68)

First indexed and scored.

## MCP tools (3)

### `readiness_get_verification_token` (~102 tokens)

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.

Input parameters:

- `url` (string, required): Public https URL of the SaaS signup (or landing) page, e.g. https://example.com/signup

### `readiness_request_scan` (~131 tokens)

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.

Input parameters:

- `url` (string, required): Public https URL of the SaaS signup (or landing) page, e.g. https://example.com/signup

### `readiness_get_scan` (~75 tokens)

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.

Input parameters:

- `id` (string, required): scan id returned by readiness_request_scan

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/agentwares-readiness-scorer/api-mcp#diagnostics

## Score history

- 2026-09-20: 74
- 2026-09-19: 74
- 2026-09-18: 73
- 2026-09-17: 73
- 2026-09-16: 72
- 2026-09-15: 72
- 2026-09-14: 71
- 2026-09-13: 71
- 2026-09-12: 71
- 2026-09-11: 70
- 2026-09-10: 70
- 2026-09-09: 69
- 2026-09-08: 69
- 2026-09-07: 68

## Common questions

### 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 74 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://agentwares-readiness.vercel.app/api/mcp
- Repository: https://github.com/agentwares/servers
- Website: https://agentwares-readiness.vercel.app/
- Changelog RSS feed: https://verifymcp.io/servers/agentwares-readiness-scorer/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/agentwares-readiness-scorer/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/agentwares-readiness-scorer/api-mcp