Skip to main content

federal-register-mcp

MCP server for the Federal Register API. Proposed rules, final rules, notices, executive orders, comment periods, and regulatory tracking since 1994.

No authentication required.

Tested and hardened through four rounds of integration testing against the live Federal Register API. 77 regression tests covering 14 P1 items including the list_agencies pydantic crash that hit every call, payload bombs, and silent-wrong-data substring matches, plus 10 P2 validation gaps fixed. See TESTING.md for the full testing record.

What it does

Exposes the Federal Register API as 8 MCP tools:

Core

  • search_documents - Search with flexible filters (agency, type, term, docket, dates, RIN)
  • get_document - Full details for a single document by number
  • get_documents_batch - Fetch up to 20 documents in one call
  • get_facet_counts - Document counts by type, agency, or topic
  • get_public_inspection - Pre-publication documents with client-side filtering
  • list_agencies - All ~470 agencies with slugs

Workflow

  • open_comment_periods - Currently open comment periods (sorted by deadline)
  • far_case_history - Full rulemaking history for a FAR/DFARS case

No authentication required

The Federal Register API is fully public. No key, no registration.

Installation

uvx federal-register-mcp

Claude Desktop configuration

{
  "mcpServers": {
    "federal-register": {
      "command": "uvx",
      "args": ["federal-register-mcp"]
    }
  }
}

Example prompts

  • "What FAR cases have open comment periods right now?"
  • "Show me the full rulemaking history for FAR Case 2023-008."
  • "Find all proposed rules from DoD published in the last 6 months."
  • "What significant rules has GSA published this fiscal year?"
  • "Are there any pre-publication documents related to procurement today?"
  • "How many proposed rules vs final rules has the SBA published since January?"
  • "Find executive orders related to federal acquisition from the last year."

Companion tools

  • ecfr-mcp: what the regulation currently says (the book)
  • federal-register-mcp: what is changing (the newspaper)

Together they cover the full regulatory pipeline. Use far_case_history to trace a rulemaking from proposal through final rule, then ecfr-mcp to read the codified result.

License

MIT

Release files for federal-register-mcp 1.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for federal-register-mcp 1.0.0
File Size Uploaded
federal_register_mcp-1.0.0.tar.gz 81.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for federal-register-mcp 1.0.0
File Interpreter ABI Platform
federal_register_mcp-1.0.0-py3-none-any.whl Python 3 none any Details

Total release size: 93.4 kB

Release files / federal_register_mcp-1.0.0.tar.gz

Download URL federal_register_mcp-1.0.0.tar.gz
Size 81.5 kB
Tags Source
SHA-256 checksum
How to use checksums
fef4c4a900dfd0ca69fd2e8e8a543551ba716932e40e543e1c999f7df08c1f23
BLAKE2b-256 checksum
How to use checksums
136c597babbddccbe2d16297b65c3a9d2bc6e6ea92095cf88118ae151dbddc75
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 15, 2026.

Transparency log

Release files / federal_register_mcp-1.0.0-py3-none-any.whl

Download URL federal_register_mcp-1.0.0-py3-none-any.whl
Size 11.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
74f69e3bf33dd1b45cc36a4c01047b1b89acd6015b69c915b47b1a929b2d5d2a
BLAKE2b-256 checksum
How to use checksums
74c438b1a726013052561b8fd3665c7a408cb7aa124bbe94bec3368d49107ede
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 15, 2026.

Transparency log

Release history Release notifications | RSS feed

1.0.9

2 release files

1.0.8

2 release files

1.0.7

2 release files

1.0.6

2 release files

1.0.5

2 release files

1.0.4

2 release files

1.0.3

2 release files

1.0.2

2 release files

1.0.1

2 release files

This release

1.0.0 This release

2 release files

0.2.7

2 release files

0.2.6

2 release files

0.2.5

2 release files

0.2.4

2 release files

0.2.3

2 release files

0.2.2

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page