mcpbeat

Ecwid MCP Server

io.usefulapi/ecwid
not responding

Ecwid is listed as active in the registry but did not answer our last check. Last commit 1 Aug 2026.

Read store products, orders, customers, categories and coupons; adjust inventory and update orders.

Uptime history 43 hours of history · worst hour 0%
43 hours agonow
30.4%
Uptime 24h
28 of 92 checks
Tools
hidden behind auth
173 ms
Response time
average over 24h
0
Stars
last commit 1 Aug 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add ecwid --transport http https://ecwid.usefulapi.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ecwid": {
      "url": "https://ecwid.usefulapi.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.ecwid]
url = "https://ecwid.usefulapi.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ecwid": {
      "url": "https://ecwid.usefulapi.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "ecwid": {
      "url": "https://ecwid.usefulapi.io/mcp"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://ecwid.usefulapi.io/mcp streamable-http answering 57 ms 0 min ago

Ecwid — questions

Answers built from our own checks of this server.

Is Ecwid working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 28 of 92 checks got a reply (30.4%), average response time 173 ms. The bar chart above shows every period we have measured.
The registry lists Ecwid as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Ecwid?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Ecwid need an API key?
No. Ecwid completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.
How fast is Ecwid?
It answers our handshake in 173 ms on average, which is faster than 69% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Ecwid open source?
Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.