federal-regulations-mcp-server
io.github.cyanheads/federal-regulations-mcp-servercyanheadsstreamable-httpv0.6.2Scanned
Search and trace US federal rules across the Federal Register, eCFR, and Regulations.gov.
7 tools: 7 only read.
- Reads private data · 4
- Reads text others write · 5
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the federal-regulations-mcp-server can do
The federal-regulations-mcp-server is published by the GitHub account cyanheads. It has 7 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
4 tools read private data (regulations_search_rules, regulations_get_document, regulations_find_comments and 1 more); 5 tools bring in text other people can write (regulations_search_rules, regulations_get_document, regulations_browse_cfr and 2 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 0.6.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Only reads 7Show 7 read-only tools
regulations_browse_cfrExplore the codified Code of Federal Regulations via eCFR in three modes.Reads text others writeNo findings
Why it is in this group
- The name "regulations_browse_cfr" says "browse": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe name "regulations_browse_cfr" says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it 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`.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
regulations_find_commentsFetch public comments on a Federal Register document or a Regulations.gov docket — the unique corpus of what citizens and organizations actually submitted.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "regulations_find_comments" says "find": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "document": it reads documents.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe name "regulations_find_comments" says "find" and "comment": it reads comments, which other people can write.
- untrusted-inputThe description's first sentence says "fetch" and "comment": it reads comments, which other people can write.
Description, as the server wrote it 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 the body, upstream submission classification and attachment download URLs. When attachments exist and the body is empty or just a cover note, attachmentOnly is true. Requires REGULATIONS_GOV_API_KEY (free at https://api.data.gov/signup/).
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
regulations_get_cfr_sectionRead the codified text at a CFR location via eCFR — current or as of a past date.No findings
Why it is in this group
- The name "regulations_get_cfr_section" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
regulations_get_docketPull a rulemaking docket from Regulations.gov by docket ID (e.g.No findings
Why it is in this group
- The name "regulations_get_docket" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
regulations_get_documentFetch one Federal Register document by its FR document number — full metadata (title, type, agencies, abstract, action, effective/comment dates, RINs, EO 12866 significance, and fo…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "regulations_get_document" says "get": a word for reading.
What it can reach
- private-dataThe name "regulations_get_document" says "get" and "document": it reads documents.
- private-dataThe description's first sentence says "fetch" and "document": it reads documents.
- untrusted-inputThe description's first sentence says "fetch" and "comment": it reads comments, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
regulations_list_open_commentsList 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, an…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "regulations_list_open_comments" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "document": it reads documents.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe name "regulations_list_open_comments" says "list" and "comment": it reads comments, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "comment": it reads comments, which other people can write.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
regulations_search_rulesSearch 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,…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "regulations_search_rules" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "search" and "document": it reads documents.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:31 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:regulations_find_commentsOnly readsdescription
- Changed:regulations_list_open_commentsOnly readsinputSchema
- Changed:regulations_search_rulesOnly readsinputSchema
Tools7 changed.~7 changedView diff
- Changed:regulations_browse_cfrOnly readsdescriptioninputSchema
- Changed:regulations_find_commentsOnly readsinputSchema
- Changed:regulations_get_cfr_sectionOnly readsinputSchema
- Changed:regulations_get_docketOnly readsdescriptioninputSchema
- Changed:regulations_get_documentOnly readsdescriptioninputSchema
- Changed:regulations_list_open_commentsOnly readsinputSchema
- Changed:regulations_search_rulesOnly readsdescriptioninputSchema
Install
Pinned to version 0.6.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http federal-regulations https://federal-regulations.caseyjhand.com/mcpclaude mcp add --transport http federal-regulations https://federal-regulations.caseyjhand.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__federal-regulations__regulations_search_rules",
"mcp__federal-regulations__regulations_get_document",
"mcp__federal-regulations__regulations_browse_cfr",
"mcp__federal-regulations__regulations_get_cfr_section",
"mcp__federal-regulations__regulations_get_docket",
"mcp__federal-regulations__regulations_find_comments",
"mcp__federal-regulations__regulations_list_open_comments"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as federal-regulations. Review it before you use it.
Capability tags behind 5 rules
- mcp__federal-regulations__regulations_search_rules private-data, untrusted-input
- mcp__federal-regulations__regulations_get_document private-data, untrusted-input
- mcp__federal-regulations__regulations_browse_cfr untrusted-input
- mcp__federal-regulations__regulations_find_comments private-data, untrusted-input
- mcp__federal-regulations__regulations_list_open_comments private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.cyanheads/federal-regulations-mcp-server/verify?hash=277f9fa894cec8d858adc39cec10088024b5b5200ae0062bd257be741ebb01d5" | jq -e '.changed == false'Pinned hash 277f9fa894ce, from Nov 13, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.cyanheads/federal-regulations-mcp-server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.cyanheads/federal-regulations-mcp-server)Source: MCP Registry · repository. Synced Nov 13, 2026, 17:18 UTC.
federal-regulations-mcp-server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the federal-regulations-mcp-server safe?
- No scan can promise that. What its definitions show: 7 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the federal-regulations-mcp-server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the federal-regulations-mcp-server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the federal-regulations-mcp-server have?
- 7 tools: 7 read. regulations_search_rules, regulations_get_document, regulations_browse_cfr, regulations_get_cfr_section, regulations_get_docket, regulations_find_comments and regulations_list_open_comments.
Does the federal-regulations-mcp-server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the federal-regulations-mcp-server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the federal-regulations-mcp-server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.