mcpbeat Sign in

Federal Regulations MCP Server

answering

Federal Regulations MCP Server is answering right now. Last checked 16 min ago. 255 installs a week from npm. It exposes 7 tools. Last commit 29 Oct 2026.

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

Installs per day peak 300 · avg 53 · -71% w/w
a month agotoday
Uptime history 91 days of history · worst day 92%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
558 ms
Response time
average over 24h
255
Installs / week
npm and PyPI

What changed 66

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

29 Oct 7 tools changed the parameters they ask for regulations_browse_cfr, regulations_find_comments, regulations_get_cfr_section and 4 more
29 Oct 4 tool descriptions were rewritten regulations_browse_cfr, regulations_get_docket, regulations_get_document and 1 more
29 Oct a tool changed version
28 Oct a tool changed version
25 Oct a tool changed version
9 Oct a tool changed version
25 Sep 6 tools changed the parameters they ask for9 times that day regulations_browse_cfr, regulations_find_comments, regulations_get_cfr_section and 3 more
25 Sep 5 tool descriptions were rewritten regulations_find_comments, regulations_get_cfr_section, regulations_get_document and 2 more
25 Sep a tool changed version3 times that day
22 Sep 5 tool descriptions were rewritten regulations_browse_cfr, regulations_get_cfr_section, regulations_get_document and 2 more
and 34 more, back to 10 August 2026

Nothing serious here today

Today is the operative word: we check Federal Regulations MCP Server every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add federal-regulations-mcp-server --transport http https://federal-regulations.caseyjhand.com/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "federal-regulations-mcp-server": {
      "type": "http",
      "url": "https://federal-regulations.caseyjhand.com/mcp"
    }
  }
}

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 three modes. "structure" lists all 50 titles; with a title, that title's top-level divisions (its chapters, or subtitles); and with a title and part, every section and appendix in the part, flattened and paged, each naming the subpart and subject group it sits under — the way to enumerate a part's sections without reading its text. "search" runs a full-text query across the codified CFR and returns matching sections with their hierarchy path and a snippet, one result per section, paged. "versions" lists the dates a part's or one section's text changed, oldest first per section, paged, with the latest amendment date; with changed_since, what changed across a title. Every mode accepts title and part to narrow the scope, and all three feed regulations_get_cfr_section — a version row's `date` reads that version. 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, by its object ID or document ID), fr_document_number (convenience — resolves the FR number to the Regulations.gov document carrying it), or comment_id (one comment's full detail and attachments). A list narrows by comment text with search_term (each hit then carries the matching passages) and by posted date with posted_after/posted_before. 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, with its Authority and Source notes, an index of its sections, and the names of its appendices; title + appendix for one appendix, passing the identifier exactly as regulations_browse_cfr emits it. A section can be written as people cite it — "61", "§ 141.61", "141.61(c)", or the full cite "40 CFR 141.61" in part 141 all read 40 CFR 141.61 — and a part as "Part 141"; the response names the identifier it read. Text comes back as a window of up to 64,000 characters (max_chars raises it to 200,000) with the total length and, when text remains, the offset to resume from; whole parts run to millions of characters, so page with offset or read a single section. eCFR retains historical versions from 2017 through the title's up-to-date date; a date outside that window is rejected with the window named. Current single-section reads are served from a synced local mirror when it holds the title's latest eCFR issue; 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) — or read one document by document_id for its file download URLs and attachments, which a docket listing does not carry. Provide exactly one of docket_id / document_id. 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 — find one with search_term, or filter document_types to "Proposed Rule"/"Rule" for 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, EO 12866 significance, and for a presidential document its subtype, number, signing date, and president) plus the cross-source handles that make this a workflow server. The output carries the Regulations.gov docket ID (chain into regulations_get_docket or regulations_find_comments), the docket numbers the Federal Register prints (chain back into regulations_search_rules as docket_id), the comment count and comment URL, and the affected CFR parts (chain into regulations_get_cfr_section). Set include_full_text only when the rule body itself is needed: it returns the plain-text body as a window of up to 64,000 characters (max_chars raises it to 200,000), with the body's total length and, when text remains, the offset to resume from. Short documents return whole; major final rules run past a million characters, so page through with offset rather than reading them in one call.
regulations_list_open_comments
List Federal Register documents currently open for public comment, sorted by closing date (soonest first) across the whole open window, filterable by document type, agency slug, and topic. "What can I still weigh in on?" Covers proposed rules and the final rules that take comment (direct final and interim final rules) by default; add NOTICE for the much larger set of notices with comment periods. Runs on the Federal Register's open-comment window and needs no key: each row carries its Regulations.gov docket and document IDs, comment count, and comment URL from the Federal Register document's embedded Regulations.gov info. Open one row with regulations_get_document for the full document, or pull the comments with regulations_find_comments (which, like regulations_get_docket, needs REGULATIONS_GOV_API_KEY).
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, affected CFR title and part, printed docket number, RIN, EO 12866 significance, effective date range, and for presidential documents the executive order number, subtype, president, and signing date range, all combined. A page cite from a CFR source note ("89 FR 49102", with its date) resolves to the documents printed on that page. The primary discovery entry point: results carry the document number (open with regulations_get_document), its citation and page range, each issuing agency with its filterable slug, printed docket numbers, Regulations.gov docket and document IDs, comment count and comment URL, whether the comment period is open, RINs, significance, presidential-document identifiers, and affected CFR parts that chain into the comment and codified-text tools. A query ranks by relevance unless order says otherwise; filter-only browsing lists newest first. 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

URLTransportStateLatencyChecked
https://federal-regulations.caseyjhand.com/mcp streamable-http answering 257 ms 16 min ago

Alternatives to Federal Regulations MCP Server

same job, measured the same way
Citesearch
by cloudcorprecords

Search, read and trace links across the Edgepedia encyclopedia corpus.

264 installs/wk local only
Release Alert
by releasealert

Search packages across registries, and read their releases and CVEs.

answering
MarkMesh
by markmesh

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

answering
Datacite MCP Server
by cyanheads

Search DataCite datasets and software, fetch DOI metadata, trace relations, format citations.

347 installs/wk 6 tools answering
Altmetric MCP
by altmetric-mcp

MCP server for Altmetric APIs - track research attention across news, policy, social media, and more

answering
US SAM.gov, EU TED & Brazil PNCP Public Tenders Radar
by jesleytassili-glitch

Monitor live government contracts and tenders across US Federal awards, EU TED OJ S & Brazil PNCP.

answering
Rokha
by rokha

Search a registry of agent skills and MCP servers, then run them for real. No install, traced.

30 tools answering
Sikaru Docs
by sikaru

Read-only search over the public Sikaru documentation: managed agents, inference, evals and traces.

1 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 91 of 91 checks got a reply (100.0%), average response time 558 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 in the form 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 558 ms on average, which is faster than 20% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. 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 255 times in the last week. Week over week that is -71%. 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?
The code is open source: it is published under the Apache-2.0 licence, written in TypeScript, 2 stars on GitHub and 9 open issues. The licence covers the code in the repository, not the hosted service at federal-regulations.caseyjhand.com, which runs on its operator's own terms.