mcp-registry/dev.echorelay/management · v1.15.0
As of 2026-10-19 16:19 UTC, the Echorelay Management MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 24 outages in 90 days, with a median recovery of 3 minutes.
A managed runtime for custom API integrations. Manage lines, endpoints, keys, logs and DLQ via MCP.
Claude Code
claude mcp add --transport http echorelay-management-mcp-server https://mcp.echorelay.dev
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"echorelay-management-mcp-server": {
"type": "http",
"url": "https://mcp.echorelay.dev"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
3 tool definition(s) exceed ~1,200 tokens each (largest: dry_run_endpoint, ~5,937).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~15,721 tokens every session. How to fix →
80 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
20 parameter(s) across 10 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 →
Loading this server's tool list costs an agent ~31,427 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
Handshake + tools/list takes ~2,301 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 →
In the last 30 days: 0 tool(s) removed and 15 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 →
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/dev.echorelay/management"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/dev.echorelay/management"}) over MCP.
dry_run_endpoint ~5,937 tokensupdate_endpoint ~5,842 tokenscreate_endpoint ~5,742 tokenscreate_credential ~771 tokensgenerate_line_draft ~557 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%2Fdev.echorelay%2Fmanagement?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fdev.echorelay%2Fmanagement?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.echorelay%2Fmanagement.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.echorelay%2Fmanagement.svg :target: https://glimind.com/server/mcp-registry%2Fdev.echorelay%2Fmanagement?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:16de1bb69f155f30…, first seen 2026-10-17, included at leaf 9843 of 27,574. Version history · verify what your client received.
Compare: most reliable devops servers · most reliable files servers · most reliable productivity servers · most reliable other servers · most reliable security 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-19 16:19 UTC, the Echorelay Management MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 24 outages in 90 days, with a median recovery of 3 minutes.
Echorelay Management MCP server advertises 80 tools, including activate_line, archive_project, cancel_line_publish, cancel_subscription, change_plan.
Point your MCP client at this streamable-http endpoint: https://mcp.echorelay.dev
Glimind scanned all 80 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.