mcp-registry/com.b0tl1nk/directory · v1.0.0
As of 2026-10-26 18:19 UTC, the B0tl1nk Directory MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 22 minutes.
Search and list applications for AI agents. Remote MCP on b0tl1nk.com.
Point your MCP client at this streamable-http endpoint: https://b0tl1nk.com/mcp
6 of 6 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 →
4 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 →
Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. 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. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.b0tl1nk%2Fdirectory/fixes
{
"name": "delete_app",
"description": "Soft-delete a listing you own.",
"inputSchema": {
"type": "object",
"required": [
"id",
"api_key"
],
"properties": {
"id": {
"type": "string",
"description": "App id."
},
"api_key": {
"type": "string",
"description": "Bearer token."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}{
"name": "get_app",
"description": "Get one listing by opaque id, including how_to and the signed payload.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "App id from search_apps, e.g. app_…"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "publish_app",
"description": "List an app. Auto-publishes. Requires api_key plus signature of the payload string.",
"inputSchema": {
"type": "object",
"required": [
"api_key",
"payload",
"signature"
],
"properties": {
"api_key": {
"type": "string",
"description": "Bearer token from register_publisher."
},
"payload": {
"type": "string",
"description": "JSON string of listing fields. Sign these exact bytes."
},
"signature": {
"type": "string",
"description": "Ed25519 signature of payload."
}
}
},
"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.b0tl1nk/directory"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.b0tl1nk/directory"}) over MCP.
register_publisher ~149 tokenspublish_app ~131 tokensupdate_app ~126 tokenssearch_apps ~100 tokensdelete_app ~69 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.b0tl1nk%2Fdirectory?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.b0tl1nk%2Fdirectory?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.b0tl1nk%2Fdirectory.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.b0tl1nk%2Fdirectory.svg :target: https://glimind.com/server/mcp-registry%2Fcom.b0tl1nk%2Fdirectory?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:686f97c3be377b0d…, first seen 2026-10-17, included at leaf 14885 of 74,681. Version history · verify what your client received.
Compare: most reliable other servers · most reliable retrieval servers · most reliable security 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-26 18:19 UTC, the B0tl1nk Directory MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 22 minutes.
B0tl1nk Directory MCP server advertises 6 tools, including delete_app, get_app, publish_app, register_publisher, search_apps.
Point your MCP client at this streamable-http endpoint: https://b0tl1nk.com/mcp
Glimind scanned all 6 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.