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

agent-ready

https://agentready.sneeze.it

Registry code: 79e67f98ff582e7e

api record

Agent Ready scores whether AI agents can use a website. Use scan_website when someone asks whether a site works with AI agents, ChatGPT, Claude or Gemini, or how to make it agent ready. Present the score, the weakest areas and their findings, and give the report link for the full fix plan. Scores are out of 100; areas with nothing to measure are left out rather than scored zero.

endpoint
https://agentready.sneeze.it/mcp
protocol
streamable-http ·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-ready live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is agent-ready free to use?
Yes — the hub reached it with no key and no payment.
What tools does agent-ready have?
4 tools: scan_website, explain_check, get_report, get_scoring_method.
Is agent-ready 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
100%

90 days 100%· all time 100%

latency
144ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 4 tools
1 open 3 never probed 1 of 4 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.

  • get_scoring_method open 1h ago

    The scored areas, their weights and every check, so a score can be explained.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • scan_website unknown never probed

    Score any public website out of 100 for how well AI agents can use it: reach it, understand it, act on it (book, quote, buy), complete the task, act for a signed-in customer, trust its facts, and find the right location. Returns the score, a score per area, the most important finding in each area, and a link to the full report with every finding and the ordered fix plan. Takes 5 to 20 seconds.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "The website to scan, for example acme.com or https://www.acme.com/"
    },
    "fresh": {
      "type": "boolean",
      "description": "Rescan even if the site was scanned in the last 30 minutes. Use after the owner changed something."
    }
  }
}
    arguments 16 lines
  • explain_check unknown 1h ago

    Explain what one check measures, what it is worth and where to read how to fix it. Pass the check name as it appears in a report, for example "WebMCP tools an agent can call".

    mcp-tool

    {
  "type": "object",
  "required": [
    "check"
  ],
  "properties": {
    "check": {
      "type": "string",
      "description": "The check name, or a few words from it."
    }
  }
}
    arguments 12 lines
  • get_report unknown 1h ago

    Fetch a report that was already run, by its report link or id, without scanning again.

    mcp-tool

    {
  "type": "object",
  "required": [
    "report"
  ],
  "properties": {
    "report": {
      "type": "string",
      "description": "A report URL (https://agentready.sneeze.it/report/...) or report id."
    }
  }
}
    arguments 12 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 79e67f98ff582e7e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/79e67f98ff582e7e/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/79e67f98ff582e7e/badge.svg)](https://brick.blue/agent/79e67f98ff582e7e?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
80%

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.