# Federal Register (pypi · federal-register-mcp)

Federal Register proposed and final rules, notices, executive orders, and FAR cases. 8 tools.

- Trust score: 79/100 (medium)
- Change this week: +18
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- pypi · `federal-register-mcp`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-1102tools-federal-register-mcp/federal-register-mcp.md), [page](https://verifymcp.io/servers/com-1102tools-federal-register-mcp/federal-register-mcp)

## Channel facts

- Registry: `pypi`
- Package: `federal-register-mcp`
- Version: `1.0.9`
- 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-09-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 1 of 34 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1838 tokens (~229/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Federal Register MCP server?

Federal Register runs locally as a PyPI package, launched with uvx federal-register-mcp. 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 com-1102tools-federal-register-mcp -- uvx federal-register-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-1102tools-federal-register-mcp": {
      "command": "uvx",
      "args": [
        "federal-register-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-1102tools-federal-register-mcp": {
      "command": "uvx",
      "args": [
        "federal-register-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-1102tools-federal-register-mcp -- uvx federal-register-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-1102tools-federal-register-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "federal-register-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-1102tools-federal-register-mcp --command uvx --arg federal-register-mcp
```

### Hermes

```yaml
mcp_servers:
  com-1102tools-federal-register-mcp:
    command: "uvx"
    args: ["federal-register-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-1102tools-federal-register-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "federal-register-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-1102tools-federal-register-mcp -t stdio -c uvx -a federal-register-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-1102tools-federal-register-mcp": {
      "command": "uvx",
      "args": [
        "federal-register-mcp"
      ]
    }
  }
}
```

## 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-09-20 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 76, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-13 (score 61, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 1.0.5 → 1.0.9
- [functional] Package version: 1.0.5 → 1.0.8
- [functional] Package version: 1.0.5 → 1.0.7

### 2026-09-11 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (8)

### `search_documents` (~487 tokens)

Search Federal Register documents.

The primary tool for finding proposed rules, final rules, notices,
and presidential documents published in the Federal Register since 1994.

Key parameters:
\- agencies: list of agency URL slugs (OR logic). Use list_agencies() to find slugs.
  Common: 'defense-department', 'general-services-administration',
  'federal-procurement-policy-office', 'small-business-administration'
\- doc_types: PRORULE (proposed rule), RULE (final rule), NOTICE, PRESDOCU
\- term: full-text keyword search (strips stop words)
\- docket_id: docket identifier (token match). 'FAR Case 2023-008' = exact,
  'FAR Case 2023' = all 2023 cases; partial tokens like 'FAR Case 20'
  match nothing
\- regulation_id_number: RIN (precise match, e.g., '9000-AO56')
\- pub_date_gte/lte: publication date range (YYYY-MM-DD)
\- comment_date_gte/lte: comment close date range
\- effective_date_gte/lte: effective date range
\- correction: True for modern corrections (C1- prefix documents)
\- significant: True for EO 12866 significant rules only
\- cfr_title + cfr_part: documents affecting a CFR location, e.g.
  cfr_title=48, cfr_part='52' for FAR part 52 (part accepts ranges
  like '1-99'; cfr_part requires cfr_title)

Count caps at 10,000 for broad queries. Use date ranges for accurate counts.
per_page capped at 100 to stay within MCP response size limits.

Input parameters:

- `agencies`
- `cfr_part`
- `cfr_title`
- `comment_date_gte`
- `comment_date_lte`
- `correction`
- `doc_types`
- `docket_id`
- `effective_date_gte`
- `effective_date_lte`
- `order` (string)
- `page` (integer)
- `per_page` (integer)
- `pub_date_gte`
- `pub_date_lte`
- `regulation_id_number`
- `significant`
- `term`

### `get_document` (~109 tokens)

Get full details for a single Federal Register document by number.

Returns all available fields including full text URLs, docket info,
RIN details, page views, topics, corrections, and CFR references.

Document numbers look like '2026-03065' (modern), 'E9-12940' or
'X94-70302' (legacy pre-2011 archive), or 'C1-2026-01234' (corrections).

Input parameters:

- `document_number` (string, required)

### `get_documents_batch` (~67 tokens)

Fetch multiple documents in one call (up to ~20).

Pass a list of document numbers. More efficient than individual calls.
Always returns {count, results, [errors]}; errors.not_found lists any
requested numbers the API could not locate.

Input parameters:

- `document_numbers` (array, required)

### `get_facet_counts` (~200 tokens)

Get document counts grouped by type, agency, topic, or time period.

Accepts the same filter conditions as search_documents. Returns
aggregated counts without individual document results.

Facets: type, agency, topic (categorical) plus daily, weekly, monthly,
quarterly, yearly (publication-date buckets, useful for trend lines).

Useful for understanding the volume of rulemaking by agency, type, or
over time within a date range before drilling into specific documents.

At least one filter (agencies, doc_types, term, pub_date_gte/lte, or
cfr_title) is required. An unfiltered facet query returns the entire
all-time aggregate.

Input parameters:

- `agencies`
- `cfr_part`
- `cfr_title`
- `doc_types`
- `facet` (string, required)
- `pub_date_gte`
- `pub_date_lte`
- `term`

### `get_public_inspection` (~238 tokens)

Get current public inspection documents (pre-publication).

Public inspection documents are FR documents filed for publication but
not yet published. Updated business days only.

The current-PI endpoint does NOT support server-side filtering. This
tool fetches all current PI documents and filters client-side by
agency and/or keyword in the title.

Useful for getting early notice of upcoming regulatory actions.

Parameters:
\- agency_filter: case-insensitive substring match against each
  document's agency slugs, names, and raw names. CAUTION: PI documents
  list only the FILING sub-agency, so a parent slug like
  'defense-department' will not match a Defense Logistics Agency
  filing. Prefer a short distinctive fragment ('defense', 'acquisition
  regulations') over a full parent slug.
\- keyword_filter: substring match against document titles
\- limit: max documents returned after filtering (default 50, max 500).
  Unfiltered dumps can exceed 170KB; narrow with filters or raise the cap.

Input parameters:

- `agency_filter`
- `keyword_filter`
- `limit` (integer)

### `list_agencies` (~203 tokens)

List agencies with their IDs, names, slugs, and parent agencies.

Use the 'slug' values with search_documents() and other tools.
Common procurement slugs:
\- federal-procurement-policy-office (OFPP)
\- defense-department (DoD)
\- general-services-administration (GSA)
\- defense-acquisition-regulations-system (DARS/DFARS)
\- small-business-administration (SBA)
\- national-aeronautics-and-space-administration (NASA)
\- veterans-affairs-department (VA)

Parameters:
\- query: optional case-insensitive substring match against name, short_name,
  and slug. Recommended: narrow results before pulling full detail.
\- include_detail: if False (default), returns only id/name/short_name/slug/parent_id.
  If True, returns all fields (description, urls, etc.). The full dump is ~700KB.

Input parameters:

- `include_detail` (boolean)
- `query`

### `open_comment_periods` (~249 tokens)

Find documents with currently open comment periods, soonest deadline first.

Covers proposed rules, notices, AND final/interim rules that accept
comments (dozens of RULE-type documents have open periods at any time).
Queries for comment close date >= today, scans up to 500 matching
documents oldest-published first (where the soonest deadlines live),
sorts by close date, and returns the first `limit`.

Honest bound: total_open is the API's true government-wide count;
scanned is how many this call examined. When total_open exceeds
scanned, narrow with agencies/term for exhaustive coverage. A very
recently published document with an unusually short comment window
can fall outside the scan in that oversubscribed case.

Default: searches all agencies. Pass agency slugs to narrow scope.
Common for procurement: ['federal-procurement-policy-office',
'defense-department', 'general-services-administration']

Parameters:
\- limit: max documents returned after sorting (default 50, max 100).
  Unfiltered dumps across all agencies can approach 200KB.

Input parameters:

- `agencies`
- `limit` (integer)
- `term`

### `far_case_history` (~285 tokens)

Get all Federal Register documents for a FAR/DFARS case or FAC.

Pass a docket ID like 'FAR Case 2023-008' (or a FAC number like
'FAC 2025-06'). Runs BOTH a docket-id search and a quoted full-text
search, then merges the two result sets (deduped by document number)
in chronological order to show the full rulemaking progression:
ANPRM -> proposed rule -> final rule -> corrections. The dual query
matters: FAC introduction and companion documents often carry only
internal docket numbers, so a docket-only search returns a partial set.

Docket matching is token-based, not substring: 'FAR Case 2023' matches
all 2023 cases (token '2023' matches '2023-008'), but a partial token
like 'FAR Case 20' matches nothing. Be specific to avoid false positives.

Each underlying search returns at most 100 documents. truncated=True
flags that one of the searches hit that cap (docket_matches and
term_matches carry the API's full counts); narrow the docket_id if so.

Minimum docket_id length is 3 characters to prevent token matches that
return unrelated documents (e.g. 'x' matched 65 random dockets in 0.1.x).

Input parameters:

- `docket_id` (string, required)

## Diagnostics

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

## Score history

- 2026-09-21: 79
- 2026-09-20: 79
- 2026-09-19: 78
- 2026-09-18: 78
- 2026-09-17: 77
- 2026-09-16: 77
- 2026-09-15: 76
- 2026-09-14: 61
- 2026-09-13: 61
- 2026-09-12: 75
- 2026-09-11: 75
- 2026-09-10: 74
- 2026-09-09: 74
- 2026-09-08: 73
- 2026-09-07: 73
- 2026-09-06: 72
- 2026-09-05: 72
- 2026-09-04: 71
- 2026-09-03: 71
- 2026-09-02: 70
- 2026-09-01: 70
- 2026-08-31: 69
- 2026-08-30: 66
- 2026-08-29: 66
- 2026-08-28: 66
- 2026-08-27: 66
- 2026-08-26: 66
- 2026-08-25: 64
- 2026-08-24: 64

## Common questions

### What is the Federal Register MCP server?

Federal Register is an MCP server listed in the public MCP registry as com.1102tools/federal-register-mcp. Federal Register proposed and final rules, notices, executive orders, and FAR cases. 8 tools. This page covers its PyPI package (federal-register-mcp).

### Is the Federal Register MCP server safe to use?

Federal Register scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. 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 8 tools: search_documents, get_document, get_documents_batch, get_facet_counts, get_public_inspection, and 3 more. Their descriptions and schemas cost roughly 1,838 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 21 September 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

- PyPI project: https://pypi.org/project/federal-register-mcp/
- Socket report: https://socket.dev/pypi/package/federal-register-mcp
- Repository: https://github.com/1102tools-dev/federal-contracting-mcps
- Website: https://1102tools.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-1102tools-federal-register-mcp/federal-register-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-1102tools-federal-register-mcp/federal-register-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-1102tools-federal-register-mcp/federal-register-mcp