mcpbeat

Regulatory Monitor MCP Server

io.github.martc03/regulatory-monitor
answering

Regulatory Monitor is answering right now. Last checked 8 min ago. Last commit 6 Apr 2026.

Federal Register monitoring and regulations.gov tracking. 4 MCP tools for regulatory compliance.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
458 ms
Response time
average over 24h
5
Stars
last commit 6 Apr 2026

Connect this server

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

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

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://regulatory-monitor-mcp.apify.actor/mcp streamable-http needs key 459 ms 8 min ago

Regulatory Monitor — questions

Answers built from our own checks of this server.

Why is there no tool list for Regulatory Monitor?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Regulatory Monitor working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 458 ms. The bar chart above shows every period we have measured.
How do I connect Regulatory Monitor?
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. You will need your own key or an OAuth login: it refuses anonymous clients.
Does Regulatory Monitor need an API key?
Yes. Every time we knock, Regulatory Monitor answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Regulatory Monitor?
It answers our handshake in 458 ms on average, which is faster than 26% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Regulatory Monitor open source?
Yes — it is published under the MIT licence, written in TypeScript and 5 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.