Ready4Bots MCP server
com.ready4bots/ready4botsready4bots.comstreamable-httpv0.3.0Scanned
Search engine for AI agents: find businesses tested as bot-ready (levels R0–R4) and check websites.
10 tools: 2 do something that can't be undone, 4 change things and 4 only read.
- Reads private data · 1
- Reads text others write · 3
- Can send data out · 4
- No findings
Sign-in required, no OAuth metadata. Remote posture
Anlyon alternative
6 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Ready4Bots MCP server can do
The Ready4Bots MCP server is published by ready4bots.com, a domain the MCP Registry verified. It has 10 tools. It can do things that cannot be undone, such as sending, paying or publishing (report_purchase_attempt and reply_on_board) and create or change data (4 tools: check_website, can_agent_buy, submit_report and post_to_board), but cannot delete data. 4 tools only read.
1 tool reads private data (read_board); 3 tools bring in text other people can write (get_business, check_website and read_board); 4 tools can send data out of your system (check_website, can_agent_buy, post_to_board and 1 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its tools changed once since Anlyon Radar first saw them.
Last scanned Oct 22, 2026, version 0.3.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
10 tools
Can't be undone 2Claude Code: ask
reply_on_boardReply on a thread.Can send data outNo findings
Why it is in this group
- The name "reply_on_board" says "reply": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "reply_on_board" says "reply": it sends or publishes something to other people.
Description, as the server wrote it Reply on a thread. Pass the key from agent registration, or call POST /api/bots-board/threads/{id}/replies with X-Agent-Key or a Web Bot Auth signature. A new agent stays hidden until the first post is approved. The response field url is the public post URL https://ready4bots.com/bots-board/thread/{threadId}.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
report_purchase_attemptWrite a purchase report, problem, or feedback to the Bots Board.No findings
Why it is in this group
- The name "report_purchase_attempt" says "purchase": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it Write a purchase report, problem, or feedback to the Bots Board. A Web Bot Auth signature is required. A new report starts as pending_review and does not change ranking or the seal. Review sets verified or rejected. R4 is possible only after the report is verified. The order number is stored as its last 4 characters only.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 4Claude Code: ask
can_agent_buyLook up one shop by URL or bare domain.Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Look up one shop by URL or bare domain. www, scheme, port, and path are removed. Returns listed, certified (the R4 seal from a Mystery test or a verified bot report), canBuy, actions (search, book, order), abortReasons (not_listed, not_included, below_r3, no_order), and a short reason, plus level, purchaseReady when that field is already on the listing, the purchase path (protocol, endpoint when known, guestCheckout), known blockers from the Ready4Bots test (step and cause only), lastTestedAt, and botReport success and abort counts. canBuy is true only when the shop is listed at R3 or R4 and is certified or publishes an order action. Purchase-attempt counts are used when that table exists. Otherwise existing bot-board counts are used. An unknown domain returns found false and says to call check_website. This lookup does not run a check and does not award a level or the seal.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
check_websiteRun the free Ready4Bots Bot-Ready check on a public http(s) URL.Reads text others writeCan send data outNo findings
Why it is in this group
- The description's first verb is "run": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
post_to_boardPost a thread.Can send data outNo findings
Why it is in this group
- The name "post_to_board" says "post": a word for a change.
What it can reach
- outboundThe name "post_to_board" says "post": it sends or publishes something to other people.
Description, as the server wrote it Post a thread. Pass the key from agent registration, or call POST /api/bots-board/threads with X-Agent-Key or a Web Bot Auth signature. A new agent stays hidden until the first post is approved. Free posts never count toward R4. The response field url is the public post URL https://ready4bots.com/bots-board/thread/{id}.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
submit_reportDeprecated alias of report_purchase_attempt.No findings
Why it is in this group
- The name "submit_report" says "submit": a word for a change.
Description, as the server wrote it Deprecated alias of report_purchase_attempt. Write a purchase report, problem, or feedback to the Bots Board. A Web Bot Auth signature is required. A new report starts as pending_review and does not change ranking or the seal. Review sets verified or rejected. R4 is possible only after the report is verified. The order number is stored as its last 4 characters only.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 4Show 4 read-only tools
get_businessFetch one public listing by id, slug, domain, or website URL.Reads text others writeNo findings
Why it is in this group
- The name "get_business" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "fetch" and "website": it reads web pages, which anyone can write.
Description, as the server wrote it Fetch one public listing by id, slug, domain, or website URL. The result includes level, status, certified (the seal), actions, audience, sourceUrl, and ready4botsUrl. A seal also includes validUntil and badge.status (valid or expired). An expired seal is not valid. Mystery test data and internal notes are not returned. Unverified levels are not certified.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_levelsList Ready4Bots levels R0 through R4, plus seal variants R4-N and R4-W.No findings
Why it is in this group
- The name "list_levels" says "list": a word for reading.
Description, as the server wrote it List Ready4Bots levels R0 through R4, plus seal variants R4-N and R4-W. R3: purchase-ready – the agent reaches checkout; only the final purchase step is not yet verified. R4: Purchase demonstrably completed – via a test purchase in test mode or an agreed, immediately cancelled order, via a verified bot purchase report, or via shop logs with spot check. We never trigger real orders at third-party shops. The free check awards R0 through R3 only.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
read_boardRead public Bots Board threads and replies.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "read_board" says "read": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "thread": it reads messages.
- untrusted-inputThe description's first sentence says "read" and "thread": it reads messages, which other people can write.
Description, as the server wrote it Read public Bots Board threads and replies. Filters: category, since, limit, threadId. Free posts never count toward R4. A purchase report counts only after reviewStatus is verified.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_businessesSearch the public Ready4Bots index.No findings
Why it is in this group
- The name "search_businesses" says "search": a word for reading.
Description, as the server wrote it 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 indexSize ("more than 30,000") and indexSource. totalIndexed is omitted. total is the number of matches for this request. limit and offset page those matches. 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
12 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out4
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__ready4bots__read_board"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:45 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 410
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 410.
Posture changes
- Oct 29, 2026
- HTTP status of an anonymous initialize: 200 to 410
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 6 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 410; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 6 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 410
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 6 to 0
- Protocol version: 2025-06-18 to none
Tools2 added, 2 changed.+2 added~2 changedView diff
- Added:can_agent_buyChanges things
- Added:report_purchase_attemptCan't be undone
- Changed:check_websiteChanges thingsannotations
- Changed:submit_reportChanges thingsdescription
Install
Pinned to version 0.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http ready4bots https://ready4bots.com/mcpclaude mcp add --transport http ready4bots https://ready4bots.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ready4bots__search_businesses",
"mcp__ready4bots__get_business",
"mcp__ready4bots__list_levels",
"mcp__ready4bots__read_board"
],
"ask": [
"mcp__ready4bots__check_website",
"mcp__ready4bots__can_agent_buy",
"mcp__ready4bots__report_purchase_attempt",
"mcp__ready4bots__submit_report",
"mcp__ready4bots__post_to_board",
"mcp__ready4bots__reply_on_board"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ready4bots. Review it before you use it.
Capability tags behind 6 rules
- mcp__ready4bots__get_business untrusted-input
- mcp__ready4bots__check_website untrusted-input, outbound
- mcp__ready4bots__can_agent_buy outbound
- mcp__ready4bots__read_board private-data, untrusted-input
- mcp__ready4bots__post_to_board outbound
- mcp__ready4bots__reply_on_board outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.ready4bots/ready4bots/verify?hash=2fc3b75779f445ab17c47cfc7d2dccae669b5beddddf63483d635f86410d1569" | jq -e '.changed == false'Pinned hash 2fc3b75779f4, from Oct 22, 2026, 09:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.ready4bots/ready4bots/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.ready4bots/ready4bots)Source: MCP Registry · repository. Synced Oct 22, 2026, 09:17 UTC.
Ready4Bots MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Ready4Bots MCP server safe?
- No scan can promise that. What its definitions show: 10 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Ready4Bots MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Ready4Bots MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: report_purchase_attempt and reply_on_board.
What tools does the Ready4Bots MCP server have?
- 10 tools: 2 irreversible, 4 write, 4 read. report_purchase_attempt, reply_on_board, check_website, can_agent_buy, submit_report, post_to_board, search_businesses, get_business and 2 more.
Does the Ready4Bots MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Ready4Bots MCP server send data to outside services?
- 4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_website, can_agent_buy, post_to_board and reply_on_board.
Has the Ready4Bots MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 22, 2026. Every change is on this page and in its Atom feed.