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

ready4bots

https://ready4bots.com

Registry code: 947679726dbc3910

api record

Ready4Bots is a public, read-only index of businesses an agent can look up. search_businesses matches name, industry, tags, product keywords, and a few synonyms (shoes/sneakers, coffee/espresso, hotel/lodging). It ranks by relevance, then by R-level. Filters: category (channel or industry id), country, level (R0–R3, or R4 for the seal), min_level, action (search, book, order), audience (customer, seller, dev), and certified. get_business returns one listing, including level, status, certified, actions, and audience. search_businesses, get_business, and list_levels never change a listing.…

endpoint
https://ready4bots.com/mcp
door code
0fb5c23c9e167b84
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 ready4bots live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is ready4bots free to use?
Yes — the hub reached it with no key and no payment.
What tools does ready4bots have?
4 tools: check_website, get_business, list_levels, search_businesses.
Is ready4bots 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
888ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • 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
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
2 open 2 never probed 2 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_levels open 1h ago

    List Ready4Bots levels R0 through R4. The free check can award R0 through R3 only. R4 and certified require Ready4Bots verification.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • search_businesses open 1h ago

    Search the public Ready4Bots index. Free text matches name, industry, tags, product keywords, category, description, and domain, including synonyms such as shoes/sneakers, coffee/espresso, and hotel/lodging. Results are ranked by that relevance, then by published R-level. Filter by category (E-commerce, SaaS, or an industry id such as fashion-shoes), country, exact level (R0–R3 from a published test, R4 only for the certified seal), minimum level, action (search, book, or order), audience (customer, seller, or dev), and certified. The response includes totalIndexed, the size of the catalog, and indexSource. Each result includes level, status, certified, industry, channel, actions, audience, sourceUrl, and ready4botsUrl. A level is present only when a test recorded one. Unverified listings are never certified. The tool waits for the live providers table. indexSource is postgres when that read finishes, including when it returns no public row. indexSource is snapshot, with fallbackReason, only when the database cannot be reached. get_business reads the same catalog.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "level": {
          "enum": [
            "R0",
            "R1",
            "R2",
            "R3",
            "R4"
          ],
          "type": "string",
          "description": "Exact published level. R0–R3 are test levels. R4 is the certified seal only."
        },
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Page size. Default 20, max 50."
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "description": "Free text matched against name, industry, tags, product keywords, category, description, country, id, and domain. shoes matches sneakers, coffee matches espresso, hotel matches lodging."
        },
        "action": {
          "enum": [
            "search",
            "book",
            "order"
          ],
          "type": "string",
          "description": "Published action: search (product search with prices), book (reservation), or order (cart and checkout)."
        },
        "offset": {
          "type": "integer",
          "maximum": 10000,
          "minimum": 0,
          "description": "Number of matches to skip."
        },
        "country": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "Country code stored on the listing, for example DE or US."
        },
        "audience": {
          "enum": [
            "customer",
            "seller",
            "dev"
          ],
          "type": "string",
          "description": "customer when a customer action is published. seller and dev are not in this index and return no rows."
        },
        "category": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "Channel or industry id, for example SaaS, E-commerce, or coffee-food-drink."
        },
        "certified": {
          "type": "boolean",
          "description": "true keeps only the Ready4Bots certified seal. false drops sealed listings."
        },
        "min_level": {
          "enum": [
            "R0",
            "R1",
            "R2",
            "R3",
            "R4"
          ],
          "type": "string",
          "description": "Keep listings whose published level is at least this. Unscored listings are omitted."
        }
      }
    }
    arguments 79 lines
  • check_website unknown never probed

    Run the free Ready4Bots Bot-Ready check on a public http(s) URL. Scores R0 through R3 with the v0.1 checker. Never awards R4 and never sets certified. A guarantee hint returns status R4 candidate · not verified. The same check the website runs; a saved report gets a public result URL.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1,
          "description": "Public website URL to score."
        }
      }
    }
    arguments 15 lines
  • get_business unknown 1h ago

    Fetch one public listing by id, slug, domain, or website URL. The result includes level, status, certified (the seal), actions, audience, sourceUrl, and ready4botsUrl. Mystery test data and internal notes are not returned. Unverified levels are not certified.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "id": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Listing id, slug, domain, or website URL."
        },
        "domain": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Domain or website URL, if id is omitted."
        }
      }
    }
    arguments 18 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 947679726dbc3910.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/947679726dbc3910/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/947679726dbc3910/badge.svg)](https://brick.blue/agent/947679726dbc3910?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
1
ok
1
failed
0
success rate
100%
median latency
1,936ms
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
—

1 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.