mcp-registry/xyz.botfriendly/botfriendly · v0.1.0
As of 2026-10-22 03:06 UTC, the Botfriendly MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 11 minutes.
Directory of APIs, merchants, and tools AI agents can actually use.
Claude Code
claude mcp add --transport http botfriendly-mcp-server https://mcp.botfriendly.xyz
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"botfriendly-mcp-server": {
"type": "http",
"url": "https://mcp.botfriendly.xyz"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
7 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~1,730 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 2 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fxyz.botfriendly%2Fbotfriendly/fixes
{
"name": "check_site",
"description": "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. R",
"inputSchema": {
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"description": "Site to check (scheme optional, https assumed; public sites only)"
},
"format": {
"enum": [
"json",
"prompt"
],
"type": "string",
"description": "json (default) returns the full scored report; prompt returns a markdown prompt for a coding agent covering every failed or partial finding"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_featured",
"description": "Get site-wide featured/promoted services (max 3). These are paid placements clearly marked as ads.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_protocol_stats",
"description": "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).",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/xyz.botfriendly/botfriendly"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/xyz.botfriendly/botfriendly"}) over MCP.
search_services ~923 tokenssubmit_service ~657 tokenscheck_site ~255 tokensget_protocol_stats ~147 tokensget_service ~94 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fxyz.botfriendly%2Fbotfriendly?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fxyz.botfriendly%2Fbotfriendly?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.botfriendly%2Fbotfriendly.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.botfriendly%2Fbotfriendly.svg :target: https://glimind.com/server/mcp-registry%2Fxyz.botfriendly%2Fbotfriendly?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b0af4bd1160a2eb7…, first seen 2026-10-17, included at leaf 14718 of 43,188. Version history · verify what your client received.
Compare: most reliable web servers · most reliable search servers · most reliable data servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 03:06 UTC, the Botfriendly MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 11 minutes.
Botfriendly MCP server advertises 7 tools, including check_site, get_featured, get_protocol_stats, get_service, list_categories.
Point your MCP client at this streamable-http endpoint: https://mcp.botfriendly.xyz
Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.