mcpbeat

Ejec2 MCP Server

mx.com.elcheff.portal/ejec2
not responding

Ejec2 is listed as active in the registry but did not answer our last check.

MCP server para El Cheff - punto de venta para restaurantes

Uptime history 40 hours of history · worst hour 0%
40 hours agonow
0.0%
Uptime 24h
0 of 91 checks
—
Tools
hidden behind auth
1789 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

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

Endpoints

URLTransportStateLatencyChecked
https://portal.elcheff.com.mx/mcp streamable-http answering 1789 ms 13 min ago

Ejec2 — questions

Answers built from our own checks of this server.

Is Ejec2 working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 1789 ms. The bar chart above shows every period we have measured.
The registry lists Ejec2 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 Ejec2?
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 Ejec2 need an API key?
No. Ejec2 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.