mcp-registry/com.botrecipe/vault · v1.0.0
As of 2026-10-25 15:12 UTC, the Botrecipe Vault MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 25.5 hours.
Scoped login vault: your bot signs in to sites without ever seeing the password.
Claude Code
claude mcp add --transport http botrecipe-vault-mcp-server https://vault.cloudforbots.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"botrecipe-vault-mcp-server": {
"type": "http",
"url": "https://vault.cloudforbots.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
11 of 11 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 →
9 parameter(s) across 5 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 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 →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. 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. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.botrecipe%2Fvault/fixes
{
"name": "create_bot_key",
"description": "Owner only. Make a per-bot key (vk_...) that can only open sessions on the logins you name. Shown once; we store only its hash. Revoke any time with revoke_bot_key.",
"inputSchema": {
"type": "object",
"required": [
"label",
"logins"
],
"properties": {
"label": {
"type": "string",
"description": "Which bot, e.g. \"invoice-bot\"."
},
"logins": {
"type": "array",
"items": {
"type": "string"
},
"description": "Names of saved logins this bot may use."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "delete_login",
"description": "Owner only. Delete a saved login, end its open sessions and remove it from every bot key.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}{
"name": "list_logins",
"description": "List saved logins (name, domain, scope, sessions today; never secrets). With your owner key it also lists bot keys. A bot key only sees the logins it was granted.",
"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/com.botrecipe/vault"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.botrecipe/vault"}) over MCP.
save_login ~425 tokensopen_session ~337 tokenssession_fetch ~139 tokenscreate_bot_key ~130 tokensaudit_log ~75 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%2Fvault?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.botrecipe%2Fvault?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.botrecipe%2Fvault.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.botrecipe%2Fvault.svg :target: https://glimind.com/server/mcp-registry%2Fcom.botrecipe%2Fvault?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:1d857e1d5b995f61…, first seen 2026-10-17, included at leaf 1066 of 66,923. Version history · verify what your client received.
Compare: most reliable security servers · most reliable browser servers · most reliable other servers · most reliable productivity 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 15:12 UTC, the Botrecipe Vault MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 25.5 hours.
Botrecipe Vault MCP server advertises 11 tools, including audit_log, create_bot_key, delete_login, end_session, list_logins.
Point your MCP client at this streamable-http endpoint: https://vault.cloudforbots.com/mcp
Glimind scanned all 11 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.