FRTracker — Federal Regulatory Research
REMOTE · FRTRACKER.APP · SCANNED SEP 24
Source-linked US federal regulations: CFR provision history, obligations, rules, comments.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1077 tokens (~107/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the FRTracker — Federal Regulatory Research MCP server?
FRTracker — Federal Regulatory Research is a hosted endpoint at https://frtracker.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · frtracker.app
claude mcp add --transport http app-frtracker-regulatory-research 'https://frtracker.app/mcp'
{
"mcpServers": {
"app-frtracker-regulatory-research": {
"url": "https://frtracker.app/mcp"
}
}
} {
"servers": {
"app-frtracker-regulatory-research": {
"type": "http",
"url": "https://frtracker.app/mcp"
}
}
} [mcp_servers.app-frtracker-regulatory-research] url = "https://frtracker.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-frtracker-regulatory-research": {
"type": "remote",
"url": "https://frtracker.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-frtracker-regulatory-research --url 'https://frtracker.app/mcp' --transport streamable-http
mcp_servers:
app-frtracker-regulatory-research:
url: "https://frtracker.app/mcp" {
"McpServers": {
"app-frtracker-regulatory-research": {
"Transport": "http",
"Url": "https://frtracker.app/mcp"
}
}
} assistant mcp add app-frtracker-regulatory-research -t streamable-http -u 'https://frtracker.app/mcp'
{
"mcpServers": {
"app-frtracker-regulatory-research": {
"type": "http",
"url": "https://frtracker.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://frtracker.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=frtracker.app | CN=WE1,O=Google Trust Services,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a113322287d95160ee78d944859ab32 |
| SANs: frtracker.app, status.frtracker.app, *.status.frtracker.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of frtracker.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| frtracker.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://frtracker.app/mcp | Verified | 200 | |
| http (plaintext) | http://frtracker.app/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_provision_history Get Provision History ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| canonical_id | string | yes | Canonical provision id, e.g. "21-cfr-1304.04(a)" |
No output schema declared.
No examples provided.
get_requirement Get Requirement ~38
Detail for one extracted obligation by id, including its source rule and citation URL. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Requirement id |
No output schema declared.
No examples provided.
get_rule_comments Get Rule Comments ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| doc | string | yes | Federal Register document number, e.g. "2024-12345" |
| offset | integer | – | Row offset for pagination |
No output schema declared.
No examples provided.
get_stats Get Stats ~28
Aggregate corpus statistics: documents, obligations, pairs, agencies, coverage dates. No API key required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_obligations List Obligations ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Agency slug |
| deontic | string | – | Deontic class |
| limit | integer | – | Max rows (default 25, max 100) |
| page | integer | – | Page number (default 1) |
| q | string | – | Full-text filter within obligations |
No output schema declared.
No examples provided.
list_rules List Rules ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Agency slug, e.g. "environmental-protection-agency" |
| docket | string | – | Docket id |
| limit | integer | – | Max rows (default 25, max 100) |
| page | integer | – | Page number (default 1) |
| pathway | string | – | Rulemaking pathway |
| type | string | – | Document type |
No output schema declared.
No examples provided.
lookup_provision Lookup Provision ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Optional YYYY-MM-DD snapshot upper bound (not in the future) |
| q | string | yes | Citation ("21 CFR 1304.04") or an exact quote from regulatory text |
No output schema declared.
No examples provided.
recent_cfr_changes Recent Cfr Changes ~51
Most recent detected changes to CFR text (title, part, name, dates), newest first. No API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max rows (default 50, max 200) |
No output schema declared.
No examples provided.
rules_amending Rules Amending ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max rules (default 50, max 200) |
| part | string | yes | CFR part, e.g. "52" |
| section | string | – | Optional section id, e.g. "52.2120". Omit for all rules touching the part. |
| title | string | yes | CFR title number, e.g. "40" |
No output schema declared.
No examples provided.
search_regulations Search Regulations ~98
Full-text search over Federal Register documents and extracted obligations (FTS5/BM25). Totals are approximate (total_exact: false). Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 25, max 50) |
| page | integer | – | Page number (default 1) |
| q | string | yes | Search query (min 3 chars) |
| tab | string | – | Result type (default all) |
No output schema declared.
No examples provided.
What is the FRTracker — Federal Regulatory Research MCP server?
FRTracker — Federal Regulatory Research is an MCP server listed in the public MCP registry as app.frtracker/regulatory-research. Source-linked US federal regulations: CFR provision history, obligations, rules, comments. This page covers its hosted endpoint (https://frtracker.app/mcp).
Is the FRTracker — Federal Regulatory Research MCP server safe to use?
FRTracker — Federal Regulatory Research scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the FRTracker — Federal Regulatory Research MCP server expose?
FRTracker — Federal Regulatory Research exposes 10 tools: lookup_provision, get_provision_history, rules_amending, recent_cfr_changes, get_stats, and 5 more. Their descriptions and schemas cost roughly 940 tokens of context every time the server is loaded.
Does the FRTracker — Federal Regulatory Research MCP server require authentication?
No. We connected to FRTracker — Federal Regulatory Research without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FRTracker — Federal Regulatory Research MCP server still maintained?
FRTracker — Federal Regulatory Research is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.