# Federal Register (npm · @pipeworx/mcp-federal-register)

Federal Register MCP — US Federal Register API (free, no auth)

- Trust score: 81/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 70/100, [markdown](https://verifymcp.io/servers/pipeworx-io-federal-register/federal-register-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-federal-register/federal-register-mcp)
- npm · `@pipeworx/mcp-federal-register`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-federal-register/pipeworx-mcp-federal-register.md), [page](https://verifymcp.io/servers/pipeworx-io-federal-register/pipeworx-mcp-federal-register)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-federal-register`
- Version: `0.2.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-federal-register).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-federal-register -- npx -y @pipeworx/mcp-federal-register
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-federal-register": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-federal-register"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-federal-register": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-federal-register"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-federal-register -- npx -y @pipeworx/mcp-federal-register
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-federal-register": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-federal-register"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-federal-register --command npx --arg -y --arg @pipeworx/mcp-federal-register
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-federal-register:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-federal-register"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-federal-register": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-federal-register"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-federal-register -t stdio -c npx -a -y @pipeworx/mcp-federal-register
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-federal-register": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-federal-register"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 81, +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.

### 2026-11-02 (score 80, +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.

### 2026-11-01 (score 79, +1)

- [security regression] 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.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional improvement] Stability: unverified → 0.07
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.1 → 0.2.2

### 2026-10-31 (score 78, +15)

- [security improvement] Malware scan: unverified → pass
- [functional regression] Security disclosure: unverified → fail

### 2026-10-30 (score 63)

First indexed and scored.

## MCP tools (3)

### `search_documents` (~757 tokens)

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.

Input parameters:

- `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…

### `get_document` (~95 tokens)

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.

Input parameters:

- `number` (string, required): Federal Register document number (e.g., "2024-12345")

### `recent_rules` (~111 tokens)

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.

Input parameters:

- `limit` (number): Number of results to return (default 20, max 100)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-federal-register/pipeworx-mcp-federal-register#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 79
- 2026-10-31: 78
- 2026-10-30: 63

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-federal-register
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-federal-register
- Repository: https://github.com/pipeworx-io/mcp-federal-register
- Website: https://pipeworx.io/packs/federal-register
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-federal-register/pipeworx-mcp-federal-register.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-federal-register/pipeworx-mcp-federal-register.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-federal-register/pipeworx-mcp-federal-register