Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Regulatory Intel MCP

REMOTE · REGULATORY.DATAKOOT.COM

US Federal Register for AI agents: rules, notices, executive orders, agency lookup. No keys.

0 this week 82 Trust /100

Last scanned (14 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 21 Nov 2026.

Category News and Social

Trust breakdown (7 categories)

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 Security69
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Oct 26 0
    • Authorization: unverified → partial ▲ security
    • Tool “agencies” now declares an output schema ▲ functional
    • Tool “document” now declares an output schema ▲ functional
    • Tool “executive_orders” now declares an output schema ▲ functional
    • Tool “recent_documents” now declares an output schema ▲ functional
    • Tool “search_documents” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
    • Tool “agencies” changed its title: Agencies cosmetic
    • Tool “document” changed its title: Document cosmetic
    • Tool “executive_orders” changed its title: Executive Orders cosmetic
    • Tool “recent_documents” changed its title: Recent Documents cosmetic
    • Tool “search_documents” changed its title: Search Documents cosmetic
  • 2 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 3 Sept 26 0
    • HSTS header: fail → pass ▲ security
    • Stability: unverified → 0.03 ▲ functional
    • MCP protocol version: 2024-11-05 → 2025-06-18 functional
Diagnostics

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 21 Nov 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. DS published 19718 13 Verified
datakoot.com. No DS 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
MCP tools · 5 exposed · ~557 tokens

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 →

Tool Tokens
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'.

NameTypeReqDescription
querystring–Filter agencies whose name contains this text.
NameTypeReqDescription
agencies–––
count–––
provenanceobject–Where this answer came from. served_at is when Datakoot answered (UTC); upstream lists the official sources consulted. Datakoot may serve a briefly cached copy, so the source's own observation can be…
source–––

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.

NameTypeReqDescription
document_numberstringyesFederal Register document number, e.g. 2026-17888. Get one from search_documents or recent_documents.
NameTypeReqDescription
abstract–––
action–––
agencies–––
cfr_references–––
citation–––
comments_close_on–––
dates–––
document_number–––
effective_on–––
executive_order_number–––
html_url–––
note–––
pdf_url–––
provenanceobject–Where this answer came from. served_at is when Datakoot answered (UTC); upstream lists the official sources consulted. Datakoot may serve a briefly cached copy, so the source's own observation can be…
publication_date–––
regulation_id_numbers–––
significant–––
signing_date–––
source–––
title–––
topics–––
type–––

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.

NameTypeReqDescription
per_pageinteger–Results to return (default 10, max 30).
sincestring–Only EOs published on/after this date (YYYY-MM-DD).
termstring–Optional keyword to search within executive orders.
NameTypeReqDescription
count–––
note–––
provenanceobject–Where this answer came from. served_at is when Datakoot answered (UTC); upstream lists the official sources consulted. Datakoot may serve a briefly cached copy, so the source's own observation can be…
results–––
source–––
total_pages–––

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.

NameTypeReqDescription
agencystring–Agency slug (from the 'agencies' tool).
daysinteger–Look back this many days (default 7, max 90).
per_pageinteger–Results to return (default 15, max 30).
typestring–Document type. One of: rule, proposed_rule, notice, presidential_document.
NameTypeReqDescription
count–––
note–––
provenanceobject–Where this answer came from. served_at is when Datakoot answered (UTC); upstream lists the official sources consulted. Datakoot may serve a briefly cached copy, so the source's own observation can be…
results–––
since–––
source–––
total_pages–––
window_days–––

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'.

NameTypeReqDescription
agencystring–Agency slug (from the 'agencies' tool), e.g. 'environmental-protection-agency'.
per_pageinteger–Results to return (default 10, max 30).
sincestring–Only documents published on/after this date (YYYY-MM-DD).
termstring–Keyword(s) to search, e.g. 'artificial intelligence', 'PFAS'.
typestring–Restrict to one document type.
untilstring–Only documents published on/before this date (YYYY-MM-DD).
NameTypeReqDescription
count–––
note–––
provenanceobject–Where this answer came from. served_at is when Datakoot answered (UTC); upstream lists the official sources consulted. Datakoot may serve a briefly cached copy, so the source's own observation can be…
results–––
source–––
total_pages–––

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http com-datakoot-federal-register-rules 'https://regulatory.datakoot.com/mcp'
Common questions

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 82 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Regulatory Intel MCP server?

VerifyMCP ran 12 checks on Regulatory Intel MCP, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Regulatory Intel MCP: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.