Federal Register
NPM · @PIPEWORX/MCP-FEDERAL-REGISTER · 2 COMPONENTS
Federal Register MCP — US Federal Register API (free, no auth)
Available components
Last scanned (11 hours ago)
Scores higher than 69% of npm servers
Category News and Social
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-federal-register). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1016 tokens (~338/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.07 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.1 → 0.2.2 functional
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 63
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-federal-register@0.2.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-federal-register |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-federal-register/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635941527 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:9c4f8521ec69bf6d92d00bf7a374a17e78f7ed53193b6c9f6fb9e97e9363463ddd7ca9755783078f725693af8c2fc153815d7f8b4f2759ab41844bbee |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_document ~95
Get full details for a Federal Register document by its document number (e.g., "2024-12345"). Returns title, abstract, full text link, agencies, dates, and docket information. For a presidential document (executive order, proclamation, memorandum) this also includes executive_order_number, signing_date, and citation.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | Federal Register document number (e.g., "2024-12345") |
No output schema declared.
No examples provided.
recent_rules ~111
Browse the most recently published final rules and regulations from the Federal Register, **with no topic filter** — returns whatever was published most recently across every agency (FAA airworthiness directives, Coast Guard safety zones, EPA tolerance exemptions, etc.). For questions about a specific topic ("EV tax credits", "AI rules", "drug pricing"), use search_documents instead. Returns title, abstract, agency, effective dates, significance.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of results to return (default 20, max 100) |
No output schema declared.
No examples provided.
search_documents ~757
Search the US Federal Register by topic / keyword for proposed rules, final rules, notices, and presidential documents. **Use this whenever the question mentions a SUBJECT** ("EV tax credits", "AI export controls", "PFAS regulations", "clean energy", "ozempic labeling", etc.) — recent_rules takes no topic filter and would return random unrelated rules. For a STRUCTURED count/list ("how many executive orders in 2026", "list 2026 proclamations"), pass type:"presidential_document" plus presidential_document_type rather than relying on free-text query — a free-text search for "executive order" also matches documents that merely MENTION one, over- or under-counting the real set. To find or confirm ONE specific executive order by its number, pass executive_order_number instead — it scopes and filters for you, no type/presidential_document_type needed. Returns title, abstract, agency, publication date, links, and for presidential documents also executive_order_number, signing_date, and citation. The response always echoes filters_applied: a genuine zero still says exactly what was searched, so it is never a bare empty result. Examples: search_documents({query: "EV tax credit", type: "rule"}), search_documents({type: "presidential_document", presidential_document_type: "executive_order", since: "2026-01-01"}), search_documents({executive_order_number: "14435"}), search_documents({query: "Strait of Hormuz", since: "365d"}). Pass `since` to constrain to recent documents — without it the relevance ranker can return decade-old docs for sparse-term queries.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Agency slug filter (e.g., "environmental-protection-agency", "securities-and-exchange-commission") |
| executive_order_number | string | – | Look up ONE executive order by its number, e.g. "14435" or "EO 14435" — automatically scopes to type:"presidential_document" + presidential_document_type:"executive_order" and filters the result to a… |
| presidential_document_type | string | – | Only with type:"presidential_document" — narrows to one sub-type: "executive_order", "proclamation", "memorandum", "determination", "notice", or "other". This is the STRUCTURED way to count/list exec… |
| query | string | – | Search keywords (e.g., "clean energy tax credit"). Optional if type/agency/since/presidential_document_type/executive_order_number already scope the search — forcing a free-text term onto a structure… |
| since | string | – | Publication date floor. Accepts ISO date ("2025-01-01") or shorthand ("30d", "12m", "365d", "1y"). Recommended for any topical search to avoid stale results — the relevance ranker can surface 2004-20… |
| type | string | – | Document type filter: "rule", "proposed_rule", "notice", "presidential_document" — mapped internally to the Federal Register API's own codes (RULE/PRORULE/NOTICE/PRESDOCU); an unrecognized value is r… |
No output schema declared.
No examples provided.
How do I install the Federal Register MCP server?
Federal Register runs locally as an npm package, launched with npx -y @pipeworx/mcp-federal-register. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-federal-register
claude mcp add pipeworx-io-federal-register -- npx -y @pipeworx/mcp-federal-register
What is the Federal Register MCP server?
Federal Register is an MCP server listed in the public MCP registry as io.github.pipeworx-io/federal-register. Federal Register MCP, US Federal Register API (free, no auth). This page covers its npm package (@pipeworx/mcp-federal-register).
Is the Federal Register MCP server safe to use?
Federal Register scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Federal Register MCP server expose?
Federal Register exposes 3 tools: search_documents, get_document, recent_rules. Their descriptions and schemas cost roughly 963 tokens of context every time the server is loaded.
Is the Federal Register MCP server still maintained?
Federal Register is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Federal Register MCP server under?
Federal Register declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.