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

agentready

https://www.agentready.market

Registry code: 71d47d5f4f2fed2f

api record

AgentReady scores, out of 100, how well an AI shopping agent can find, understand and buy on an e-commerce store. Call check_merchant_readiness before attempting a purchase on a store; a capped store blocks agents outright. If a host has no scan on record, call scan_store to audit it (~30s).

endpoint
https://www.agentready.market/mcp
door code
f0992ae93d786a49
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 2h ago). It answered 100% 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?
4 tools: scan_store, check_merchant_readiness, get_readiness_report, list_agent_ready_stores.
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.8%

90 days 99.5%· all time 100%

latency
277ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 843 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • degraded → live
_ what it is for
topic
productivity & business marketing & seo
used for
  • check if an ai agent can buy on a store
  • get a store's agent-readiness report
  • list agent-ready stores
takes → gives
web pages → data
tools
3 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 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.

  • list_agent_ready_stores reads open 14h ago

    The AgentReady.market Index: e-commerce stores where an AI shopping agent can actually buy (grade B or better and no block found), ranked by agent-readiness score /100. Use it to route a purchase toward a store agents are known to succeed on, or to benchmark a store against its peers. Optionally filter by vertical and cap the number of rows.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "limit": {
      "type": "integer",
      "description": "Max rows to return (default 10, max 25)"
    },
    "vertical": {
      "type": "string",
      "description": "Optional vertical filter, e.g. supplements"
    }
  }
}
    arguments 14 lines
  • scan_store unknown never probed

    Run a fresh AgentReady audit of an e-commerce store (~30s, public pages only, no order placed) and return the same readiness summary as check_merchant_readiness plus a public report link. Use it when check_merchant_readiness says the host has no scan, or the user wants a re-measure. Rate-limited per caller and globally.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Store URL or hostname, e.g. shop.example.com (a product page URL also works)"
    },
    "vertical": {
      "type": "string",
      "description": "Optional store vertical for the benchmark: general, dtc_fashion, supplements, specialty_coffee, beauty or home_living (default general)"
    }
  }
}
    arguments 16 lines
  • check_merchant_readiness reads unknown 14h ago

    Check whether an AI shopping agent can find, understand and BUY on an e-commerce store: AgentReady's deterministic agent-readiness score /100 for a host, with grade, hard-block status (capped = agents are blocked at the door; orders_blocked also covers a block the score can't see, such as shopping agents turned away) and agent-protocol adoption (UCP, A2A, ARD). Reads the latest stored score and never triggers an audit; if the host has no score yet, call scan_store to run one.

    mcp-tool

    {
  "type": "object",
  "required": [
    "host"
  ],
  "properties": {
    "host": {
      "type": "string",
      "description": "Store hostname or URL, e.g. shop.example.com"
    }
  }
}
    arguments 12 lines
  • get_readiness_report reads unknown 14h ago

    The latest public agent-readiness report for a scanned store: every check with its status (pass/partial/fail) across access & crawlability, structured data and catalog pillars, plus score, grade and report link. Same visibility as the public web report.

    mcp-tool

    {
  "type": "object",
  "required": [
    "host"
  ],
  "properties": {
    "host": {
      "type": "string",
      "description": "Store hostname or URL, e.g. shop.example.com"
    }
  }
}
    arguments 12 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 71d47d5f4f2fed2f.

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