BotFriendly
REMOTE · MCP.BOTFRIENDLY.XYZ
Directory of APIs, merchants, and tools AI agents can actually use.
Available components
Last scanned (21 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
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 Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1619 tokens (~231/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% 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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Oct 26 +1
- Stability: 0.97 → pass security
- 7 Oct 26 0
- Tool “submit_service” rewrote its description, which is the text the model reads security
- “submit_service” added an optional parameter “api_url” cosmetic
- “submit_service” added an optional parameter “has_api” cosmetic
- “submit_service” reworded the description of “mcp_server_url” cosmetic
- “submit_service” reworded the description of “openapi_spec_url” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 25 Sept 26 0
First indexed and scored.
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 21 Nov 2026 · Probed https://mcp.botfriendly.xyz
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.botfriendly.xyz | CN=YR2,O=Let's Encrypt,C=US | 24 Sept 2026 | 23 Dec 2026 | RSA 2048 | SHA256-RSA | 6f305c7bb82dbbf44aaa72a67c7b0b1bb3e |
| SANs: mcp.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 mcp.botfriendly.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | DS published | 3599, 18130 | 8, 8 | Verified |
| botfriendly.xyz. | No DS | 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://mcp.botfriendly.xyz | Verified | 200 | |
| http (plaintext) | http://mcp.botfriendly.xyz | HTTPS enforced | 308 | https://mcp.botfriendly.xyz/ |
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 ~127
Get every protocol on botfriendly.xyz/protocols with adoption stats: how agents call a service and prove who sent them (MCP, OpenAPI, A2A, XAA) 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 count — how many listed services support it, or null for protocols that aren't a listing attribute (A2A, XAA).
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 ~594
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) |
| no_human | boolean | – | Only services an agent can start using with no human setting up a key: probe-backed — its own (non-documentation) MCP server lists its tools to an unauthenticated client and the service needs no key… |
| 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 ~488
Submit a service to the BotFriendly directory. There is no review queue: each interface URL must be on the service's own domain, or linked from the service's own site, and is fetched during the call; the listing publishes immediately if its MCP server, OpenAPI spec or API completes a handshake — one of has_mcp_server, has_openapi_spec or has_api is required; llms.txt, skill files and feeds only add badges. The url must be the product, not an article (/blog/, /news/ and similar are rejected), and a domain can add at most 2 listings a day and 3 in total. 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 | – | – |
| api_url | string | – | Required when has_api is true: the API's base URL (api.example.com, or a path under /api or /v1). It must answer in JSON. On the service's own domain, or linked from its site. |
| 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_api | boolean | – | – |
| 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. On the service's own domain, or linked from its site. |
| name | string | yes | Service name |
| openapi_spec_url | string | – | Required when has_openapi_spec is true. On the service's own domain, or linked from its site. |
| tags | array | – | – |
| url | string | yes | Service URL |
No output schema declared.
No examples provided.
How do I install the BotFriendly MCP server?
BotFriendly is a hosted endpoint at https://mcp.botfriendly.xyz/, 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 · mcp.botfriendly.xyz
claude mcp add --transport http xyz-botfriendly-botfriendly 'https://mcp.botfriendly.xyz/'
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://mcp.botfriendly.xyz).
Is the BotFriendly MCP server safe to use?
BotFriendly scores 77 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,537 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the BotFriendly MCP server?
VerifyMCP ran 12 checks on BotFriendly, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about BotFriendly: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.