mcp-registry/ai.dataecho/mcp · v1.0.0
As of 2026-10-26 17:06 UTC, the Dataecho 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 6 outages in 90 days, with a median recovery of 4 minutes.
Deploy files, sites, and Dockerfile apps to live URLs + private drives for agent memory.
Point your MCP client at this streamable-http endpoint: https://dataecho.ai/mcp
26 of 26 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 →
10 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. All of them as JSON: /v1/readiness/mcp-registry%2Fai.dataecho%2Fmcp/fixes
{
"name": "app_status",
"description": "Build/run status of a container app deployed via publish_site with a Dockerfile. Poll until status is `live` or `failed`.",
"inputSchema": {
"type": "object",
"required": [
"slug"
],
"properties": {
"logs": {
"type": "boolean",
"description": "Include build logs"
},
"slug": {
"type": "string",
"description": "Site slug"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "create_drive",
"description": "Create a new private drive.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "Drive name"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "delete_site",
"description": "Permanently delete an owned site. Irreversible — confirm with the user first.",
"inputSchema": {
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"description": "Site slug"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": 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/ai.dataecho/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ai.dataecho/mcp"}) over MCP.
publish_site ~505 tokensupdate_site_metadata ~200 tokensdrive_write_file ~199 tokensdrive_share ~179 tokensset_variable ~165 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%2Fai.dataecho%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fai.dataecho%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.dataecho%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.dataecho%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fai.dataecho%2Fmcp?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:996c4876064c4efb…, first seen 2026-10-17, included at leaf 10340 of 74,311. Version history · verify what your client received.
Compare: most reliable devops servers · most reliable web servers · most reliable files servers · most reliable data 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-26 17:06 UTC, the Dataecho 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 6 outages in 90 days, with a median recovery of 4 minutes.
Dataecho MCP server advertises 26 tools, including app_status, claim_site, create_drive, delete_site, delete_variable.
Point your MCP client at this streamable-http endpoint: https://dataecho.ai/mcp
Glimind scanned all 26 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.