FedReg Tracker

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Federal regulatory intelligence from the Federal Register: search rules and notices, track deadlines

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "FedReg Tracker": {
      "url": "https://fedregtracker.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (12)

• search_federal_regulations read-only

  Search U.S. Federal Register documents (final rules, proposed rules, notices, presidential documents) live from FederalRegister.gov. Filter by keywords, agency, document type, publication/comment/effective dates, CFR title and part, RIN, docket or industry. Every result states its legal status (a proposed rule is never binding) and official links. No account needed.

  Parameters:

  • rin — string
  • page — integer
  • limit — integer
  • order
  • query — string — Keywords. Supports quotes for phrases.
  • agency — array — Agency abbreviations or slugs.
  • cfr_part — string
  • industry
  • cfr_title — integer
  • docket_id — string
  • significant — boolean
  • effective_to — string — Effective on or before.
  • published_to — string — Latest publication date.
  • document_type — array
  • effective_from — string — Effective on or after.
  • published_from — string — Earliest publication date.
  • comments_close_to — string — Comment period closes on or before.
  • comments_close_from — string — Comment period closes on or after.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get_regulatory_document read-only

  Full structured record for one Federal Register document: status, agencies, publication/comment/effective dates, RINs, dockets, CFR parts, official links, linked rulemakings, deadline history, any earlier Public Inspection filing, and (when configured) the Regulations.gov docket title, comment period and posted comment count. Also finds documents still on Public Inspection.

  Parameters:

  • document_number (required) — string — Federal Register document number, e.g. 2026-12345.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• track_federal_regulations

  Save a persistent watchlist. FedReg Tracker then monitors the Federal Register and Public Inspection on its own schedule and queues alerts and deadline reminders, with no chat open. Example: 'Track new cybersecurity regulations affecting federal contractors' → {name:'cyber-contractors', filters:{keywords:['cybersecurity'], cfr:[{title:48}]}}. Requires an access key.

  Parameters:

  • filters (required) — object — What to watch. All dimensions you set must match; any value within one may match. rins, dockets and document_numbers match on their own.
  • name — string
  • alert_preferences — object

  Hints: read-only no · destructive no · idempotent no · open-world no

• manage_regulatory_watchlist destructive

  Manage this account's watchlists. action=list needs nothing else; other actions need watchlist (name or id). update accepts new filters, alert_preferences or new_name.

  Parameters:

  • action (required)
  • filters — object — What to watch. All dimensions you set must match; any value within one may match. rins, dockets and document_numbers match on their own.
  • new_name — string
  • watchlist — string — Watchlist name or id.
  • alert_preferences — object

  Hints: read-only no · destructive yes · idempotent no · open-world no

• list_regulatory_alerts

  New alerts for this account's watchlists, highest priority first: new publications, Public Inspection filings (labeled prepublication), deadline extensions, effective-date changes, withdrawals, corrections and deadline reminders. Reading marks them delivered unless peek=true. An empty list means nothing new.

  Parameters:

  • peek — boolean
  • limit — integer
  • status
  • watchlist — string — Watchlist name or id.

  Hints: read-only no · destructive no · idempotent no · open-world no

• get_regulatory_timeline read-only

  Lifecycle of a rulemaking: proposed rule, comment periods, extensions, final rule, effective date, corrections and withdrawals, with observed events and deadline history. Give a RIN, a rulemaking_id or a document_number. Links are 'confirmed' (shared RIN) or 'probable' (shared docket); missing stages are never invented.

  Parameters:

  • rin — string
  • rulemaking_id — string
  • document_number — string — Federal Register document number, e.g. 2026-12345.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get_regulatory_deadlines read-only

  Upcoming comment deadlines or effective dates from the documents' structured fields, filtered by date range, agency, keywords, or one of your watchlists. Dates are calendar dates as published.

  Parameters:

  • to — string — End date (default 30 days after start).
  • from — string — Start date (default today).
  • limit — integer
  • query — string
  • agency — array
  • watchlist — string — Watchlist name or id.
  • deadline_type
  • document_type — array

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• compare_regulatory_documents read-only

  Compare two Federal Register documents (or the latest proposed and final rule for a RIN): exact metadata differences plus sentence-level text differences with verbatim excerpts. Text comparison is labeled partial; it is not a legal redline.

  Parameters:

  • rin — string
  • document_a — string — Federal Register document number, e.g. 2026-12345.
  • document_b — string — Federal Register document number, e.g. 2026-12345.
  • include_text — boolean

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get_cfr_changes read-only

  Changes to codified CFR text from the eCFR (ecfr.gov): which sections got a new version, when (version, amendment and eCFR issue dates), whether eCFR marks it substantive or removed, links to the eCFR page and XML for that date, and Federal Register documents that probably made the change. Parts in watchlists are checked daily; any other part is read on first request. Give cfr_title and cfr_part (or a section like 63.2), or a watchlist with CFR filters. Version metadata, not a text diff; the eCFR is not the official legal edition.

  Parameters:

  • limit — integer
  • since — string — Earliest version date (default 90 days ago).
  • until — string — Latest version date.
  • section — string — Section, e.g. 63.2.
  • cfr_part — string — Part, e.g. 63 or 1910.
  • cfr_title — integer
  • watchlist — string — Watchlist name or id.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get_regulatory_intelligence_brief read-only

  A structured, source-linked brief for one document: what happened, agency, status, who may be affected (from your watchlist when given), why it may matter, key dates, a suggested next step, sources, confidence and limitations. Built from source fields, not generated guesses.

  Parameters:

  • document_number (required) — string — Federal Register document number, e.g. 2026-12345.
  • watchlist — string — Watchlist name or id.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• manage_business_profile

  Optional business profile used to suggest relevance: industries, NAICS codes, business size, regions, regulated activities, interests, federal contractor status. Give only what helps monitoring. action=get reads it.

  Parameters:

  • action
  • industries — array
  • naics_codes — array
  • business_size
  • operating_regions — array
  • federal_contractor — boolean
  • regulated_activities — array
  • regulatory_interests — array

  Hints: read-only no · destructive no · idempotent no · open-world no

• rate_regulatory_alert

  Tell FedReg Tracker how relevant a document was: relevant, not_relevant, high_priority, already_reviewed, more_like_this or stop_tracking (no more alerts for that document).

  Parameters:

  • document_number (required) — string — Federal Register document number, e.g. 2026-12345.
  • rating (required)

  Hints: read-only no · destructive no · idempotent no · open-world no

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.