BotFriendly
REMOTE · WWW.BOTFRIENDLY.XYZ · SCANNED SEP 20
Directory of APIs, merchants, and tools AI agents can actually use.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1355 tokens (~193/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the BotFriendly MCP server?
BotFriendly is a hosted endpoint at https://www.botfriendly.xyz/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.botfriendly.xyz
claude mcp add --transport http xyz-botfriendly-botfriendly 'https://www.botfriendly.xyz/api/mcp'
{
"mcpServers": {
"xyz-botfriendly-botfriendly": {
"url": "https://www.botfriendly.xyz/api/mcp"
}
}
} {
"servers": {
"xyz-botfriendly-botfriendly": {
"type": "http",
"url": "https://www.botfriendly.xyz/api/mcp"
}
}
} [mcp_servers.xyz-botfriendly-botfriendly] url = "https://www.botfriendly.xyz/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-botfriendly-botfriendly": {
"type": "remote",
"url": "https://www.botfriendly.xyz/api/mcp",
"enabled": true
}
}
} openclaw mcp add xyz-botfriendly-botfriendly --url 'https://www.botfriendly.xyz/api/mcp' --transport streamable-http
mcp_servers:
xyz-botfriendly-botfriendly:
url: "https://www.botfriendly.xyz/api/mcp" {
"McpServers": {
"xyz-botfriendly-botfriendly": {
"Transport": "http",
"Url": "https://www.botfriendly.xyz/api/mcp"
}
}
} assistant mcp add xyz-botfriendly-botfriendly -t streamable-http -u 'https://www.botfriendly.xyz/api/mcp'
{
"mcpServers": {
"xyz-botfriendly-botfriendly": {
"type": "http",
"url": "https://www.botfriendly.xyz/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 0
- Tool “list_categories” rewrote its description, which is the text the model reads security
- “search_services” reworded the description of “category” cosmetic
- “submit_service” reworded the description of “category” cosmetic
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://www.botfriendly.xyz/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.botfriendly.xyz | CN=YR2,O=Let's Encrypt,C=US | 4 Sept 2026 | 3 Dec 2026 | RSA 2048 | SHA256-RSA | 55f1dbe74366585186ca1f887a6a4e7c6bb |
| SANs: www.botfriendly.xyz | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.botfriendly.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| botfriendly.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.botfriendly.xyz/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.botfriendly.xyz/api/mcp | HTTPS enforced | 308 | https://www.botfriendly.xyz/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_site ~200
Score how bot-friendly a website is (0-100). Fetches the site the way an agent would — no JavaScript, no cookies — and checks access (reachability, HTTPS, robots.txt, AI crawlers allowed, real 404s), content without JavaScript (H1, 500+ chars of raw text, metadata, JSON-LD), and machine discovery (llms.txt, sitemap, OpenAPI spec or ai-plugin.json), with evidence and fix advice per check. Set format to 'prompt' to instead get a ready-to-paste coding-agent prompt that fixes every failed finding. Rate limited to 6 checks per minute per caller; each check takes a few seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | json (default) returns the full scored report; prompt returns a markdown prompt for a coding agent covering every failed or partial finding |
| url | string | yes | Site to check (scheme optional, https assumed; public sites only) |
No output schema declared.
No examples provided.
get_featured ~30
Get site-wide featured/promoted services (max 3). These are paid placements clearly marked as ads.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_protocol_stats ~91
Get adoption stats for every protocol BotFriendly tracks: the machine-readable interfaces (MCP, OpenAPI) and the agent payment, authorization, and commerce protocols (x402, mpp, l402, ap2, tap, agent-pay, ace, acp, ucp, actp, icc). Each entry carries its sponsor, layer, spec URL, and how many listed services support it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_service ~59
Get full details for a specific service by its slug, including all protocol support, URLs, auth method, billing, and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Service slug (e.g. browserbase, anthropic-claude-api, firecrawl) |
No output schema declared.
No examples provided.
list_categories ~39
List every BotFriendly category with its id (the search_services category value), human label, aliases (older slugs still accepted), description and service count.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_services ~521
Search the BotFriendly directory for bot-friendly services, APIs, and tools that AI agents can use. Filter by category, payment/commerce protocol support (x402, MPP, L402, AP2, TAP, Agent Pay, ACE, ACP, UCP, ACTP, ICC), auth method, and more. Results may start with up to 3 promoted listings (paid ads) pinned to the top — site-wide ads on unfiltered searches, category ads on category searches — clearly marked with promoted:true and ad:true. Use promoted=false to exclude ads.
| Name | Type | Req | Description |
|---|---|---|---|
| accepts_mpp | boolean | – | Only services accepting MPP payments |
| accepts_x402 | boolean | – | Only services accepting x402 payments |
| auth_method | string | – | Filter by auth method |
| category | string | – | Category id: think (Models), see (Vision), hear-speak (Speech), create (Media), remember (Memory), search (Search), browse (Browsers), communicate (Messaging), execute (Compute), pay (Payments), shop… |
| has_mcp | boolean | – | Only services with MCP servers |
| min_score | number | – | Minimum bot-friendly score (1-5) |
| page | number | – | Page number (default 1) |
| promoted | boolean | – | Filter by promoted status: true for promoted only, false for organic only |
| protocol | array | – | Only services supporting ALL of these agent payment/commerce protocols. x402 (x402, Coinbase, x402 Foundation); mpp (Machine Payments Protocol, Stripe, Tempo); l402 (L402, Lightning Labs); ap2 (Agent… |
| query | string | – | Keyword search (Postgres websearch semantics: multiple words are ANDed, so a single distinctive keyword like 'scraping' matches more than a phrase like 'web scraping') |
| sort | string | – | Sort order (default: score) |
No output schema declared.
No examples provided.
submit_service ~333
Submit a service to the BotFriendly directory. There is no review queue: each interface URL must be on the service's own domain and is fetched during the call, and the listing publishes immediately if one answers. Every listing needs an icon — pass icon_url, or leave it out and the service's own site is checked for one.
| Name | Type | Req | Description |
|---|---|---|---|
| accepts_mpp | boolean | – | – |
| accepts_x402 | boolean | – | – |
| auth_method | string | – | Auth method |
| billing_model | string | – | – |
| category | string | yes | Category id (see list_categories) |
| contact_email | string | – | Contact email for verification |
| description | string | yes | Short description (max 120 chars) |
| has_mcp_server | boolean | – | – |
| has_openapi_spec | boolean | – | – |
| icon_base64 | string | – | Alternative to icon_url: the image inline, as a data: URI or bare base64. |
| icon_url | string | – | Link to the service's icon (PNG, JPEG, SVG or WebP, under 1MB). Fetched and re-hosted, downscaled to 512px. Omit it and the service's site is checked for one. |
| mcp_server_url | string | – | Required when has_mcp_server is true, and must be on the service's own domain. |
| name | string | yes | Service name |
| openapi_spec_url | string | – | Required when has_openapi_spec is true, and must be on the service's own domain. |
| tags | array | – | – |
| url | string | yes | Service URL |
No output schema declared.
No examples provided.
What is the BotFriendly MCP server?
BotFriendly is an MCP server listed in the public MCP registry as xyz.botfriendly/botfriendly. Directory of APIs, merchants, and tools AI agents can actually use. This page covers its hosted endpoint (https://www.botfriendly.xyz/api/mcp).
Is the BotFriendly MCP server safe to use?
BotFriendly scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BotFriendly MCP server expose?
BotFriendly exposes 7 tools: search_services, get_service, list_categories, get_featured, get_protocol_stats, and 2 more. Their descriptions and schemas cost roughly 1,273 tokens of context every time the server is loaded.
Does the BotFriendly MCP server require authentication?
No. We connected to BotFriendly without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BotFriendly MCP server still maintained?
BotFriendly is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.