# FedReg Tracker (remote · fedregtracker.com)

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

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `fedregtracker.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/agentstructure-fedreg/fedregtracker.md), [page](https://verifymcp.io/servers/agentstructure-fedreg/fedregtracker)

## Channel facts

- Endpoint: `https://fedregtracker.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (manage_regulatory_watchlist).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 81/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 42% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http agentstructure-fedreg 'https://fedregtracker.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "agentstructure-fedreg": {
      "url": "https://fedregtracker.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "agentstructure-fedreg": {
      "type": "http",
      "url": "https://fedregtracker.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.agentstructure-fedreg]
url = "https://fedregtracker.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "agentstructure-fedreg": {
      "type": "remote",
      "url": "https://fedregtracker.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add agentstructure-fedreg --url 'https://fedregtracker.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  agentstructure-fedreg:
    url: "https://fedregtracker.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "agentstructure-fedreg": {
      "Transport": "http",
      "Url": "https://fedregtracker.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add agentstructure-fedreg -t streamable-http -u 'https://fedregtracker.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "agentstructure-fedreg": {
      "type": "http",
      "url": "https://fedregtracker.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 64, +1)

- [security] 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
- [functional regression] Schema quality: 132 → 152
- [functional improvement] Tool coverage: 37% → 42%
- [cosmetic] “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”

### 2026-10-16 (score 63, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-15 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-14 (score 63)

First indexed and scored.

## MCP tools (12)

### `search_federal_regulations` (~260 tokens)

Search federal regulations

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.

Input parameters:

- `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)

### `get_regulatory_document` (~104 tokens)

Get a Federal Register document

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.

Input parameters:

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

### `track_federal_regulations` (~138 tokens)

Create a regulatory watchlist

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.

Input parameters:

- `alert_preferences` (object)
- `filters` (object, required): 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)

### `manage_regulatory_watchlist` (~115 tokens)

List, update, pause, resume or delete watchlists

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.

Input parameters:

- `action` (required)
- `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.

### `list_regulatory_alerts` (~97 tokens)

List new 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.

Input parameters:

- `limit` (integer)
- `peek` (boolean)
- `status`
- `watchlist` (string): Watchlist name or id.

### `get_regulatory_timeline` (~119 tokens)

Get a rulemaking timeline

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.

Input parameters:

- `document_number` (string): Federal Register document number, e.g. 2026-12345.
- `rin` (string)
- `rulemaking_id` (string)

### `get_regulatory_deadlines` (~123 tokens)

Get comment and effective-date deadlines

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.

Input parameters:

- `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.

### `compare_regulatory_documents` (~114 tokens)

Compare proposed and final rules

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.

Input parameters:

- `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)

### `get_cfr_changes` (~232 tokens)

Get codified CFR text changes

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.

Input parameters:

- `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.

### `get_regulatory_intelligence_brief` (~105 tokens)

Get a regulatory intelligence brief

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.

Input parameters:

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

### `manage_business_profile` (~110 tokens)

Set or read the 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.

Input parameters:

- `action`
- `business_size`
- `federal_contractor` (boolean)
- `industries` (array)
- `naics_codes` (array)
- `operating_regions` (array)
- `regulated_activities` (array)
- `regulatory_interests` (array)

### `rate_regulatory_alert` (~74 tokens)

Give feedback on an 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).

Input parameters:

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/agentstructure-fedreg/fedregtracker#diagnostics

## Score history

- 2026-10-18: 64
- 2026-10-17: 64
- 2026-10-16: 63
- 2026-10-15: 63
- 2026-10-14: 63

## Common questions

### 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.

## Links

- Remote endpoint: https://fedregtracker.com/mcp
- Website: https://fedregtracker.com/
- Changelog RSS feed: https://verifymcp.io/servers/agentstructure-fedreg/fedregtracker.xml
- Changelog JSON feed: https://verifymcp.io/servers/agentstructure-fedreg/fedregtracker.json
- HTML version of this page: https://verifymcp.io/servers/agentstructure-fedreg/fedregtracker