mcpbeat Sign in

FRTracker — Federal Regulatory Research MCP Server

by frtracker Your server? Claim it
answering

FRTracker — Federal Regulatory Research is answering right now. Last checked 12 min ago. It exposes 10 tools.

Source-linked US federal regulations: CFR provision history, obligations, rules, comments.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 74 days of history · worst day 96%
74 days agonow
100.0%
Uptime 24h
91 of 91 checks
10
Tools
read from the server
161 ms
Response time
average over 24h
authentication required
Access
streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 27 August 2026. No other catalogue keeps this.

27 Aug a tool appeared rules_amending

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add regulatory-research --transport http https://frtracker.app/mcp
Settings → Connectors → Add custom connector, then paste this address
https://frtracker.app/mcp
~/.codex/config.toml
[mcp_servers.regulatory-research]
url = "https://frtracker.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "regulatory-research": {
      "url": "https://frtracker.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "regulatory-research": {
      "type": "http",
      "url": "https://frtracker.app/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

rules
list_rules
List Federal Register documents with filters: agency slug, document type, rulemaking pathway (interim_final/temporary/direct_final = notice-and-comment bypass classes), or docket id. Requires an API key.
rules_amending
Which final rules amend a CFR part or section, read from each rule's own amendatory instructions ("Amend § 52.2120 by..."). Returns the rules, the sections each addresses, and dates. This reports what a rule SAYS it amends — it is not an attribution of any observed text change to that rule. Covers 2020-present; absence means not indexed, not that no rule amended it. No API key required.
lookup
lookup_provision
Look up a CFR provision by citation (e.g. "21 CFR 1304.04") or by an exact quotation, optionally as of a past date. Returns the provision text with a ProvisionEvidence object (source, snapshot date, hashes). Explicitly reports ambiguity or no-match instead of guessing. Requires a free API key.
obligations
list_obligations
List extracted regulatory obligations ("who must do what") with filters: agency, deontic class, free text. Obligations are machine-extracted with quality tiers; they are not legal advice. Requires an API key.
provision
get_provision_history
Documented change history for a CFR provision by canonical id (e.g. "21-cfr-1304.04(a)"): before/after text, computed redline, observed dates, and candidate final rules. 404 when the provision is not in the documented-change set — absence of a documented change is not a claim that nothing changed. No API key required.
recent
recent_cfr_changes
Most recent detected changes to CFR text (title, part, name, dates), newest first. No API key required.
regulations
search_regulations
Full-text search over Federal Register documents and extracted obligations (FTS5/BM25). Totals are approximate (total_exact: false). Requires an API key.
requirement
get_requirement
Detail for one extracted obligation by id, including its source rule and citation URL. Requires an API key.
rule
get_rule_comments
Public comments for a Federal Register document (organization, title, date, body where available). Coverage is partial and stated in the response. Requires an API key.
stats
get_stats
Aggregate corpus statistics: documents, obligations, pairs, agencies, coverage dates. No API key required.

Endpoints

URLTransportStateLatencyChecked
https://frtracker.app/mcp streamable-http needs auth 336 ms 12 min ago

Alternatives to FRTracker — Federal Regulatory Research

same job, measured the same way
Federal Regulations MCP Server
by cyanheads

Search and trace US federal rules across the Federal Register, eCFR, and Regulations.gov.

255 installs/wk 7 tools answering
Fcc Regulations
by pipeworx-io

FCC Regulations MCP — US Federal Communications Commission rules (47 CFR).

298 installs/wk 46 tools answering
SquarePact Federal Procurement Regulations
by squarepact

Search, quote and link U.S. federal procurement regulations from official sources.

answering
US Federal Regulations (CFR)
by openkrill

Read a CFR or eCFR section, or search US federal regulations and the Federal Register.

5 tools answering
Regulations Gov
by pipeworx-io

Regulations.gov MCP — federal regulatory dockets, documents, public comments

327 installs/wk 49 tools answering
US Code of Federal Regulations
by mccallar

Look up, search, and track changes to the US Code of Federal Regulations (eCFR).

232 installs/wk local only
U
US Legal Case Search
by memoryapi

US legal case search: court decisions and company litigation history

3 tools answering
eCFR.io Federal Regulations
by ecfr

Search and read US federal regulations with legal and inline citations linking to ecfr.io.

answering

FRTracker — Federal Regulatory Research — questions

Answers built from our own checks of this server.

What can FRTracker — Federal Regulatory Research do?
It exposes 10 tools, read directly from the server on our last check. Among them: get_provision_history, get_requirement, get_rule_comments, get_stats, list_obligations, list_rules and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is FRTracker — Federal Regulatory Research working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 161 ms. The bar chart above shows every period we have measured.
Is FRTracker — Federal Regulatory Research still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect FRTracker — Federal Regulatory Research?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does FRTracker — Federal Regulatory Research need an API key?
Yes. Every time we knock, FRTracker — Federal Regulatory Research answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is FRTracker — Federal Regulatory Research?
It answers our handshake in 161 ms on average, which is faster than 81% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.