mcp-registry/io.github.coburn2716/directree-mcp · v1.0.0
As of 2026-10-20 17:37 UTC, the Coburn2716 Directree MCP server is up with a Glimind reliability score of 97/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 4 minutes.
Search 5000+ software tools with structured, labelled facts. No pay-to-rank.
Claude Code
claude mcp add --transport http coburn2716-directree-mcp-server https://www.directree.io/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"coburn2716-directree-mcp-server": {
"type": "http",
"url": "https://www.directree.io/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
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 →
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 →
Handshake + tools/list takes ~2,067 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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.coburn2716%2Fdirectree-mcp/fixes
{
"name": "compare_tools",
"description": "Compare 2-4 tools side by side using directree's structured facts.",
"inputSchema": {
"type": "object",
"required": [
"slugs"
],
"properties": {
"slugs": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 4,
"minItems": 2,
"description": "Array of 2-4 tool slugs to compare"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_tool",
"description": "Get full structured facts for one tool by its directree slug.",
"inputSchema": {
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"description": "The tool slug (e.g. 'notion', 'linear')"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "list_categories",
"description": "List all software categories in the directree directory with tool counts.",
"inputSchema": {
"type": "object",
"required": [],
"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/io.github.coburn2716/directree-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.coburn2716/directree-mcp"}) over MCP.
search_tools ~135 tokenscompare_tools ~85 tokensget_tool ~69 tokenslist_categories ~50 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%2Fio.github.coburn2716%2Fdirectree-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.coburn2716%2Fdirectree-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.coburn2716%2Fdirectree-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.coburn2716%2Fdirectree-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.coburn2716%2Fdirectree-mcp?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:7d643c29875661c6…, first seen 2026-10-17, included at leaf 9820 of 34,175. Version history · verify what your client received.
Compare: most reliable comparison servers · most reliable retrieval servers · 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-20 17:37 UTC, the Coburn2716 Directree MCP server is up with a Glimind reliability score of 97/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 4 minutes.
Coburn2716 Directree MCP server advertises 4 tools, including compare_tools, get_tool, list_categories, search_tools.
Point your MCP client at this streamable-http endpoint: https://www.directree.io/api/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.