Regulatory Intel MCP
REMOTE · REGULATORY.SELFLABBS.COM
US Federal Register for AI agents: rules, notices, executive orders, agency lookup. No keys.
Available components
Last scanned (2 months ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 28 Jul 2026.
Category News and Social
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety–
Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 17 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Aug 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Aug 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
- 10 Aug 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 9 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 31 Jul 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
- 29 Jul 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
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 17 Aug 2026 · Probed https://regulatory.selflabbs.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of regulatory.selflabbs.com. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| regulatory.selflabbs.com. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://regulatory.selflabbs.com/mcp | Unreachable | ||
| http (plaintext) | http://regulatory.selflabbs.com/mcp | HTTPS enforced |
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 ~60
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 | – |
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 ~106
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 | – | – |
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.
How do I install the Regulatory Intel MCP server?
Regulatory Intel MCP is a hosted endpoint at https://regulatory.selflabbs.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.selflabbs.com
claude mcp add --transport http selflabbs-regulatory-intel-mcp 'https://regulatory.selflabbs.com/mcp'
What is the Regulatory Intel MCP server?
Regulatory Intel MCP is listed in the public MCP registry as io.github.selflabbs/regulatory-intel-mcp. US Federal Register for AI agents: rules, notices, executive orders, agency lookup. No keys. This page covers its hosted endpoint (https://regulatory.selflabbs.com/mcp).
Is the Regulatory Intel MCP server safe to use?
Regulatory Intel MCP scores 0 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 519 tokens of context every time the server is loaded.
Does the Regulatory Intel MCP server require authentication?
Its publisher declares no required credentials for Regulatory Intel MCP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Regulatory Intel MCP server still maintained?
Regulatory Intel MCP has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 28 July 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.