Federal Regulations MCP Server

by cyanheads Your server? Claim it

answering

Federal Regulations MCP Server is answering right now. Last checked 6 min ago. 221 installs a week from npm. It exposes 7 tools. Last commit 21 Sep 2026.

Search and trace US federal rules across the Federal Register, eCFR, and Regulations.gov.

Installs per day peak 280 · avg 29 · +269% w/w

a month agotoday

Uptime history 51 days of history · worst day 0%

51 days agonow

97.8%

Uptime 24h

89 of 91 checks

Tools

read from the server

279 ms

Response time

average over 24h

221

Installs / week

npm and PyPI

What changed 22

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 10 August 2026. No other catalogue keeps this.

20 Sep a tool changed version

22 Aug 7 tools changed the parameters they ask for regulations_browse_cfr, regulations_find_comments, regulations_get_cfr_section and 4 more

22 Aug a tool changed version2 times that day

10 Aug a tool changed version5 times that day

10 Aug 3 tools changed the parameters they ask for4 times that day regulations_browse_cfr, regulations_find_comments, regulations_get_cfr_section

10 Aug 2 tool descriptions were rewritten3 times that day regulations_browse_cfr, regulations_get_cfr_section

and 7 more, back to 10 August 2026

Federal Regulations MCP Server does not always answer

Over the last week it answered 99.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add federal-regulations-mcp-server --transport http https://federal-regulations.caseyjhand.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "federal-regulations-mcp-server": {
      "url": "https://federal-regulations.caseyjhand.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.federal-regulations-mcp-server]
url = "https://federal-regulations.caseyjhand.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "federal-regulations-mcp-server": {
      "url": "https://federal-regulations.caseyjhand.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "federal-regulations-mcp-server": {
      "url": "https://federal-regulations.caseyjhand.com/mcp"
    }
  }
}

This one needs environment variables set before it will start: MCP_HTTP_HOST (The hostname for the HTTP server.), MCP_HTTP_PORT (The port to run the HTTP server on.), MCP_HTTP_ENDPOINT_PATH (The endpoint path for the MCP server.), MCP_AUTH_MODE (Authentication mode to use: 'none', 'jwt', or 'oauth'.), REGULATIONS_GOV_API_KEY (api.data.gov key for the Regulations.gov tools (get_docket, find_comments). Free at https://api.data.gov/signup/. The Federal Register and eCFR tools work without it.), MCP_LOG_LEVEL (Sets the minimum log level for output (e.g., 'debug', 'info', 'warn').). The author declared them in the registry entry; get the values from the project itself.

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

regulations

regulations_browse_cfr

Explore the codified Code of Federal Regulations via eCFR in two modes. "structure" walks the CFR hierarchy (all 50 titles, or one title's chapters → parts → sections) to discover a cite when the exact citation is unknown. "search" runs a full-text query across the codified CFR and returns matching sections with their hierarchy path and a snippet. Both modes accept title and part to narrow the scope, so a part surfaced by structure mode can be searched directly instead of filtering a whole title's hits by eye. Both feed regulations_get_cfr_section. Every search result reports which corpus answered it — the synced local mirror or the live eCFR index — and what that corpus covers, in `source` and `sourceScope`.

regulations_find_comments

Fetch public comments on a Federal Register document or a Regulations.gov docket — the unique corpus of what citizens and organizations actually submitted. Provide exactly one targeting parameter: docket_id (all comments in a docket, broadest), document_object_id (comments on one document, from regulations_get_docket), fr_document_number (convenience — resolves the FR number to its Regulations.gov document internally), or comment_id (one comment's full detail and attachments). The list endpoint returns no body text or attachment info — call with comment_id to read a comment's body. When a comment's real content is a PDF/DOCX attachment, the body is a stub and attachmentOnly is true; the attachment download URLs are returned. Requires REGULATIONS_GOV_API_KEY (free at https://api.data.gov/signup/).

regulations_get_cfr_section

Read the codified text at a CFR location via eCFR — current or as of a past date. Answers "what does 40 CFR 50.1 say today?" and "...as of 2019-01-01?". Three locations: title + part + section for one section; title + part alone for the whole part (large parts can be very long, and their appendices are named rather than inlined; prefer a specific section when you know it); title + appendix for one appendix, passing the identifier exactly as regulations_browse_cfr emits it. eCFR retains historical versions back to roughly 2017; a date before coverage is rejected with guidance. Current single-section reads are served from a synced local mirror when available; the source is reported.

regulations_get_docket

Pull a rulemaking docket from Regulations.gov by docket ID (e.g. "EPA-HQ-OAR-2025-0194") — the docket's metadata (title, agency, RIN, abstract) and the documents filed in it (NPRM, final rule, supporting materials). The docket is the folder holding a rule's whole paper trail; each returned document's objectId feeds regulations_find_comments. A docket often contains hundreds of supporting materials — filter document_types to "Proposed Rule"/"Rule" to find the rule documents themselves. Requires REGULATIONS_GOV_API_KEY (free at https://api.data.gov/signup/); the Federal Register and eCFR tools work without it.

regulations_get_document

Fetch one Federal Register document by its FR document number — full metadata (title, type, agencies, abstract, action, effective/comment dates, RINs) plus the cross-source handles that make this a workflow server. The output carries the docket ID (chain into regulations_get_docket or regulations_find_comments) and the affected CFR parts (chain into regulations_get_cfr_section). Set include_full_text only when the rule body itself is needed — final rules can run tens of thousands of words.

regulations_list_open_comments

List rules currently open for public comment, filterable by agency slug and topic, sorted by closing date (soonest first). "What can I still weigh in on?" Runs on the Federal Register's open-comment window and is fully functional without a key. When REGULATIONS_GOV_API_KEY is configured, each row is enriched with the comment count from the Federal Register document's embedded Regulations.gov info (no extra rate-limited call). Open one row with regulations_get_document for the full proposal, or pull the comments with regulations_find_comments.

regulations_search_rules

Search the Federal Register — the daily journal of US proposed rules, final rules, notices, and presidential documents (1994–present) — filtering by full-text query, document type, agency slug, publication date range, and whether the rule is open for comment. The primary discovery entry point: results carry the document number (open with regulations_get_document), docket IDs, RINs, and affected CFR parts that chain into the comment and codified-text tools. The Federal Register caps navigation at 50 pages and the match count at 10,000; when a result set is larger, narrow with published_after/published_before rather than paging deeper.

Endpoints

URL	Transport	State	Latency	Checked
https://federal-regulations.caseyjhand.com/mcp	streamable-http	answering	421 ms	6 min ago

Alternatives to Federal Regulations MCP Server

same job, measured the same way

MarkMesh

by markmesh

Trademark search, monitoring and conflict research across 30+ registers, with provenance.

answering

Ask the Grid

by parisi-labs

Live U.S. electric-grid data, forecasts, alerts, and analysis across major grid regions.

answering

CiteNexus

by akougkas

Search scholarly sources, verify references, and export citations with traceable evidence.

local only

Meridian Trace — Medical Device Registrations

by meridiantrace

Medical device registrations across 25 markets: coverage gaps, 510(k) predicates, classification

12 tools answering

US Drought Monitor

by olyport

Current drought conditions and severity across the United States

3 tools answering

Parahuman

by parahuman

Search brand mentions, track sentiment, and manage monitored keywords across 11 platforms.

answering

Hypathesis

by predme

Variable relationships from research papers with causal direction and source traceback.

4 tools answering

EkoPump

by edjacarmona-cmd

Real-time fuel prices, alerts, and cheapest gas stations across 38+ countries.

4 tools answering

Federal Regulations MCP Server — questions

Answers built from our own checks of this server.

What can Federal Regulations MCP Server do?

It exposes 7 tools, read directly from the server on our last check. Among them: regulations_browse_cfr, regulations_find_comments, regulations_get_cfr_section, regulations_get_docket, regulations_get_document, regulations_list_open_comments and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Federal Regulations MCP Server working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 91 checks got a reply (97.8%), average response time 279 ms. The bar chart above shows every period we have measured.

How do I connect Federal Regulations MCP Server?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Federal Regulations MCP Server need an API key?

No. Federal Regulations MCP Server completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Federal Regulations MCP Server?

It answers our handshake in 279 ms on average, which is faster than 56% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Federal Regulations MCP Server?

The npm package @cyanheads/federal-regulations-mcp-server was installed 221 times in the last week. Week over week that is +269%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Federal Regulations MCP Server open source?

Yes — it is published under the Apache-2.0 licence, written in TypeScript, 1 stars on GitHub and 4 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.