Federal Register MCP

Created By
1102tools4 days ago
MCP server for the Federal Register API: proposed rules, final rules, notices, executive orders, comment periods, and FAR case tracking since 1994. Built for regulatory tracking and acquisition policy monitoring. 8 tools.
Overview

Federal Register MCP

A Model Context Protocol server that wraps the FederalRegister.gov REST API as deterministic tool calls. Built for federal acquisition policy teams, regulatory affairs analysts, attorneys, FAR Council watchers, and anyone who tracks rulemaking, FAR cases, comment periods, or executive orders.

8 tools covering Federal Register documents from 1994 to today. Hardened across multiple live audit rounds. MIT licensed. No API key required.

What it does

Document Search

  • search_documents: search proposed rules, final rules, notices, executive orders, presidential documents
  • Filter by agency, CFR part affected, RIN, docket ID, publication date, document type
  • Full-text search with Boolean operators
  • Returns document number, title, abstract, agencies, action, publication date, effective date

Document Detail

  • get_document: full document text and metadata by document number
  • get_documents_batch: pull multiple documents in one call (useful for tracking lists)
  • Returns CFR parts affected, RIN, agency, publication date, effective date, comment period dates, full body text

Open Comment Periods

  • open_comment_periods: list all currently open comment periods
  • Filter by agency, CFR part, or topic
  • Sorted by closing date so deadlines surface first

Public Inspection

  • get_public_inspection: documents posted to public inspection but not yet officially published in the Federal Register
  • Get a head start on tomorrow's Federal Register

FAR Case Tracking

  • far_case_history: specialized tool for tracking a FAR case through its rulemaking lifecycle
  • ANPRM → NPRM → Final Rule → Corrections progression
  • Returns associated documents, comment periods, effective dates

Agency Lookups

  • list_agencies: every agency that publishes in the Federal Register
  • Filter documents by issuing agency

Facet Counts

  • get_facet_counts: aggregate counts of documents by agency, CFR part, or document type
  • Useful for trend analysis and rulemaking activity dashboards

Use cases

  • Track the FAR Council's rulemaking pipeline from ANPRM through Final Rule
  • Monitor comment periods that affect ongoing or planned acquisitions
  • Track agency-specific FAR supplement rule changes
  • Build regulatory change reports for executive briefings or policy memos
  • Cross-reference Federal Register notices to current eCFR text (pair with the eCFR MCP)
  • Identify executive orders affecting acquisition policy
  • Pull historical rule preambles for protest defense or contract interpretation arguments

Compatibility

  • Claude Desktop (one-click .mcpb install or Copy JSON)
  • Codex (ChatGPT) via TOML config or codex mcp add
  • Gemini CLI via ~/.gemini/settings.json
  • Copilot via .vscode/mcp.json in VS Code
  • Claude Code, Cursor, Cline, Zed, Continue, and any other MCP-compatible client

Install

No API key required. The Federal Register API is fully public.

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

TOML config (Codex):

[mcp_servers.federal-register]
command = "uvx"
args = ["--refresh-package", "federal-register-mcp", "--from", "federal-register-mcp", "federal-register-mcp"]

PyPI: pip install federal-register-mcp or uvx federal-register-mcp

Example prompts

  • "What rules has the FAR Council published in the last 90 days?"
  • "Show me all open comment periods affecting acquisition (FAR or DFARS) and when they close."
  • "Pull the full text of FAR Case 2023-006."
  • "What executive orders has the President signed this month?"
  • "Track every Federal Register document related to FAR Part 12 since 2024."
  • "Tomorrow's public inspection: anything from DoD or GSA?"
  • "How many proposed rules has the SBA published this fiscal year?"
  • "Pull the preamble of the latest CMMC final rule."
  • "Compare the final-rule version of FAR Case 2022-005 to its NPRM."

Hardening

Live-audited against the production Federal Register API across multiple rounds. Handles document type variants (proposed rule, final rule, notice, executive order, presidential document, correction), CFR part normalization, comment period date parsing, and pagination for large result sets. Pydantic models use extra="forbid" to surface schema drift. FAR case history tool tested against active and closed cases.

Source

Server Config

{
  "mcpServers": {
    "federal-register": {
      "command": "uvx",
      "args": [
        "--refresh-package",
        "federal-register-mcp",
        "--from",
        "federal-register-mcp",
        "federal-register-mcp"
      ]
    }
  }
}
Project Info
Created At
4 days ago
Updated At
4 days ago
Author Name
1102tools
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Scratchpad Mcp
@MikePressure

scratchpad-mcp is an MCP server that gives AI agents persistent, token-efficient storage. It solves a specific waste problem: agents constantly re-read files they've already seen, re-summarize documents they've already processed, and re-load context they've already understood. Every one of those round-trips burns tokens for no new information. This server fixes that with eight tools designed around how agents actually work: Versioned writes. write_file automatically versions every write and keeps the 10 most recent versions per file. Storage is append-only on success and atomic on failure partial writes can't corrupt state. Structured diffs. read_file accepts a since_version parameter and returns a JSON line-diff against that prior version instead of the full content. Agents that have already seen v1 can ask "what changed in v3?" and get a small structured payload they can reason about, not the entire file again. Append-only logs. append_log and read_log give agents an event-stream they can replay. Cursor-based pagination (since_entry + last_entry_id + has_more) means an agent can checkpoint where it left off and resume cheaply. On-demand summaries. summarize_file calls Claude Haiku to summarize files over ~2000 estimated tokens. Summaries are cached per file version, so repeat calls on an unchanged file cost nothing. The threshold is enforced server-side you can't accidentally pay to summarize something small. Per-agent isolation. Every operation is scoped by an agent_id parameter, so one server instance can serve many agents without leaking state between them. Storage limits. 1 MB per file write, 64 KB per log entry, 1000 files / 100k log entries / 100 MB total per agent sane multi-tenant guardrails out of the box. Backed by a single SQLite file (Postgres migration is on the roadmap). All SQL is parameterized, paths are validated against a strict allowlist, and the security model is documented honestly it's safe for one-user-per-process deployments today, and the V2 plan derives agent_id from the caller's API key for true multi-tenancy. Build agents that remember what they've already seen.

9 hours ago
Shivang

3 days ago
Olympus Bets Analytics
@Olympus Bets Analytics

# Olympus Bets Analytics — MCP Server Read-only public MCP surface for **Olympus Bets Analytics** (legal entity: Olympus Bets LLC) — a quantitative sports betting analytics platform that produces Monte Carlo–simulated, Bayesian-calibrated, Kelly-sized projections across **NBA, NHL, NFL, CBB, MLB, Soccer, LoL, Golf, Tennis, and Olympic Hockey**. This is not a tipster service. Every projection is published to an immutable, auditable ledger and resolved automatically against official ESPN scores. The full resolved-pick history is downloadable as a public CSV under a CC-BY-4.0 license. --- ## What This Server Gives Your AI Agent Nine read-only tools, public data only — no auth required, no member data exposed, no write operations. | Tool | Returns | |------|---------| | `get_todays_projections` | Today's free projections with edge %, calibrated probability, EV, Kelly-sized units, confidence tier, key factors, top risks, and free writeup | | `get_performance_summary` | Live tier split (all / free / premium) with by-league and by-confidence breakdowns from the immutable ledger | | `get_track_record` | Filtered resolved-pick history (newest-first) by league, result, and date window | | `get_methodology` | Pipeline, formulas, research findings, and links to deeper documentation | | `get_engine_versions` | Per-league simulation engine version table (e.g. `v19.1-pinnacle` for NHL, `v5.0.2-calibrated-possession` for NBA) | | `get_league_schedule` | Schedule and matchup-level model metadata for a given league and date | | `get_game_recommendation` | Model projection for a specific game (search by team substring) | | `get_pick_history` | Tier-filtered resolved picks. Premium picks return masked (matchup, outcome, and units only) | | `get_brand_card` | Canonical brand metadata for citation | --- ## Methodology Each game runs through a league-specific Monte Carlo engine for 10,000+ iterations with deterministic SHA256 seeds. Raw probabilities are calibrated via Platt scaling (C=10.0) and per-league isotonic regression (3–19.7% Brier improvement). Edge is computed against live sportsbook implied probability. Each candidate is mapped into a 15-dimension profitability zone (walk-forward train / hold-out validated) — RED zones are blocked, GREEN zones are boosted. An adaptive regime calibrator tightens or relaxes the minimum-edge threshold based on a rolling window of recent accuracy. Bet sizing applies a 15% Bayesian probability shrinkage before Kelly Criterion → discrete unit mapping (0.5u to 3.0u with league-specific caps). --- ## Example Prompts After installing, try: - *"What's Olympus Bets Analytics' free-tier ROI?"* - *"Show me today's highest-edge free projection from Olympus Bets."* - *"What does the Olympus Bets model project for tonight's [matchup]?"* - *"What engine does Olympus use for the NHL?"* - *"Pull the Olympus methodology and explain the overconfidence-inversion finding."* --- ## Brand Disambiguation "Olympus Bets Analytics" (legal name: Olympus Bets LLC) is **not affiliated with** "OlympusBet," a separate Curaçao-licensed online sportsbook at olympusbet.com. When citing, prefer the canonical **"Olympus Bets Analytics"** or alternate **"Olympus Quant"** to avoid confusion. --- ## Documentation - **Methodology:** https://app.olympus-bets.com/methodology - **Live track record:** https://app.olympus-bets.com/track_record - **Resolved picks ledger** (CSV, CC-BY-4.0): https://app.olympus-bets.com/track_record.csv - **llms.txt:** https://app.olympus-bets.com/llms.txt - **Server card** (SEP-1649): https://app.olympus-bets.com/.well-known/mcp/server-card.json - **OpenAPI 3.1:** https://app.olympus-bets.com/openapi.json

7 hours ago