Compatible with every major AI agent and IDE
What is the Federal Register MCP Server?
Connect your AI agent to the Federal Register and navigate the vast landscape of U.S. government regulations and public notices through natural language.
What you can do
- Document Search — Search through millions of documents published since 1994 using filters like agency, date, document type, and RIN.
- Public Inspection — Access the 'Public Inspection' desk to see documents scheduled for publication before they officially hit the register.
- Agency Intelligence — List all federal agencies and retrieve detailed profiles, including their recent regulatory activity and metadata.
- Regulatory Tracking — Monitor specific dockets, Regulation Identifier Numbers (RIN), and CFR titles/parts to stay ahead of compliance changes.
- Deep Metadata — Fetch full document details, including publication dates, page ranges, and agency contact information.
How it works
- Subscribe to this server
- No API key is required for standard public access
- Start querying the Federal Register from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Legal Professionals — quickly find specific rules or notices without navigating complex government portals
- Compliance Officers — track regulatory changes and public inspection filings in real-time
- Policy Researchers — analyze agency activity and historical document trends via AI-driven search
Built-in capabilities (9)
Fetch a single agency by slug
Retrieve all documents currently on public inspection
Fetch a single published document
Fetch multiple published documents
Retrieve documents on public inspection on a specific date
Fetch a single public inspection document
List all federal agencies
Search published Federal Register documents
Search public inspection documents
Why Claude Desktop?
Claude Desktop is the definitive way to connect Federal Register to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 9 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Federal Register in Claude Desktop
Federal Register and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Federal Register to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Federal Register in Claude Desktop
The Federal Register MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 9 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Federal Register for Claude Desktop
Every tool call from Claude Desktop to the Federal Register MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find documents from a specific agency like the FDA?
First, use the list_agencies tool to find the correct agency slug or ID. Then, use the search_documents tool and provide that slug in the agencies parameter to filter results.
Can I see documents before they are officially published in the daily register?
Yes! Use the search_public_inspection or get_current_public_inspection tools. These access the 'Public Inspection' desk, which contains documents filed for public review before their formal publication date.
Is it possible to search for documents related to a specific Regulation Identifier Number (RIN)?
Absolutely. Use the search_documents tool and provide the rin parameter. This will return all published documents associated with that specific regulatory action.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
Fintoc
12 toolsAccess bank accounts, movements, and initiate transfers via AI agents with Fintoc.

Join
10 toolsManage recruiting, jobs, and candidates via JOIN API.

Omni BI Intelligence
10 toolsInteract with Omni BI dashboards, models, and data exports — run queries and track metrics directly from your AI agent.

HTMLCSSToImage
10 toolsGenerate high-quality images and PDFs from HTML/CSS or URLs directly from your AI agent.
