Home / MCP registry index / ai.dataecho/mcp
ai.dataecho/mcp
ai.dataecho/mcp in the official MCP registry.
Endpoint https://dataecho.ai/mcp. Source: github.com/mohocp/dataecho.
The registry describes it as: Deploy files, sites, and Dockerfile apps to live URLs + private drives for agent memory.
We read its 26 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
platform_info request_login_code verify_login_code publish_site claim_site list_sites search_sites get_site update_site_metadata delete_site app_status list_drives create_drive drive_list_files drive_read_file drive_write_file drive_delete_file drive_move_file drive_share drive_tokens drive_revoke_token drive_history drive_restore list_variables set_variable delete_variable
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-dataecho-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.