Regulatory Intel MCP
REMOTE · REGULATORY.DATAKOOT.COM · SCANNED SEP 27
US Federal Register for AI agents: rules, notices, executive orders, agency lookup. No keys.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 614 tokens (~122/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Regulatory Intel MCP server?
Regulatory Intel MCP is a hosted endpoint at https://regulatory.datakoot.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · regulatory.datakoot.com
claude mcp add --transport http com-datakoot-federal-register-rules 'https://regulatory.datakoot.com/mcp'
{
"mcpServers": {
"com-datakoot-federal-register-rules": {
"url": "https://regulatory.datakoot.com/mcp"
}
}
} {
"servers": {
"com-datakoot-federal-register-rules": {
"type": "http",
"url": "https://regulatory.datakoot.com/mcp"
}
}
} [mcp_servers.com-datakoot-federal-register-rules] url = "https://regulatory.datakoot.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-datakoot-federal-register-rules": {
"type": "remote",
"url": "https://regulatory.datakoot.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-datakoot-federal-register-rules --url 'https://regulatory.datakoot.com/mcp' --transport streamable-http
mcp_servers:
com-datakoot-federal-register-rules:
url: "https://regulatory.datakoot.com/mcp" {
"McpServers": {
"com-datakoot-federal-register-rules": {
"Transport": "http",
"Url": "https://regulatory.datakoot.com/mcp"
}
}
} assistant mcp add com-datakoot-federal-register-rules -t streamable-http -u 'https://regulatory.datakoot.com/mcp'
{
"mcpServers": {
"com-datakoot-federal-register-rules": {
"type": "http",
"url": "https://regulatory.datakoot.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://regulatory.datakoot.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=datakoot.com | CN=WE1,O=Google Trust Services,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f1d8a58e3689895d13d01b4310b689be |
| SANs: datakoot.com, regulatory.datakoot.com, *.regulatory.datakoot.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of regulatory.datakoot.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| datakoot.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://regulatory.datakoot.com/mcp | Verified | 200 | |
| http (plaintext) | http://regulatory.datakoot.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
agencies ~63
Look up US federal agencies and their slugs (used to filter the other tools by issuing agency). Optionally pass a query to match by name, e.g. 'environmental' or 'defense'.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Filter agencies whose name contains this text. |
No output schema declared.
No examples provided.
document ~83
Get full detail on a single Federal Register document by its document number (e.g. '2026-12811'): abstract, action, effective date, comment deadline, CFR references, citation, topics, agencies and links.
| Name | Type | Req | Description |
|---|---|---|---|
| document_number | string | yes | Federal Register document number, e.g. 2026-17888. Get one from search_documents or recent_documents. |
No output schema declared.
No examples provided.
executive_orders ~94
Search recent US presidential Executive Orders published in the Federal Register. Optionally filter by keyword and date. Returns EO number, signing/publication date, title and links.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | integer | – | Results to return (default 10, max 30). |
| since | string | – | Only EOs published on/after this date (YYYY-MM-DD). |
| term | string | – | Optional keyword to search within executive orders. |
No output schema declared.
No examples provided.
recent_documents ~121
List the most recent Federal Register documents, optionally filtered by type and issuing agency, over a look-back window. Use this to monitor newly published rules/notices from an agency.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Agency slug (from the 'agencies' tool). |
| days | integer | – | Look back this many days (default 7, max 90). |
| per_page | integer | – | Results to return (default 15, max 30). |
| type | string | – | Document type. One of: rule, proposed_rule, notice, presidential_document. |
No output schema declared.
No examples provided.
search_documents ~196
Search the US Federal Register for regulations and notices. Filter by keyword, document type (rule, proposed_rule, notice, presidential_document), issuing agency (slug from the agencies tool), and publication date. Returns matching documents with title, type, agencies, abstract and links. Great for 'what did agency X publish about topic Y'.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Agency slug (from the 'agencies' tool), e.g. 'environmental-protection-agency'. |
| per_page | integer | – | Results to return (default 10, max 30). |
| since | string | – | Only documents published on/after this date (YYYY-MM-DD). |
| term | string | – | Keyword(s) to search, e.g. 'artificial intelligence', 'PFAS'. |
| type | string | – | Restrict to one document type. |
| until | string | – | Only documents published on/before this date (YYYY-MM-DD). |
No output schema declared.
No examples provided.
What is the Regulatory Intel MCP server?
Regulatory Intel MCP is listed in the public MCP registry as com.datakoot/federal-register-rules. US Federal Register for AI agents: rules, notices, executive orders, agency lookup. No keys. This page covers its hosted endpoint (https://regulatory.datakoot.com/mcp).
Is the Regulatory Intel MCP server safe to use?
Regulatory Intel MCP scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Regulatory Intel MCP server expose?
Regulatory Intel MCP exposes 5 tools: search_documents, document, recent_documents, executive_orders, agencies. Their descriptions and schemas cost roughly 557 tokens of context every time the server is loaded.
Does the Regulatory Intel MCP server require authentication?
No. We connected to Regulatory Intel MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Regulatory Intel MCP server still maintained?
Regulatory Intel MCP is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.