mcpbeat

Ecosystem Aec Regulatory MCP Server

io.github.carruda-Global/ecosystem-aec-regulatory
not responding

Ecosystem Aec Regulatory is listed as active in the registry but did not answer our last check.

NR-1 psychosocial risk, LGPD, whistleblower, pay equity & anti-corruption tools (Brazil)

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 39 hours of history · worst hour 0%
39 hours agonow
0.0%
Uptime 24h
0 of 91 checks
—
Tools
hidden behind auth
199 ms
Response time
average over 24h
open, no key
Access
sse

Connect this server

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

run in your terminal
claude mcp add ecosystem-aec-regulatory --transport http https://engenheiro-producao-ai.onrender.com/mcp/regulatory/sse
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ecosystem-aec-regulatory": {
      "url": "https://engenheiro-producao-ai.onrender.com/mcp/regulatory/sse"
    }
  }
}
~/.codex/config.toml
[mcp_servers.ecosystem-aec-regulatory]
url = "https://engenheiro-producao-ai.onrender.com/mcp/regulatory/sse"
.cursor/mcp.json
{
  "mcpServers": {
    "ecosystem-aec-regulatory": {
      "url": "https://engenheiro-producao-ai.onrender.com/mcp/regulatory/sse"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "ecosystem-aec-regulatory": {
      "url": "https://engenheiro-producao-ai.onrender.com/mcp/regulatory/sse"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://engenheiro-producao-ai.onrender.com/mcp/regulatory/sse sse answering 199 ms 6 min ago

Ecosystem Aec Regulatory — questions

Answers built from our own checks of this server.

Is Ecosystem Aec Regulatory 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 199 ms. The bar chart above shows every period we have measured.
Is Ecosystem Aec Regulatory still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists Ecosystem Aec Regulatory 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 Ecosystem Aec Regulatory?
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 Ecosystem Aec Regulatory need an API key?
No. Ecosystem Aec Regulatory 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.