mcp-registry/com.botrecipe/recipes · v1.0.0
As of 2026-10-25 22:42 UTC, the Botrecipe Recipes MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 25.4 hours.
Search and read 263 real AI bot setups: steps, what worked, what failed. Full pack $7.
Claude Code
claude mcp add --transport http botrecipe-recipes-mcp-server https://botrecipe.com/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"botrecipe-recipes-mcp-server": {
"type": "http",
"url": "https://botrecipe.com/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
5 parameter(s) across 3 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 →
3 of 3 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 →
In the last 30 days: 1 tool(s) removed and 1 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 →
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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.botrecipe%2Frecipes/fixes
{
"name": "get_recipe",
"description": "Get one full recipe by id from search_recipes (free). Needs an email: pass `email` here, ?email= on the MCP URL, or an X-Email header. Use your human's email if they agree. Returns the full recipe and its next_step tool.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string"
},
"email": {
"type": "string",
"description": "your (or your human's) email address"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "list_directory",
"description": "List MCP servers and bots in the botrecipe.com directory (seeded from the official MCP Registry, moderated). Optional filters: query, kind (mcp|bot), category.",
"inputSchema": {
"type": "object",
"properties": {
"kind": {
"enum": [
"mcp",
"bot"
],
"type": "string"
},
"query": {
"type": "string"
},
"category": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "search_recipes",
"description": "Search 579 free bot recipes (steps, prompt, what to watch). Returns id, title, summary, url, next_step.",
"inputSchema": {
"type": "object",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 25,
"minimum": 1
},
"query": {
"type": "string",
"description": "words to match"
}
}
},
"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/com.botrecipe/recipes"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.botrecipe/recipes"}) over MCP.
get_recipe ~119 tokenslist_directory ~97 tokenssearch_recipes ~90 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%2Fcom.botrecipe%2Frecipes?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.botrecipe%2Frecipes?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.botrecipe%2Frecipes.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.botrecipe%2Frecipes.svg :target: https://glimind.com/server/mcp-registry%2Fcom.botrecipe%2Frecipes?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:e6fa24128a369919…, first seen 2026-10-17, included at leaf 10244 of 69,035. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable search 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-25 22:42 UTC, the Botrecipe Recipes MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 25.4 hours.
Botrecipe Recipes MCP server advertises 3 tools, including get_recipe, list_directory, search_recipes.
Point your MCP client at this streamable-http endpoint: https://botrecipe.com/api/mcp
Glimind scanned all 3 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.