Skip to content

US federal rules taking effect MCP server

io.github.joelp22-maker/referencesource-rulesjoelp22-makerstreamable-httpv1.0.0Scanned

Which published US federal rules take effect between two dates, and which CFR parts they amend?

5 tools: 1 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 1 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the US federal rules taking effect MCP server can do

The US federal rules taking effect MCP server is published by the GitHub account joelp22-maker. It has 5 tools. It can create or change data (1 tool: verify_quote), but cannot delete data. 4 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (tool-shadowing). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 1Claude Code: ask
  • verify_quoteIs this right?No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check a claimed fact about a rule against the register
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • get_ruleEverything 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 …1 finding

    Why it is in this group

    • The name "get_rule" says "get": a word for reading.

    Findings

    • Warn

      The description contains "every other tool", wording about other tools or servers.

      Matched text

      description: "...rs look like "2026-13685" and appear in every other tool's results."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get one rule by Federal Register document number
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_agenciesWhich agencies have rules coming?No findings

    Why it is in this group

    • The name "list_agencies" says "list": a word for reading.
    Description, as the server wrote it
    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".

    Annotations the server declares

    • title: List the agencies with rules taking effect
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_rules_amending_cfr_partIs anything changing in the part of the CFR I am subject to?No findings

    Why it is in this group

    • The name "list_rules_amending_cfr_part" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List rules amending a CFR part
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_rules_taking_effectWhat lands on me, and when?No findings

    Why it is in this group

    • The name "list_rules_taking_effect" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List federal rules taking effect between two dates
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:23 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://referencesource.org/mcp/rules: tools/list returned 5 tools to an anonymous client, including verify_quote (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The description contains "every other tool", wording about other tools or servers.

    Matched text

    description: "...rs look like "2026-13685" and appear in every other tool's results."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http referencesource-rules https://referencesource.org/mcp/rules
claude mcp add --transport http referencesource-rules https://referencesource.org/mcp/rules

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__referencesource-rules__list_rules_taking_effect",
      "mcp__referencesource-rules__get_rule",
      "mcp__referencesource-rules__list_agencies",
      "mcp__referencesource-rules__list_rules_amending_cfr_part"
    ],
    "ask": [
      "mcp__referencesource-rules__verify_quote"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as referencesource-rules. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.joelp22-maker/referencesource-rules/verify?hash=5a4ffbe081252268329b368c097e66456c74b5686ff643100cea85b12385d682" | jq -e '.changed == false'

Pinned hash 5a4ffbe08125, from Nov 21, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.joelp22-maker/referencesource-rules/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.joelp22-maker/referencesource-rules
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.joelp22-maker/referencesource-rules.svg)](https://radar.anlyon.com/servers/io.github.joelp22-maker/referencesource-rules)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:37 UTC.

US federal rules taking effect MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the US federal rules taking effect MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the US federal rules taking effect MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the US federal rules taking effect MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the US federal rules taking effect MCP server have?

5 tools: 1 write, 4 read. verify_quote, list_rules_taking_effect, get_rule, list_agencies and list_rules_amending_cfr_part.

Does the US federal rules taking effect MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the US federal rules taking effect MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the US federal rules taking effect MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.