mcp-registry/io.github.jdhart81/regulatory-radar · v1.28.1
As of 2026-10-22 20:42 UTC, the Jdhart81 Regulatory Radar MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 7 minutes.
California, US, and global climate compliance scans with source-linked deadlines.
Claude Code
claude mcp add --transport http jdhart81-regulatory-radar-mcp-server https://mcp.viridisconservation.com/regulatory-radar/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"jdhart81-regulatory-radar-mcp-server": {
"type": "http",
"url": "https://mcp.viridisconservation.com/regulatory-radar/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
21 parameter(s) across 4 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
In the last 30 days: 0 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.jdhart81%2Fregulatory-radar/fixes
{
"name": "describe_agent",
"description": "Fleet-standard self-description: capabilities, inputs, outputs.",
"inputSchema": {
"type": "object",
"title": "describe_agentArguments",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.jdhart81/regulatory-radar"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.jdhart81/regulatory-radar"}) over MCP.
build_evidence_pack ~330 tokensmonitor_changes ~245 tokensscan_regulations ~240 tokensassess_compliance ~222 tokensdescribe_agent ~52 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.jdhart81%2Fregulatory-radar?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.jdhart81%2Fregulatory-radar?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jdhart81%2Fregulatory-radar.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jdhart81%2Fregulatory-radar.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.jdhart81%2Fregulatory-radar?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:0e7cbf91febd9076…, first seen 2026-10-17, included at leaf 1960 of 48,045. Version history · verify what your client received.
Compare: most reliable other servers · most reliable ml servers · most reliable security servers · most reliable payments servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 20:42 UTC, the Jdhart81 Regulatory Radar MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 7 minutes.
Jdhart81 Regulatory Radar MCP server advertises 18 tools, including agent-arbitration, agent-compute-ledger, agent-covenant, agent-escrow, agent-identity-registry.
Point your MCP client at this streamable-http endpoint: https://mcp.viridisconservation.com/regulatory-radar/mcp
Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.