US federal rules taking effect
REMOTE · REFERENCESOURCE.ORG
Which published US federal rules take effect between two dates, and which CFR parts they amend?
Available components
Last scanned (15 hours ago)
Scores higher than 86% of remote servers
Reachable. Last reached 21 Nov 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 Security74
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 953 tokens (~190/item across 5 items; 5 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 10 Oct 26 0
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 2026 · Probed https://referencesource.org/mcp/rules
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=referencesource.org | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 284c538e5c38c80d0eb8e23b1bba01ab |
| SANs: referencesource.org | ||||||
| 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 referencesource.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| org. | DS published | 725 | 8 | Verified |
| referencesource.org. | No DS | 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://referencesource.org/mcp/rules | Verified | 200 | |
| http (plaintext) | http://referencesource.org/mcp/rules | HTTPS enforced | 301 | https://referencesource.org/mcp/rules |
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_rule Get one rule by Federal Register document number ~111
Everything this register holds for one final rule: title, agency, effective date, the rule's own DATES paragraph, the CFR parts it amends, its publication date, a link to the rule on federalregister.gov, and a verbatim quote of the Federal Register API record it was read from. Document numbers look like "2026-13685" and appear in every other tool's results.
| Name | Type | Req | Description |
|---|---|---|---|
| document_number | string | yes | Federal Register document number, e.g. "2026-13685". |
| Name | Type | Req | Description |
|---|---|---|---|
| register | object | – | – |
| rule | object | yes | – |
No examples provided.
list_agencies List the agencies with rules taking effect ~88
Which agencies have rules coming? Returns each agency in this register with how many rules it has taking effect, the soonest and latest of those dates. Call it to get an agency name exactly as the Federal Register writes it before filtering with list_rules_taking_effect — "Federal Aviation Administration", not "FAA".
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional case-insensitive substring filter on the agency name. |
| Name | Type | Req | Description |
|---|---|---|---|
| agencies | array | yes | – |
| agencies_total | integer | yes | – |
| coverage | string | yes | – |
| register | object | – | – |
No examples provided.
list_rules_amending_cfr_part List rules amending a CFR part ~187
Is anything changing in the part of the CFR I am subject to? Give a CFR title and part — "49 CFR 192", "40 CFR 52", "21 CFR 1308" — and get the already-published final rules that amend it, soonest effective date first, with each rule's DATES paragraph and a verbatim quote. The part is matched whole, so "40 CFR 5" never returns rules about 40 CFR 52.
| Name | Type | Req | Description |
|---|---|---|---|
| cfr_part | string | yes | The CFR title and part together, e.g. "49 CFR 192". A bare part number is refused: it is ambiguous across the fifty CFR titles. |
| from | string | – | Optional ISO date; only rules taking effect on or after it. |
| limit | integer | – | How many to return, 1–20. Default 20. |
| Name | Type | Req | Description |
|---|---|---|---|
| cfr_part | string | yes | – |
| coverage | string | yes | – |
| register | object | – | – |
| rules | array | yes | – |
| rules_matched | integer | yes | – |
| rules_returned | integer | – | – |
No examples provided.
list_rules_taking_effect List federal rules taking effect between two dates ~219
What lands on me, and when? Lists already-published US federal final rules whose effective date falls between two dates, soonest first, optionally from one agency. Each with the rule title, the agency, the CFR parts amended, the document number, the rule's own DATES paragraph and a verbatim quote of the Federal Register record. This is the compliance-calendar question — use it for "what takes effect in Q4", not for searching the Federal Register by topic.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Optional agency filter, matched case-insensitively as a substring of the agency name ("Coast Guard", "aviation"). Call list_agencies for the names as the Federal Register writes them. |
| from | string | yes | ISO start date, inclusive, e.g. "2026-10-01". |
| limit | integer | – | How many to return, 1–20. Default 20. |
| to | string | yes | ISO end date, inclusive, e.g. "2026-12-31". |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | string | yes | – |
| from | string | yes | – |
| register | object | – | – |
| rules | array | yes | – |
| rules_matched | integer | yes | – |
| rules_returned | integer | – | – |
| to | string | yes | – |
No examples provided.
verify_quote Check a claimed fact about a rule against the register ~175
Is this right? Check a claim about a final rule — its effective date, its agency, the CFR parts it amends — against the Federal Register record instead of trusting it. Says whether the claim matches a stored value, appears only in the verbatim quote, or differs (and then what the record says instead). Effective dates are exactly where a confident wrong answer costs money.
| Name | Type | Req | Description |
|---|---|---|---|
| claimed_value | string | yes | The value to check, exactly as claimed, e.g. "Terminated" or "2026-10-29". |
| document_number | string | yes | Federal Register document number of the rule the claim is about, e.g. "2026-13685". |
| field | string | – | Which field the claim is about, if you know it. Without it, every stored field of the record is checked. |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | string | yes | – |
| claimed_value | string | yes | – |
| in_source_quote | boolean | – | – |
| match | object | – | – |
| quote_source | string | – | – |
| record | object | – | – |
| stored_values | object | – | – |
| verdict | string | yes | matches_record: the claim equals a stored value (match.match_type says how exactly). matches_quote: it appears in the verbatim source quote but is not a stored value. differs: the record was found an… |
No examples provided.
How do I install the US federal rules taking effect MCP server?
US federal rules taking effect is a hosted endpoint at https://referencesource.org/mcp/rules, 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 · referencesource.org
claude mcp add --transport http joelp22-maker-referencesource-rules 'https://referencesource.org/mcp/rules'
What is the US federal rules taking effect MCP server?
US federal rules taking effect is an MCP server listed in the public MCP registry as io.github.joelp22-maker/referencesource-rules. Which published US federal rules take effect between two dates, and which CFR parts they amend? This page covers its hosted endpoint (https://referencesource.org/mcp/rules).
Is the US federal rules taking effect MCP server safe to use?
US federal rules taking effect scores 85 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 US federal rules taking effect MCP server expose?
US federal rules taking effect exposes 5 tools: list_rules_taking_effect, get_rule, list_agencies, list_rules_amending_cfr_part, verify_quote. Their descriptions and schemas cost roughly 780 tokens of context every time the server is loaded.
Does the US federal rules taking effect MCP server require authentication?
No. We connected to US federal rules taking effect without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the US federal rules taking effect MCP server still maintained?
US federal rules taking effect is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the US federal rules taking effect MCP server?
VerifyMCP ran 13 checks on US federal rules taking effect, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.