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

webmcp-tool-agent-readiness

https://webmcp-tool.com

Registry code: 64f8d02601f28b28

api record

Scores public websites for agent readiness. Reach for score_site first, then explain_check for any finding the user asks about. Call watch_site only after the user explicitly requests a monitoring confirmation email to the supplied address. Monitoring starts only after the recipient confirms on the page.

endpoint
https://webmcp-tool.com/api/mcp
door code
70da6ea1281e0b6c
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 webmcp-tool-agent-readiness live?
Yes — it answered the hub's last check (checked 1h ago). It answered 77% of checks over the last 30 days.
Is webmcp-tool-agent-readiness free to use?
Yes — the hub reached it with no key and no payment.
What tools does webmcp-tool-agent-readiness have?
5 tools: explain_check, score_site, get_badge_embed, watch_site, list_checks.
Is webmcp-tool-agent-readiness 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
77.4%

90 days 89.2%· all time 90.1%

latency
59ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 757 checks · signed record
  • down → live
  • down → live
  • degraded → down· HTTP 504
  • degraded → down· HTTP 504
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • score a website's agent readiness
  • explain an agent readiness finding
  • get an agent readiness badge
  • watch a site's score by email
takes → gives
web pages → data
tools
4 reads1 sends messages
_ 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 5 tools
1 open 4 never probed 1 of 5 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.

  • list_checks reads open 1h ago

    Use this when the user asks what the Agent Readiness Score measures or how it is calculated, rather than how one site performs. Lists every check in the rule set with its pillar, weight and question. Fetches nothing.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • explain_check reads unknown 1h ago

    Use this when the user asks what a specific Agent Readiness finding means, why it matters to AI agents or how to fix it, usually after score_site. Explains one check: what it asks, why an agent cares, how it is weighted and how to fix it, with a code snippet where one exists. Answers from the rule set only and fetches nothing.

    mcp-tool

    {
      "type": "object",
      "required": [
        "checkId"
      ],
      "properties": {
        "checkId": {
          "type": "string",
          "description": "Check identifier, for example content-without-javascript"
        }
      }
    }
    arguments 12 lines
  • score_site reads unknown 23h ago

    Use this when the user asks whether a website is ready for AI agents, agent-ready, AI-agent friendly or WebMCP-ready, or what to fix so agents can use it. Scores one public website out of 100 for agent readiness and returns a grade, the fitness and adoption sub-scores, the five highest-value fixes, the scan time and whether the result came from cache. Reads one public page plus standard discovery files (robots.txt, /.well-known endpoints, sitemaps, llms.txt) and up to ten same-origin script bundles; it never logs in, submits forms or changes the site. Results are cached for about an hour.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Public http(s) address, for example example.com"
        }
      }
    }
    arguments 12 lines
  • get_badge_embed reads unknown 1h ago

    Use this when the user wants to show a site's Agent Readiness badge on that site. Scores the site if needed, then returns the HTML snippet for sites at grade C or better (bronze, silver or gold), or the reason and the first fixes when the site is not eligible. Returns HTML to paste; it installs nothing and runs no script.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Public http(s) address, for example example.com"
        }
      }
    }
    arguments 12 lines
  • watch_site sends messages unknown never probed

    Use this only when the user explicitly asks to be emailed when a site's Agent Readiness Score changes. Sends a confirmation email for monitoring that site. Use only when the user explicitly asks to receive a confirmation email for monitoring at the supplied address. Set sendConfirmationEmail to true only then. Monitoring starts only after the recipient opens the link and confirms on the page; this call itself sends one email.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url",
        "email",
        "sendConfirmationEmail"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Public http(s) address or bare host, for example example.com"
        },
        "email": {
          "type": "string",
          "description": "Address that will receive the confirmation and the alerts"
        },
        "sendConfirmationEmail": {
          "type": "boolean",
          "const": true,
          "description": "True only after the user explicitly requests a monitoring confirmation email."
        }
      }
    }
    arguments 23 lines
_ try it over mcp 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 64f8d02601f28b28.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/64f8d02601f28b28/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/64f8d02601f28b28/badge.svg)](https://brick.blue/agent/64f8d02601f28b28?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 knowoff the mcp door
card completeness
90%

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.