FedReg Tracker
REMOTE · FEDREGTRACKER.COM
Federal regulatory intelligence from the Federal Register: search rules and notices, track deadlines
Available components
Last scanned (2 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Education and Research
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
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (manage_regulatory_watchlist). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1824 tokens (~152/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 42% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 17 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_cfr_changes” rewrote its description, which is the text the model reads security
- Tool “get_regulatory_document” rewrote its description, which is the text the model reads security
- Schema quality: 132 → 152 ▼ functional
- Tool coverage: 37% → 42% ▲ functional
- “get_cfr_changes” added an optional parameter “limit” cosmetic
- “get_cfr_changes” added an optional parameter “section” cosmetic
- “get_cfr_changes” added an optional parameter “since” cosmetic
- “get_cfr_changes” added an optional parameter “until” cosmetic
- “get_cfr_changes” added an optional parameter “watchlist” cosmetic
- “get_cfr_changes” reworded the description of “cfr_part” cosmetic
- 16 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 15 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 14 Oct 26 63
First indexed and scored.
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 18 Oct 2026 · Probed https://fedregtracker.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fedregtracker.com | CN=YR1,O=Let's Encrypt,C=US | 8 Oct 2026 | 6 Jan 2027 | RSA 2048 | SHA256-RSA | 598a66160649a0a732ba65acc246ef807d9 |
| SANs: fedregtracker.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fedregtracker.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| fedregtracker.com. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fedregtracker.com/mcp | Verified | 200 | |
| http (plaintext) | http://fedregtracker.com/mcp | HTTPS enforced | 308 | https://fedregtracker.com/mcp |
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 →
compare_regulatory_documents Compare proposed and final rules ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
| rin | string | – | – |
No output schema declared.
No examples provided.
get_cfr_changes Get codified CFR text changes ~232
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cfr_part | string | – | Part, e.g. 63 or 1910. |
| cfr_title | integer | – | – |
| limit | integer | – | – |
| section | string | – | Section, e.g. 63.2. |
| since | string | – | Earliest version date (default 90 days ago). |
| until | string | – | Latest version date. |
| watchlist | string | – | Watchlist name or id. |
No output schema declared.
No examples provided.
get_regulatory_deadlines Get comment and effective-date deadlines ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | array | – | – |
| deadline_type | – | – | – |
| document_type | array | – | – |
| from | string | – | Start date (default today). |
| limit | integer | – | – |
| query | string | – | – |
| to | string | – | End date (default 30 days after start). |
| watchlist | string | – | Watchlist name or id. |
No output schema declared.
No examples provided.
get_regulatory_document Get a Federal Register document ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| document_number | string | yes | Federal Register document number, e.g. 2026-12345. |
No output schema declared.
No examples provided.
get_regulatory_intelligence_brief Get a regulatory intelligence brief ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| document_number | string | yes | Federal Register document number, e.g. 2026-12345. |
| watchlist | string | – | Watchlist name or id. |
No output schema declared.
No examples provided.
get_regulatory_timeline Get a rulemaking timeline ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| document_number | string | – | Federal Register document number, e.g. 2026-12345. |
| rin | string | – | – |
| rulemaking_id | string | – | – |
No output schema declared.
No examples provided.
list_regulatory_alerts List new regulatory alerts ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| peek | boolean | – | – |
| status | – | – | – |
| watchlist | string | – | Watchlist name or id. |
No output schema declared.
No examples provided.
manage_business_profile Set or read the business profile ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | – | – | – |
| business_size | – | – | – |
| federal_contractor | boolean | – | – |
| industries | array | – | – |
| naics_codes | array | – | – |
| operating_regions | array | – | – |
| regulated_activities | array | – | – |
| regulatory_interests | array | – | – |
No output schema declared.
No examples provided.
manage_regulatory_watchlist List, update, pause, resume or delete watchlists ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | – | yes | – |
| alert_preferences | object | – | – |
| 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. |
No output schema declared.
No examples provided.
rate_regulatory_alert Give feedback on an alert ~74
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).
| Name | Type | Req | Description |
|---|---|---|---|
| document_number | string | yes | Federal Register document number, e.g. 2026-12345. |
| rating | – | yes | – |
No output schema declared.
No examples provided.
search_federal_regulations Search federal regulations ~260
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | array | – | Agency abbreviations or slugs. |
| cfr_part | string | – | – |
| cfr_title | integer | – | – |
| comments_close_from | string | – | Comment period closes on or after. |
| comments_close_to | string | – | Comment period closes on or before. |
| docket_id | string | – | – |
| document_type | array | – | – |
| effective_from | string | – | Effective on or after. |
| effective_to | string | – | Effective on or before. |
| industry | – | – | – |
| limit | integer | – | – |
| order | – | – | – |
| page | integer | – | – |
| published_from | string | – | Earliest publication date. |
| published_to | string | – | Latest publication date. |
| query | string | – | Keywords. Supports quotes for phrases. |
| rin | string | – | – |
| significant | boolean | – | – |
No output schema declared.
No examples provided.
track_federal_regulations Create a regulatory watchlist ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_preferences | object | – | – |
| filters | object | yes | 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 | – | – |
No output schema declared.
No examples provided.
How do I install the FedReg Tracker MCP server?
FedReg Tracker is a hosted endpoint at https://fedregtracker.com/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 · fedregtracker.com
claude mcp add --transport http agentstructure-fedreg 'https://fedregtracker.com/mcp'
What is the FedReg Tracker MCP server?
FedReg Tracker is an MCP server listed in the public MCP registry as io.github.agentstructure/fedreg. Federal regulatory intelligence from the Federal Register: search rules and notices, track deadlines. This page covers its hosted endpoint (https://fedregtracker.com/mcp).
Is the FedReg Tracker MCP server safe to use?
FedReg Tracker scores 64 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 FedReg Tracker MCP server expose?
FedReg Tracker exposes 12 tools: search_federal_regulations, get_regulatory_document, track_federal_regulations, manage_regulatory_watchlist, list_regulatory_alerts, and 7 more. Their descriptions and schemas cost roughly 1,591 tokens of context every time the server is loaded.
Does the FedReg Tracker MCP server require authentication?
No. We connected to FedReg Tracker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FedReg Tracker MCP server still maintained?
FedReg Tracker is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.