mcpbeat

Regulatory Radar MCP Server

io.github.jdhart81/regulatory-radar
answering

Regulatory Radar is answering right now. Last checked 11 min ago. It exposes 4 tools. Last commit 3 Aug 2026.

California, US, and global climate compliance scans with source-linked deadlines.

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
333 ms
Response time
average over 24h
0
Stars
last commit 3 Aug 2026

Connect this server

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

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

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

assess
assess_compliance
Assess a company's compliance posture against applicable regulations. Returns compliance level, percentage, gaps, and remediation priorities.
describe
describe_agent
Fleet-standard self-description: capabilities, inputs, outputs.
monitor
monitor_changes
Monitor recent regulatory changes in a jurisdiction over a trailing window.
scan
scan_regulations
Scan a jurisdiction (e.g. EU, US, california, or CA for Canada), optionally filtered by sector. Returns regulations with urgency flags and effective dates. Price: $0.25 per call after 10 free calls/day. Pay at /x402/regulatory-radar/scan_regulations with Base USDC, cash-fund payment_ref through escrow_checkout + confirm_escrow_funding, or use /seats.

Endpoints

URLTransportStateLatencyChecked
https://mcp.viridisconservation.com/regulatory-radar/mcp streamable-http answering 317 ms 11 min ago

Regulatory Radar — questions

Answers built from our own checks of this server.

What can Regulatory Radar do?
It exposes 4 tools, read directly from the server on our last check. Among them: assess_compliance, describe_agent, monitor_changes, scan_regulations. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Regulatory Radar 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 333 ms. The bar chart above shows every period we have measured.
How do I connect Regulatory Radar?
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 Regulatory Radar need an API key?
No. Regulatory Radar completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Regulatory Radar?
It answers our handshake in 333 ms on average, which is faster than 42% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Regulatory Radar open source?
Yes — written in Python, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.