Skip to content
External endpointresponds

mcp

Deploy files, sites, and Dockerfile apps to live URLs + private drives for agent memory.

Endpoint URL
https://dataecho.ai/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:01 AM UTC
Check
MCP initialize · 8s limit
Latency
588 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
ai.dataecho/mcp

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
dataecho
Version
1.0.0
Capability keys
tools
Tool names
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
Instructions excerpt

DataEcho hosts what agents build: publish_site deploys files/sites/apps to a live URL (anonymous works — 24h expiry, ALWAYS show the user the claimUrl), drives are private versioned cloud storage. Authenticate by sending the platform API key as `Authorization: Bearer <key>` (get one via request_login_code → verify_login_code). Container apps: include a Dockerfile, must listen on process.env.PORT, persist under /data, poll app_status. Large folders: prefer the dataecho skill (npx skills add mohocp/dataecho).

Reported Aug 17, 2026, 05:01 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 398ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 813ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 514ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 588ms
Back to MCP directory