Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ai.dataecho/mcp

REMOTE · DATAECHO.AI · SCANNED SEP 24

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

Available components

0 this week 77 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the ai.dataecho/mcp server?

ai.dataecho/mcp is a hosted endpoint at https://dataecho.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · dataecho.ai

# add to Claude Code
claude mcp add --transport http ai-dataecho-mcp 'https://dataecho.ai/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-dataecho-mcp": {
      "url": "https://dataecho.ai/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-dataecho-mcp": {
      "type": "http",
      "url": "https://dataecho.ai/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ai-dataecho-mcp]
url = "https://dataecho.ai/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-dataecho-mcp": {
      "type": "remote",
      "url": "https://dataecho.ai/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-dataecho-mcp --url 'https://dataecho.ai/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-dataecho-mcp:
    url: "https://dataecho.ai/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-dataecho-mcp": {
      "Transport": "http",
      "Url": "https://dataecho.ai/mcp"
    }
  }
}
# add to Vellum
assistant mcp add ai-dataecho-mcp -t streamable-http -u 'https://dataecho.ai/mcp'
// mcp.json
{
  "mcpServers": {
    "ai-dataecho-mcp": {
      "type": "http",
      "url": "https://dataecho.ai/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 24 Sept 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 26 Aug 26 77
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 24 Sept 2026 · Probed https://dataecho.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dataecho.ai CN=WE1,O=Google Trust Services,C=US 8 Aug 2026 6 Nov 2026 ECDSA 256 ECDSA-SHA256 66987356fed2f3c00e84980a7210918c
SANs: dataecho.ai, *.dataecho.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of dataecho.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
dataecho.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://dataecho.ai/mcp Unreachable
http (plaintext) http://dataecho.ai/mcp HTTPS enforced
MCP tools · 26 exposed · ~1,574 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
app_status ~54

Build/run status of a container app deployed via publish_site with a Dockerfile. Poll until status is `live` or `failed`.

NameTypeReqDescription
logsboolean–Include build logs
slugstringyesSite slug

No output schema declared.

No examples provided.

claim_site ~54

Make a previously-anonymous site permanent under the authenticated account (requires auth + the claimToken from publish_site).

NameTypeReqDescription
claimTokenstringyesClaim token returned by the anonymous publish
slugstringyesSite slug

No output schema declared.

No examples provided.

create_drive ~23

Create a new private drive.

NameTypeReqDescription
namestringyesDrive name

No output schema declared.

No examples provided.

delete_site ~34

Permanently delete an owned site. Irreversible — confirm with the user first.

NameTypeReqDescription
slugstringyesSite slug

No output schema declared.

No examples provided.

delete_variable ~22

Delete an account variable.

NameTypeReqDescription
namestringyesVariable name

No output schema declared.

No examples provided.

drive_delete_file ~39

Delete one file from a drive.

NameTypeReqDescription
drivestringyesDrive name or drv_… id
pathstringyesFile path

No output schema declared.

No examples provided.

drive_history ~36

Version timeline of a drive (every write is a restorable version).

NameTypeReqDescription
drivestringyesDrive name or drv_… id

No output schema declared.

No examples provided.

drive_list_files ~54

List files in a drive (by drive name or drv_… id), optionally under a path prefix.

NameTypeReqDescription
drivestringyesDrive name or drv_… id
prefixstring–Path prefix filter

No output schema declared.

No examples provided.

drive_move_file ~50

Move/rename a file inside a drive.

NameTypeReqDescription
drivestringyesDrive name or drv_… id
fromstringyesCurrent path
tostringyesNew path

No output schema declared.

No examples provided.

drive_read_file ~72

Read a file from a drive. Text comes back as utf-8 `content`; binary as `contentBase64`. Files over 1 MB are refused (use the skill scripts).

NameTypeReqDescription
drivestringyesDrive name or drv_… id
pathstringyesFile path in the drive

No output schema declared.

No examples provided.

drive_restore ~55

Restore a drive to a prior version (commits a new version; nothing is lost).

NameTypeReqDescription
drivestringyesDrive name or drv_… id
versionIdstringyesdv_… id from drive_history

No output schema declared.

No examples provided.

drive_revoke_token ~47

Revoke a drive share token.

NameTypeReqDescription
drivestringyesDrive name or drv_… id
tokenIdstringyesdtok_… id from drive_tokens

No output schema declared.

No examples provided.

drive_share ~120

Mint a scoped drive access token for another agent (perms read|write, optional path prefix + TTL like `7d`). The secret is returned ONCE.

NameTypeReqDescription
drivestringyesDrive name or drv_… id
labelstring–Human label for the token
pathPrefixstring–Restrict the token to this path prefix
permsstring–read (default) or write
ttlstring–Lifetime, e.g. 1h, 7d (omit for no expiry)

No output schema declared.

No examples provided.

drive_tokens ~37

List active share tokens of a drive (secrets are never shown again).

NameTypeReqDescription
drivestringyesDrive name or drv_… id

No output schema declared.

No examples provided.

drive_write_file ~117

Write/overwrite one file in a drive (ETag-safe: pass ifMatch to assert the version you read, otherwise the current version is used automatically).

NameTypeReqDescription
contentstring–UTF-8 text content
contentBase64string–Base64 content for binary files
contentTypestring–Optional MIME type
drivestringyesDrive name or drv_… id
ifMatchstring–Optional ETag precondition
pathstringyesDestination path in the drive

No output schema declared.

No examples provided.

get_site ~28

Full details + current file manifest of an owned site.

NameTypeReqDescription
slugstringyesSite slug

No output schema declared.

No examples provided.

list_drives ~18

List the authenticated account's private cloud drives.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_sites ~17

List all sites owned by the authenticated account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_variables ~33

List account variable NAMES (values are write-only — they are injected into proxy calls and container apps, never read back).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

platform_info ~33

DataEcho platform overview: what it can host, auth state of this connection, docs links. Call this first if unsure.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

publish_site ~252

Deploy files to a live URL. No slug → create a NEW site (works without auth; anonymous sites expire in 24h — always show the user the claimUrl). With slug → UPDATE that site (complete snapshot: send ALL files). A Dockerfile in the files makes it a server-side app (auth required; listen on process.env.PORT; persist under /data; poll app_status). Total payload ≤ 8 MB — for bigger sites use the dataecho skill scripts.

NameTypeReqDescription
claimTokenstring–Claim token — required to update an anonymous site without auth
descriptionstring–Viewer page description
filesarrayyesFiles to publish. Each file: { path, content (utf-8 text) OR contentBase64 (binary), contentType? }. The publish is a COMPLETE snapshot — omitted files are removed on update.
slugstring–Existing site slug to update (omit to create a new site)
spaboolean–Enable SPA fallback routing (serve index.html for unknown paths)
titlestring–Viewer page title (used when there's no index.html)
ttlSecondsnumber–Expiry for authenticated sites, in seconds

No output schema declared.

No examples provided.

request_login_code ~39

Start sign-in: email a one-time code to the user. Follow with verify_login_code.

NameTypeReqDescription
emailstringyesThe user's email address

No output schema declared.

No examples provided.

search_sites ~46

Full-text search across the authenticated account's sites (names, metadata, and text content).

NameTypeReqDescription
limitnumber–Max results (optional)
querystringyesSearch query

No output schema declared.

No examples provided.

set_variable ~89

Create/update a write-only account secret (uppercase name). Injected as env vars into container apps and as ${VAR} into proxy calls. Optionally pin which upstream hosts may receive it.

NameTypeReqDescription
allowedUpstreamsarray–Optional allow-list of upstream hosts
namestringyesUPPER_SNAKE_CASE variable name
valuestringyesSecret value (never readable back)

No output schema declared.

No examples provided.

update_site_metadata ~117

Patch site settings without redeploying: viewer title/description, SPA mode, TTL, password (string sets, null removes).

NameTypeReqDescription
descriptionstring–Viewer description
passwordstring–Password-gate the site; pass an empty string to REMOVE the password
slugstringyesSite slug
spaModeboolean–SPA fallback routing
titlestring–Viewer title
ttlSecondsnumber–Expiry in seconds (null-like 0 not allowed; omit to keep)

No output schema declared.

No examples provided.

verify_login_code ~88

Complete sign-in with the emailed code. Returns the apiKey ONCE — configure it as the `Authorization: Bearer <key>` header of this MCP connection (and/or save to ~/.artifact/credentials for the CLI scripts). Never echo it into chat.

NameTypeReqDescription
codestringyesThe one-time code from the email
emailstringyesSame email as request_login_code

No output schema declared.

No examples provided.

Common questions

What is the ai.dataecho/mcp server?

ai.dataecho/mcp is listed in the public MCP registry as ai.dataecho/mcp. Deploy files, sites, and Dockerfile apps to live URLs + private drives for agent memory. This page covers its hosted endpoint (https://dataecho.ai/mcp).

Is the ai.dataecho/mcp server safe to use?

ai.dataecho/mcp scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ai.dataecho/mcp server expose?

ai.dataecho/mcp exposes 26 tools: platform_info, request_login_code, verify_login_code, publish_site, claim_site, and 21 more. Their descriptions and schemas cost roughly 1,574 tokens of context every time the server is loaded.

Does the ai.dataecho/mcp server require authentication?

Its publisher declares no required credentials for ai.dataecho/mcp. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the ai.dataecho/mcp server still maintained?

ai.dataecho/mcp is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.