# io.github.cyanheads/federal-regulations-mcp-server (remote · federal-regulations.caseyjhand.com)

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

- Trust score: 71/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `federal-regulations.caseyjhand.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/cyanheads-federal-regulations-mcp-server/federal-regulations.md), [page](https://verifymcp.io/servers/cyanheads-federal-regulations-mcp-server/federal-regulations)
- npm · `@cyanheads/federal-regulations-mcp-server`: 35/100, [markdown](https://verifymcp.io/servers/cyanheads-federal-regulations-mcp-server/cyanheads-federal-regulations-mcp-server.md), [page](https://verifymcp.io/servers/cyanheads-federal-regulations-mcp-server/cyanheads-federal-regulations-mcp-server)

## Channel facts

- Endpoint: `https://federal-regulations.caseyjhand.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.2`

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

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2535 tokens (~281/item across 9 items; 7 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http cyanheads-federal-regulations-mcp-server https://federal-regulations.caseyjhand.com/mcp
```

### Codex

```toml
[mcp_servers.cyanheads-federal-regulations-mcp-server]
url = "https://federal-regulations.caseyjhand.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-federal-regulations-mcp-server": {
      "type": "remote",
      "url": "https://federal-regulations.caseyjhand.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cyanheads-federal-regulations-mcp-server --url https://federal-regulations.caseyjhand.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cyanheads-federal-regulations-mcp-server:
    url: "https://federal-regulations.caseyjhand.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "cyanheads-federal-regulations-mcp-server": {
      "type": "http",
      "url": "https://federal-regulations.caseyjhand.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-08-03 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 70, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 66)

First indexed and scored.

## MCP tools (7)

### `regulations_search_rules` (~418 tokens)

Search the Federal Register — the daily journal of US proposed rules, final rules, notices, and presidential documents (1994–present) — filtering by full-text query, document type, agency slug, publication date range, and whether the rule is open for comment. The primary discovery entry point: results carry the document number (open with regulations_get_document), docket IDs, RINs, and affected CFR parts that chain into the comment and codified-text tools. The Federal Register caps navigation at 50 pages and the match count at 10,000; when a result set is larger, narrow with published_after/published_before rather than paging deeper.

Input parameters:

- `agencies` (array): Filter to one or more agencies by Federal Register agency slug (e.g. "environmental-protection-agency", "securities-and-exchange-commission"). Slugs are the kebab-case agency name; if unsure, search…
- `page` (integer): Page number (1–50, default 1). The FR API caps total_pages at 50 — with per_page=100 this allows navigating up to 5,000 results. To reach beyond that window, narrow with published_after/published_bef…
- `per_page` (integer): Results per page (1–100, default 20).
- `published_after`: Earliest publication date, ISO 8601 (YYYY-MM-DD). Combine with published_before to window large result sets — the FR caps navigation at 50 pages.
- `published_before`: Latest publication date, ISO 8601 (YYYY-MM-DD).
- `query` (string): Full-text search across document title and body. Omit to browse by filters alone (e.g. all EPA proposed rules in a date range).
- `type` (array): Document types to include. PRORULE=Proposed Rule, RULE=Final Rule, NOTICE=Notice, PRESDOCU=Presidential Document. Omit for all types.

Output parameters:

- `notice` (string): Guidance when nothing matched or when results were truncated.
- `results` (array): Matching Federal Register documents (this page).
- `shown` (number): Results returned on this page.
- `totalCount` (number): Total matches before pagination (FR count; capped at 10,000 by the API window).
- `truncated` (boolean): True when matches exceed the FR 50-page (5,000-record) navigation ceiling.

### `regulations_get_document` (~196 tokens)

Fetch one Federal Register document by its FR document number — full metadata (title, type, agencies, abstract, action, effective/comment dates, RINs) plus the cross-source handles that make this a workflow server. The output carries the docket ID (chain into regulations_get_docket or regulations_find_comments) and the affected CFR parts (chain into regulations_get_cfr_section). Set include_full_text only when the rule body itself is needed — final rules can run tens of thousands of words.

Input parameters:

- `document_number` (string, required): Federal Register document number (e.g. "2025-14555"). Obtain from regulations_search_rules results (the documentNumber field).
- `include_full_text` (boolean): When true, fetch and inline the document body as plain text (can be large). Default false returns the body URLs only; fetch full text only when you need to read the rule itself, not just its metadata…

Output parameters:

- `abstract`: Abstract summary, or null.
- `action`: Action line (e.g. "Final rule."), or null.
- `agencies` (array): Issuing agency names.
- `bodyHtmlUrl` (string): URL of the rendered HTML body.
- `cfrReferences` (array): Affected CFR parts — chain into regulations_get_cfr_section.
- `commentCount`: FR-reported comment count from Regulations.gov; null when not on Regulations.gov.
- `commentsCloseOn`: Comment-period close date (ISO 8601); when set, still open for comment.
- `dates`: Free-text dates summary from the rule, or null.
- `docketId`: Regulations.gov docket ID — chain into regulations_get_docket / find_comments. Null when not on Regulations.gov.
- `documentNumber` (string): Federal Register document number.
- `effectiveOn`: Effective date (ISO 8601), or null.
- `fullText` (string): Inlined plain-text body — present only when include_full_text=true.
- `htmlUrl` (string): Federal Register web URL for the document.
- `publicationDate` (string): Publication date (ISO 8601).
- `rawTextUrl` (string): URL of the plain-text body.
- `regulationIdNumbers` (array): Regulation Identifier Number(s) (RIN).
- `regulationsGovDocumentId`: Regulations.gov document ID — chain into regulations_find_comments (document-scoped). Null when absent.
- `supportingDocuments` (array): Related Regulations.gov supporting documents.
- `title` (string): Document title.
- `type` (string): Document type.

### `regulations_browse_cfr` (~329 tokens)

Explore the codified Code of Federal Regulations via eCFR in two modes. "structure" walks the CFR hierarchy (all 50 titles, or one title's chapters → parts → sections) to discover a cite when the exact citation is unknown. "search" runs a full-text query across the codified CFR and returns matching sections with their hierarchy path and a snippet. Both modes feed regulations_get_cfr_section. The source (mirror or live) is reported on each search result.

Input parameters:

- `date`: Point-in-time date, ISO 8601 (YYYY-MM-DD). Defaults to current. Structure mode uses this date for historical hierarchy; in search mode, a past date enables point-in-time search.
- `mode` (string, required): "structure": browse the CFR tree (titles, or one title's chapters/parts/sections) to find a cite. "search": full-text search the codified CFR for sections matching a phrase.
- `part` (string): CFR part within the title (structure mode, optional) — narrows the returned tree to one part's sections. Parts can be alphanumeric.
- `per_page` (integer): Results per page in search mode (1–50, default 20). Ignored in structure mode.
- `query`: Full-text search phrase (search mode, required in that mode). Ignored in structure mode.
- `title` (integer): CFR title number (1–50). Structure mode: omit to list all 50 titles, or provide to expand one title. Search mode: optional filter to restrict to one title.

Output parameters:

- `date` (string): Resolved point-in-time date (structure mode).
- `mode` (string): Which mode produced this result.
- `nodes` (array): Hierarchy nodes at the requested level (structure mode).
- `notice` (string): Guidance when nothing matched.
- `results` (array): Matching CFR sections, this page (search mode).
- `shown` (number): Results returned on this page (search mode).
- `source` (string): Provenance: the synced mirror index, or the live eCFR search fallback (search mode).
- `totalCount` (number): Total search matches before pagination (search mode).
- `truncated` (boolean): True when search results were capped at per_page.

### `regulations_get_cfr_section` (~290 tokens)

Read the codified text of a specific CFR section (or a whole part) via eCFR — current or as of a past date. Answers "what does 40 CFR 50.1 say today?" and "...as of 2019-01-01?". Provide title + part + section for one section, or omit section to fetch the whole part (large parts can be very long; prefer a specific section when you know it). eCFR retains historical versions back to roughly 2017; a date before coverage is rejected with guidance. Current single-section reads are served from a synced local mirror when available; the source is reported.

Input parameters:

- `date`: Point-in-time date, ISO 8601 (YYYY-MM-DD). Default current. eCFR retains historical versions back to ~2017; a date before coverage is rejected.
- `part` (string, required): CFR part within the title (e.g. "50"). Parts can be alphanumeric. Obtain from regulations_browse_cfr or a Federal Register document's cfrReferences.
- `section`: Section identifier within the part (e.g. "50.1"). Omit to fetch the entire part — large parts can be very long; prefer a specific section when you know it.
- `title` (integer, required): CFR title number (1–50). E.g. 40 for "Protection of Environment".

Output parameters:

- `bodyText` (string): Section text, XML stripped to plain text (paragraph structure preserved).
- `cfrCite` (string): Assembled cite, e.g. "40 CFR 50.1".
- `date` (string): The issue/point-in-time date the text reflects (ISO 8601).
- `heading` (string): Section/part heading.
- `hierarchyPath` (string): Human-readable hierarchy path.
- `part` (string): CFR part.
- `section`: Section identifier; null when a whole part was fetched.
- `sections` (array): Present only when a whole part was fetched — each section in the part.
- `source` (string): Provenance: the synced mirror, or the live eCFR API.
- `title` (number): CFR title number.

### `regulations_get_docket` (~319 tokens)

Pull a rulemaking docket from Regulations.gov by docket ID (e.g. "EPA-HQ-OAR-2025-0194") — the docket's metadata (title, agency, RIN, abstract) and the documents filed in it (NPRM, final rule, supporting materials). The docket is the folder holding a rule's whole paper trail; each returned document's objectId feeds regulations_find_comments. A docket often contains hundreds of supporting materials — filter document_types to "Proposed Rule"/"Rule" to find the rule documents themselves. Requires REGULATIONS_GOV_API_KEY (free at https://api.data.gov/signup/); the Federal Register and eCFR tools work without it.

Input parameters:

- `docket_id` (string, required): Regulations.gov docket ID (e.g. "EPA-HQ-OAR-2025-0194"). Obtain from a Federal Register document's docketId (regulations_get_document) or an agency rulemaking reference.
- `document_types` (array): Filter the docket's documents to these types. Omit for all. A docket often contains hundreds of "Supporting & Related Material" items — filter to "Proposed Rule"/"Rule" to find the rule documents.
- `page` (integer): Page number (1-based). Regulations.gov caps a query at 20 pages (5,000 records); beyond that, narrow with document_types.
- `per_page` (integer): Documents per page (5–250, default 25). Regulations.gov requires a minimum page size of 5.

Output parameters:

- `abstract`: Docket abstract, or null.
- `agencyId`: Agency ID (e.g. "EPA"), or null.
- `docketId` (string): Regulations.gov docket ID.
- `docketType`: Docket type (e.g. "Rulemaking"), or null.
- `documentCount` (number): Total documents in the docket (before pagination).
- `documents` (array): Documents filed in the docket (this page).
- `modifyDate`: Last-modified date, or null.
- `notice` (string): Guidance when the docket has no documents.
- `objectId`: Docket object ID, or null.
- `rin`: Regulation Identifier Number ("Not Assigned" when none), or null.
- `shown` (number): Documents returned on this page.
- `title` (string): Docket title.
- `truncated` (boolean): True when documentCount exceeds the returned set / 5,000 ceiling.

### `regulations_find_comments` (~453 tokens)

Fetch public comments on a Federal Register document or a Regulations.gov docket — the unique corpus of what citizens and organizations actually submitted. Provide exactly one targeting parameter: docket_id (all comments in a docket, broadest), document_object_id (comments on one document, from regulations_get_docket), fr_document_number (convenience — resolves the FR number to its Regulations.gov document internally), or comment_id (one comment's full detail and attachments). The list endpoint returns no body text or attachment info — call with comment_id to read a comment's body. When a comment's real content is a PDF/DOCX attachment, the body is a stub and attachmentOnly is true; the attachment download URLs are returned. Requires REGULATIONS_GOV_API_KEY (free at https://api.data.gov/signup/).

Input parameters:

- `comment_id` (string): Fetch one comment's full detail and attachments by its Regulations.gov comment ID (e.g. "EPA-HQ-OAR-2025-0194-31102"). Use to read a single comment's body after finding it in a list.
- `docket_id` (string): Fetch all comments in a docket by docket ID (e.g. "EPA-HQ-OAR-2025-0194"). Broadest scope. One of docket_id / document_object_id / fr_document_number / comment_id is required.
- `document_object_id` (string): Fetch comments on one specific document by its Regulations.gov object ID (the objectId from regulations_get_docket's documents). Comments usually attach to the docket's primary (proposed-rule) docume…
- `fr_document_number` (string): Convenience: fetch comments for a Federal Register document by its FR number (e.g. "2025-14555"). Resolves to the Regulations.gov document internally. Saves a get_document → get_docket hop.
- `page` (integer): Page number (1-based). Regulations.gov caps a query at 20 pages (5,000 records); for a high-volume docket this surfaces a sample — narrow by document_object_id.
- `per_page` (integer): Comments per page (5–250, default 25). Regulations.gov requires a minimum page size of 5.

Output parameters:

- `attachmentOnly` (boolean): True when attachments exist and the body is a stub/empty — the substance is in the attachment files (detail mode).
- `attachments` (array): Attachment files — substance lives here when attachmentOnly is true (detail mode).
- `bodyText`: Comment body, HTML-stripped. A stub ("See Attached") when content is in attachments; null when empty (detail mode).
- `commentId` (string): Comment ID (detail mode).
- `commentOnDocumentId`: Document the comment was filed on, or null (detail mode).
- `comments` (array): Comments matching the target, this page (list mode). Bodies/attachments require comment_id detail mode.
- `docketId`: Docket ID, or null (detail mode).
- `mode` (string): Which mode produced this result.
- `notice` (string): Guidance — empty results, or that bodies need comment_id detail mode.
- `organization`: Submitter organization, or null (detail mode).
- `postedDate` (string): Posted date (detail mode).
- `receivedDate`: Received date, or null (detail mode).
- `restrictReason`: Reason the comment is restricted, or null (detail mode).
- `shown` (number): Comments returned on this page (list mode).
- `submitterName`: Submitter name when public, or null (detail mode).
- `target` (string): What was queried — docket / document / FR doc (list mode).
- `title` (string): Comment title (detail mode).
- `totalCount` (number): Total comments matching the target (list mode).
- `truncated` (boolean): True when comments exceed the 5,000-record ceiling (list mode).
- `withdrawn` (boolean): True when the comment was withdrawn (detail mode).

### `regulations_list_open_comments` (~266 tokens)

List rules currently open for public comment, filterable by agency slug and topic, sorted by closing date (soonest first). "What can I still weigh in on?" Runs on the Federal Register's open-comment window and is fully functional without a key. When REGULATIONS_GOV_API_KEY is configured, each row is enriched with the comment count from the Federal Register document's embedded Regulations.gov info (no extra rate-limited call). Open one row with regulations_get_document for the full proposal, or pull the comments with regulations_find_comments.

Input parameters:

- `agencies` (array): Filter to one or more agencies by Federal Register agency slug (e.g. "environmental-protection-agency").
- `closing_before`: Only rules whose comment period closes on or before this date, ISO 8601 (YYYY-MM-DD). Use to find deadlines you need to act on soon.
- `page` (integer): Page number (1–50). The FR caps total_pages at 50; with per_page=100 this covers up to 5,000 open rules.
- `per_page` (integer): Results per page (1–100, default 20).
- `query` (string): Full-text filter across open rules. Omit to list all rules currently open for comment.

Output parameters:

- `asOf` (string): The "today" the open-window filter used (ISO 8601).
- `keyed` (boolean): Whether comment counts were enriched (REGULATIONS_GOV_API_KEY present).
- `notice` (string): Guidance when nothing matched, or that comment counts are unavailable without a key.
- `results` (array): Rules open for comment (this page), closing soonest first.
- `shown` (number): Results returned on this page.
- `totalCount` (number): Total rules open for comment matching the filters.
- `truncated` (boolean): True when matches exceed the FR 5,000-record navigation ceiling.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cyanheads-federal-regulations-mcp-server/federal-regulations#diagnostics

## Score history

- 2026-08-03: 71
- 2026-08-02: 70
- 2026-08-01: 70
- 2026-07-31: 70
- 2026-07-30: 69
- 2026-07-29: 68
- 2026-07-28: 67
- 2026-07-27: 67
- 2026-07-26: 66

## Links

- Remote endpoint: https://federal-regulations.caseyjhand.com/mcp
- Repository: https://github.com/cyanheads/federal-regulations-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/cyanheads-federal-regulations-mcp-server/federal-regulations/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/cyanheads-federal-regulations-mcp-server/federal-regulations/changelog.json
- HTML version of this page: https://verifymcp.io/servers/cyanheads-federal-regulations-mcp-server/federal-regulations