mcp-registry/com.botrecipe/wake · v1.0.0
As of 2026-10-27 04:11 UTC, the Botrecipe Wake MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 13.3 hours.
Schedule wake-ups for AI agents that bring back their saved state and thread when they fire.
Point your MCP client at this streamable-http endpoint: https://wake.cloudforbots.com/mcp
4 of 4 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 →
2 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 →
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. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.botrecipe%2Fwake/fixes
{
"name": "cancel_wake",
"description": "Cancel a pending wake-up by wake_id. Call once without confirm to preview, then with confirm=true.",
"inputSchema": {
"type": "object",
"required": [
"wake_id"
],
"properties": {
"inbox": {
"type": "string",
"description": "Your private inbox name (12+ chars, keep it secret, reuse it every session). Optional if you send an API key: then the key is your inbox."
},
"confirm": {
"type": "boolean"
},
"wake_id": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}{
"name": "check_wakes",
"description": "Collect wake-ups that are due for your inbox (each returned once, with its saved state and thread ID) and list upcoming ones. Call this at the start of a session.",
"inputSchema": {
"type": "object",
"properties": {
"inbox": {
"type": "string",
"description": "Your private inbox name (12+ chars, keep it secret, reuse it every session). Optional if you send an API key: then the key is your inbox."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "schedule_wake",
"description": "Schedule a wake-up for your agent. At the time you pick, Agent Wake POSTs your saved state (notes, thread ID, next step) to your callback URL, or holds it for check_wakes. Use it so a later, fresh session picks up where this one stopped. Call once without confirm to preview what will be saved, show the user, then call again with confirm=true.",
"inputSchema": {
"type": "object",
"required": [
"when"
],
"properties": {
"when": {
"type": "string",
"description": "When to wake: \"in 30 minutes\", \"in 2 hours\", \"in 3 days\", or an ISO time like 2026-10-16T14:00:00Z. Between 1 minute and 365 days out."
},
"inbox": {
"type": "string",
"description": "Your private inbox name (12+ chars, keep it secret, reuse it every session). Optional if you send an API key: then the key is your inbox."
},
"state": {
"type": "object",
"description": "What your future session needs: goal, progress, next step, IDs. Free up to 8 KB, Pro up to 64 KB."
},
"confirm": {
"type": "boolean",
"description": "false or missing = preview only, nothing saved. true = save the wake."
},
"thread_id": {
"type": "string",
"description": "Optional conversation or task ID to resume."
},
"callback_url": {
"type": "string",
"description": "Optional public https URL to POST the wake to (for example your agent runner webhook). Without it, collect wakes with check_wakes."
},
"repeat_minutes": {
"type": "integer",
"description": "Optional. Repeat every N minutes after the first wake (free: 60+, Pro: 5+)."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}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/wake"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.botrecipe/wake"}) over MCP.
schedule_wake ~408 tokenscancel_wake ~124 tokenscheck_wakes ~119 tokensusage_and_upgrade ~56 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%2Fwake?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.botrecipe%2Fwake?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.botrecipe%2Fwake.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.botrecipe%2Fwake.svg :target: https://glimind.com/server/mcp-registry%2Fcom.botrecipe%2Fwake?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:90d7e736e185b7de…, first seen 2026-10-17, included at leaf 5414 of 77,293. Version history · verify what your client received.
Compare: most reliable productivity servers · most reliable communication servers · most reliable other 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-27 04:11 UTC, the Botrecipe Wake MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 13.3 hours.
Botrecipe Wake MCP server advertises 4 tools, including cancel_wake, check_wakes, schedule_wake, usage_and_upgrade.
Point your MCP client at this streamable-http endpoint: https://wake.cloudforbots.com/mcp
Glimind scanned all 4 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.