ZBS Index What actually exists in applied AI, with the source next to it

mcp server

federal-regulations-mcp-server

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

Description as published by the maintainer. Source

  • version 0.1.2
  • active
  • retrieval

active — Most recent push to the repository was 2026-07-30. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.

What this server can do

7 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.

regulations_browse_cfr(date, mode, part, query, title, per_page)
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`. Required: mode.
regulations_find_comments(page, per_page, docket_id, comment_id, document_object_id, fr_document_number)
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(date, part, title, section, appendix)
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. Required: title.
regulations_get_docket(page, per_page, docket_id, document_types)
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. Required: docket_id.
regulations_get_document(document_number, include_full_text)
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. Required: document_number.
regulations_list_open_comments(page, query, agencies, per_page, closing_before)
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(page, type, query, agencies, per_page, published_after, published_before)
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.

Last successful function declaration observed on . Source: https://federal-regulations.caseyjhand.com/mcp. We list what the server declared; we do not call any of these functions.

Endpoint status observed on . Source: https://federal-regulations.caseyjhand.com/mcp.

Signals

These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.

Signal Value What it measures Window Observed Source
GitHub stars 1 Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. cumulative, all time GitHub
Last commit 2026-07-30 Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. point in time GitHub
Open issues 6 Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. as of fetch GitHub
Latest published version 0.1.2 Latest version string the maintainer published to the registry. as of fetch Model Context Protocol
Registry record last updated 2026-06-20 When the registry record was last updated by its maintainer. point in time Model Context Protocol
License Apache-2.0 Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. as of fetch GitHub
First listed in the MCP Registry 2026-06-20 Date this server was first published to the official MCP Registry. Not a usage or quality measure. point in time Model Context Protocol
repository status active The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. as of fetch GitHub
mcp tools declared 7 tools Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. as of probe federal-regulations.caseyjhand.com
mcp endpoint status ok The server listed 7 functions when asked. as of probe federal-regulations.caseyjhand.com

Where to get it

Related, by what their authors tagged them

  • com.datakoot/regulatory-intel-mcp — last commit 2026-08-02, shares federal-register, regulations
    US Federal Register for AI agents: rules, notices and executive orders. No API keys.
  • Regulatory & Compliance Intelligence MCP — last commit 2026-07-16, shares federal-register
    Regulatory compliance, FDA recalls, federal register, enforcement actions & comment deadlines.
  • GovRider — last commit 2026-03-12, shares government
    Match tech products and consulting services to live government tenders, grants, and RFPs
  • io.github.civdotiq/civiq — last commit 2026-08-06, shares government
    U.S. civic data for AI agents: reps, votes, bills, finance, lobbying, cited gov sources. 47 tools.
  • Government Contracts MCP — last commit 2026-07-16, shares government
    Government contract search and federal procurement data: SAM.gov opportunities + USASpending awards.
  • io.github.gabrielmahia/county-mcp — last commit 2026-07-18, shares government
    MCP server for Kenyan county-government services and coordination
  • io.github.cyanheads/anime-mcp-server — last commit 2026-07-30, shares cyanheads
    Search anime/manga, franchise watch order, schedule, characters, rankings, studio filmography.
  • io.github.cyanheads/arxiv-mcp-server — last commit 2026-07-27, shares cyanheads
    Search arXiv, fetch paper metadata, and read full-text content.
  • io.github.cyanheads/astronomy-mcp-server — last commit 2026-07-31, shares cyanheads
    Offline observational astronomy: positions, rise/set, moon phases, eclipses, and seasons.
  • io.github.cyanheads/attack-surface-mcp-server — last commit 2026-07-30, shares cyanheads
    Passive external attack-surface mapping: CT subdomains, DNS, TLS, HTTP posture, RDAP/WHOIS, Shodan.

These share tags the maintainers applied themselves, such as federal-register, regulations, government, cyanheads. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.

This is not a recommendation and not a test result. It is a map of what the authors said their work is about.

Also from cyanheads

How the author describes it

Topics the maintainer set on GitHub: ai-agents, cyanheads, ecfr, federal-register, government, mcp, mcp-server, model-context-protocol, regulations, typescript.

This record as data

Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.

GET /api/v1/entries/mcp_server.json

Sources

  1. cyanheads/federal-regulations-mcp-server on GitHub — GitHub, observed , trust tier 3.
  2. Tools declared by the MCP server at https://federal-regulations.caseyjhand.com/mcp — federal-regulations.caseyjhand.com, observed , trust tier 4.
  3. Official MCP Registry — Model Context Protocol, observed , trust tier 1.