_ registry / mcp http-sse · checked 1h ago

Agent Readiness Scanner

https://isitagentready.com

Registry code: cebe83946384200f

api record

Scans a website for support of 22 AI-agent protocols and standards, such as discovery files, and reports an agent-readiness audit.

endpoint
https://isitagentready.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Agent Readiness Scanner live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is Agent Readiness Scanner free to use?
Not measured yet.
What tools does Agent Readiness Scanner have?
1 tool: scan_site.
Is Agent Readiness Scanner safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.6%

90 days 99.3%· all time 99.3%

latency
92ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 270 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
used for
  • scan a website for ai agent protocol support
takes → gives
web pages → data
tools
1 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 1 tools
1 never probed 0 of 1 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • scan_site reads unknown never probed

    Scan a website to audit its support for AI agent protocols and standards. Checks 23 standards across 5 categories: discoverability (robots.txt, sitemap, Link headers, DNS for AI Discovery (DNS-AID)), content accessibility (markdown content negotiation), bot access control (AI bot rules, Content Signals, Web Bot Auth), API/auth/MCP/A2A discovery (API catalog, OAuth/OIDC, OAuth Protected Resource, Auth.md, MCP Server Card, A2A Agent Card, agent skills, WebMCP, ARD capability manifest, Personal Agent Protocol/Poppy discovery), and commerce (UCP, x402, MPP, ACP, AP2). Returns a readiness level (0-5), per-check pass/fail results with details, and actionable fix instructions with spec URLs for every failing check.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "format": "uri",
          "description": "Full URL including protocol (e.g., https://example.com/docs). Page checks use this URL; site-wide checks use its origin."
        },
        "profile": {
          "enum": [
            "all",
            "content",
            "apiApp"
          ],
          "type": "string",
          "description": "Site profile preset that controls which checks are included. \"all\" (default) runs all 23 checks. \"content\" focuses on discoverability and content for blogs/docs. \"apiApp\" runs all checks except commerce."
        },
        "enabledChecks": {
          "type": "array",
          "items": {
            "enum": [
              "robotsTxt",
              "sitemap",
              "linkHeaders",
              "dnsAid",
              "markdownNegotiation",
              "robotsTxtAiRules",
              "contentSignals",
              "webBotAuth",
              "apiCatalog",
              "oauthDiscovery",
              "oauthProtectedResource",
              "authMd",
              "mcpServerCard",
              "a2aAgentCard",
              "agentSkills",
              "webMcp",
              "ard",
              "personalAgentProtocol",
              "x402",
              "mpp",
              "ucp",
              "acp",
              "ap2"
            ],
            "type": "string"
          },
          "description": "Explicit list of check names to include (overrides profile). Valid names: robotsTxt, sitemap, linkHeaders, dnsAid, markdownNegotiation, robotsTxtAiRules, contentSignals, webBotAuth, apiCatalog, oauthDiscovery, oauthProtectedResource, authMd, mcpServerCard, a2aAgentCard, agentSkills, webMcp, ard, personalAgentProtocol, x402, mpp, ucp, acp, ap2"
        }
      }
    }
    arguments 55 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id cebe83946384200f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/cebe83946384200f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/cebe83946384200f/badge.svg)](https://brick.blue/agent/cebe83946384200f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
50%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.