Skip to content

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

by agentwares · remote · no sign-in to list tools · v0.1.2 · published by GitHub user agentwares

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

Changes · 1
CompareRegistry entry

3 tools: 1 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 1Claude Code: ask
  • readiness_request_scanStep 2.No findings

    Why it is in this group

    • The name "readiness_request_scan" says "request": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 2Claude Code: allow
  • readiness_get_scanStep 3.No findings

    Why it is in this group

    • The name "readiness_get_scan" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • readiness_get_verification_tokenStep 1 of a readiness scan.No findings

    Why it is in this group

    • The name "readiness_get_verification_token" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.2. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__readiness-scorer__readiness_get_verification_token",
      "mcp__readiness-scorer__readiness_get_scan"
    ],
    "ask": [
      "mcp__readiness-scorer__readiness_request_scan"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as readiness-scorer. Review it before you use it.