Deploy files, sites, and Dockerfile apps to live URLs + private drives for agent memory. Connect the official MCP MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.
Free to start · No credit card · No hosting needed
Real prompts you can type the moment it's connected — no setup, no docs to read.
“Use “platform_info”: DataEcho platform overview: what it can host, auth state of this connection, docs links. Call this first if unsure.”
“Use “request_login_code”: Start sign-in: email a one-time code to the user. Follow with verify_login_code.”
“Use “verify_login_code”: Complete sign-in with the emailed code. Returns the apiKey ONCE — configure it as the `Authorization: Bearer <key>` header of this MCP conne.”
“Use “publish_site”: 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 claimU.”
Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how MCP holds up.
Operated by MCP (dataecho.ai) at its documented MCP endpoint — not a third-party mirror or community re-host.
This server only exposes public data — no account and no credentials are involved when you connect.
gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.
If MCP adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.
Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.
Choose MCP in the gate directory. No sign-in needed.
MCP's tools are live in every AI client you've connected — with rules and logging built in.
Free to start · No credit card · No hosting needed
Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.
platform_info — DataEcho platform overview: what it can host, auth state of this connection, docs links. Call this first if unsure.
request_login_code — Start sign-in: email a one-time code to the user. Follow with verify_login_code.
verify_login_code — Complete sign-in with the emailed code. Returns the apiKey ONCE — configure it as the `Authorization: Bearer <key>` header of this MCP conne
publish_site — 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 claimU
claim_site — Make a previously-anonymous site permanent under the authenticated account (requires auth + the claimToken from publish_site).
list_sites — List all sites owned by the authenticated account.
search_sites — Full-text search across the authenticated account's sites (names, metadata, and text content).
get_site — Full details + current file manifest of an owned site.
+ 18 more tools once connected
https://dataecho.ai/mcpYes — MCP operates its own remote MCP server at dataecho.ai. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.
Add gate's gateway URL to your AI client once, then pick MCP in the directory. No account or sign-in is needed. From then on, MCP's tools are available in every client you've connected to gate.
No. MCP runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.
It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.
Yes — you can get started with gate for free and connect MCP in minutes. No credit card required.
Every server below works through the same gateway URL — connect once, add tools anytime.
Set up MCP in: Claude · Claude Code · ChatGPT · Cursor · VS Code