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

agentready

https://www.agentready.me

Registry code: dd8970fd491e9dce

api record

AgentReady scans public sites and returns a Fix Pack v2 implementation contract with candidate targets. Typical loop: scan_url (already includes Fix Pack v2) → resolve candidates in the site repo → human review where required → deploy → verify_fixes.

endpoint
https://www.agentready.me/api/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 agentready live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is agentready free to use?
Yes — the hub reached it with no key and no payment.
What tools does agentready have?
7 tools: validate_a2a_agent_card, verify_fixes, audit_openapi_readiness, get_fix_pack, scan_url, check_crawler_access, get_public_report.
Is agentready 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
99.4%

90 days 98.9%· all time 98.9%

latency
1,097ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 283 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • scan a site for agent readiness
  • get prioritized fixes for a site
  • check ai crawler access
  • validate an a2a agent card
  • audit an openapi document
takes → gives
text, data → data
tools
6 reads1 changes data
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 7 tools
7 never probed 0 of 7 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.

  • validate_a2a_agent_card reads unknown never probed

    Statically validate an A2A Agent Card JSON object. Strict-current evidence and legacy interoperability are reported separately; no agent endpoint or skill is invoked.

    mcp-tool

    {
      "type": "object",
      "required": [
        "card"
      ],
      "properties": {
        "card": {
          "type": "object",
          "description": "A2A Agent Card JSON object."
        }
      }
    }
    arguments 12 lines
  • verify_fixes reads unknown never probed

    Re-scan a public URL and evaluate fix-specific stable ids from a previous v1 or v2 Fix Pack. A fix closes when its finding id is absent; score delta is secondary evidence only.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url",
        "previous_fix_pack"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Public site URL (https://example.com)"
        },
        "previous_fix_pack": {
          "type": "object",
          "description": "The Fix Pack returned earlier by get_fix_pack (or an object with {score, fixes:[{id}]})."
        }
      }
    }
    arguments 17 lines
  • audit_openapi_readiness reads unknown never probed

    Statically inspect an OpenAPI 3.0 or 3.1 JSON object or JSON string for operation identity, auth and scopes, errors, examples, retries, limits, lifecycle, pagination, and workflows. No API operation is executed.

    mcp-tool

    {
      "type": "object",
      "required": [
        "document"
      ],
      "properties": {
        "document": {
          "oneOf": [
            {
              "type": "object"
            },
            {
              "type": "string"
            }
          ],
          "description": "OpenAPI JSON object or a string containing JSON. YAML is reported as unsupported and unobservable."
        }
      }
    }
    arguments 19 lines
  • get_fix_pack reads unknown 22h ago

    Scan a public URL and return Fix Pack v2: prioritized fixes with stable ids, observed evidence, candidate target URLs and repository paths, review gates, and fix-specific acceptance assertions for a coding agent.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Public site URL (https://example.com)"
        }
      }
    }
    arguments 12 lines
  • scan_url changes data unknown never probed

    Run an AgentReady scan of a public URL. Returns the 0-100 score, per-phase findings, top priorities, and the Fix Pack v2 implementation contract. Repository paths remain candidate targets until a connected-repository resolver proves them.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Public site URL (https://example.com)"
        },
        "publish_report": {
          "type": "boolean",
          "description": "Create an unlisted, expiring public report link. Defaults to false."
        }
      }
    }
    arguments 16 lines
  • check_crawler_access reads unknown 22h ago

    Fetch robots.txt and a bounded public page through validated redirects, then inspect named-token path rules, final delivery, X-Robots-Tag, and HTML meta robots. Named-bot edge/WAF treatment remains unobservable.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Public site URL and path to evaluate (https://example.com/docs)"
        }
      }
    }
    arguments 12 lines
  • get_public_report reads unknown 22h ago

    Read the latest saved public scan report or bounded history using its opaque report id. Reports are only created after explicit opt-in and expire after 30 days.

    mcp-tool

    {
      "type": "object",
      "required": [
        "report_id"
      ],
      "properties": {
        "history": {
          "type": "boolean",
          "description": "Return saved snapshots newest first instead of only the latest snapshot."
        },
        "report_id": {
          "type": "string",
          "description": "Opaque report id returned by scan_url when publish_report is true."
        }
      }
    }
    arguments 16 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 dd8970fd491e9dce.

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

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.