Regulatory Radar MCP server
io.github.jdhart81/regulatory-radarjdhart81streamable-httpv0.2.1Scanned
California, US, and global climate compliance scans with source-linked deadlines.
6 tools: 5 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Regulatory Radar MCP server can do
The Regulatory Radar MCP server is published by the GitHub account jdhart81. It has 6 tools. It can create or change data (5 tools: scan_regulations, assess_compliance, monitor_changes, watch_changes and 1 more), but cannot delete data. 1 tool only reads.
2 tools bring in text other people can write (watch_changes and build_evidence_pack).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 0.2.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 5Claude Code: ask
assess_complianceScreen a company's posture against applicable regulations.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Screen a company's posture against applicable regulations. Returns compliance level, percentage, gaps, and remediation priorities. Gated obligations count only when their applicability is established from inputs. California SB 253 needs revenue over $1B in each of the two previous fiscal years (`annual_revenue_usd` = most recent year, `prior_year_revenue_usd` = the year before) and an `entity_profile` with entity_form (corporation|partnership|llc|other_business_entity), formed_under_us_law, does_business_in_california and exemption (none|tax_exempt_nonprofit|insurance|government_majority_owned| wholesale_electricity_only|payroll_only). Missing inputs list it under applicability_unconfirmed and the level is "undetermined", never "compliant". Screening only, not legal advice.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Assess compliance
build_evidence_packBuild a live, source-hashed regulatory change evidence pack.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Build a live, source-hashed regulatory change evidence pack. Fetches only the product's registry-owned regulator URLs, reports source retrieval timestamps and SHA-256 hashes, distinguishes a first baseline from a detected change, emits a bounded text diff on later changes, and combines the evidence with a curated deadline calendar. Screening only; confirm legal applicability with the cited authority or qualified counsel.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Build evidence pack
monitor_changesWatch curated regulatory effective dates and deadlines in a bounded window.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Watch curated regulatory effective dates and deadlines in a bounded window. `since_days` controls both recently effective dates behind today and effective/deadline dates ahead of today. This is a source-linked watch over the curated Viridis dataset, not a live external regulatory feed.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Monitor changes
scan_regulationsScan a jurisdiction (e.g.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Scan a jurisdiction (e.g. EU, US, california, or CA for Canada), optionally filtered by sector and/or a free-text query over regulation names, descriptions and requirements. 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. jurisdiction is one of eu, uk, us, california, ca (Canada), au, jp, sg, global. A US state or EU member state is read as us or eu and the response says so. sector is one of agriculture, consumer_goods, energy, financial_services, fisheries, forestry, manufacturing, technology. Example arguments: {"jurisdiction": "california", "sector": "energy"}
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Scan applicable regulations
watch_changesPoll for text changes on official regulator pages since your last poll.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Poll for text changes on official regulator pages since your last poll. Radar Watch keeps a durable log of every detected change to the registry-owned official sources (SEC, European Commission, EFRAG, CARB). Pass the `cursor` from your previous answer as `since` to receive only what is new; 0 returns the whole log for your selection. Each change has the source, both text hashes, the detection time and a short diff excerpt. The answer lists exactly which sources were watched and when they were last retrieved, plus the curated deadline calendar. Sources are re-retrieved when the last sweep is older than `max_age_hours`. A change is a text difference on an official page, not a legal determination. Example arguments: {"jurisdiction": "california", "since": 0}
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Watch changes
Only reads 1Show 1 read-only tool
describe_agentFleet-standard self-description: capabilities, inputs, outputs.No findings
Why it is in this group
- The name "describe_agent" says "describe": a word for reading.
Description, as the server wrote it Fleet-standard self-description: capabilities, inputs, outputs.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Describe this service
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:29 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.viridisconservation.com/regulatory-radar/mcp: tools/list returned 6 tools to an anonymous client, including scan_regulations (write), assess_compliance (write), monitor_changes (write), watch_changes (write), build_evidence_pack (write)
Posture changes
- Nov 13, 2026
- Tools that change things, listed without credentials: 4 to 5
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added, 4 changed.+1 added~4 changedView diff
- Added:watch_changesChanges things
- Changed:assess_complianceChanges thingsinputSchema
- Changed:build_evidence_packChanges thingsinputSchema
- Changed:monitor_changesChanges thingsinputSchema
- Changed:scan_regulationsChanges thingsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 4 -> 5.View diff
- Tools that change things, listed without credentials: 4 to 5
Tools5 changed.~5 changedView diff
- Changed:assess_complianceChanges thingstitledescriptioninputSchemaannotations
- Changed:build_evidence_packChanges thingstitleannotations
- Changed:describe_agentOnly readstitleannotations
- Changed:monitor_changesChanges thingstitleannotations
- Changed:scan_regulationsChanges thingstitledescriptioninputSchemaannotations
Install
Pinned to version 0.2.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http regulatory-radar https://mcp.viridisconservation.com/regulatory-radar/mcpclaude mcp add --transport http regulatory-radar https://mcp.viridisconservation.com/regulatory-radar/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__regulatory-radar__describe_agent"
],
"ask": [
"mcp__regulatory-radar__scan_regulations",
"mcp__regulatory-radar__assess_compliance",
"mcp__regulatory-radar__monitor_changes",
"mcp__regulatory-radar__watch_changes",
"mcp__regulatory-radar__build_evidence_pack"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as regulatory-radar. Review it before you use it.
Capability tags behind 2 rules
- mcp__regulatory-radar__watch_changes untrusted-input
- mcp__regulatory-radar__build_evidence_pack untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.jdhart81/regulatory-radar/verify?hash=448812406d7b535b165ae8a10305295ba2633b8580d7a3ed009b719fd1041f9b" | jq -e '.changed == false'Pinned hash 448812406d7b, from Nov 16, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.jdhart81/regulatory-radar/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.jdhart81/regulatory-radar)Source: MCP Registry · repository. Synced Nov 16, 2026, 02:18 UTC.
Regulatory Radar MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Regulatory Radar MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Regulatory Radar MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Regulatory Radar MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Regulatory Radar MCP server have?
- 6 tools: 5 write, 1 read. scan_regulations, assess_compliance, monitor_changes, watch_changes, build_evidence_pack and describe_agent.
Does the Regulatory Radar MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Regulatory Radar MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Regulatory Radar MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.