MCP.Market

US federal rules taking effect MCP server

online · 100% uptime
by joelp22-maker·io.github.joelp22-maker/referencesource-rules·v1.0.0
No reviews yet

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

B84/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B84/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed US federal rules taking effect yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

US federal rules taking effect tools (5)

write = sends, deletes, buys or posts
  • get_ruleFree

    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.

  • list_agenciesFree

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

  • list_rules_amending_cfr_partFree

    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.

  • list_rules_taking_effectFree

    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.

  • verify_quoteFree

    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.

Public scan report

scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 693ms20/20
  • Tool poisoning5 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 40 days ago12/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 84/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How US federal rules taking effect compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
84/100
higher than 68% of 48,255 servers
Tools
5
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
12 ms
faster than 98% of 30,031 servers

What its tools let an agent do: 5 read

Install US federal rules taking effect in Claude Code, Cursor or VS Code

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

What the publisher says

From the US federal rules taking effect repository's README, as published. We do not edit it. Read it on GitHub

referencesource-mcp

MCP server for referencesource.org — small, verified reference datasets where every record carries its source URL and a verbatim quote from that page, so any value an assistant gives you can be checked, not just believed.

285 datasets, 110,000+ records: regulatory thresholds and deadlines, version compatibility, standards supersessions, certification registers, inspection requirements, and more. Each dataset states its coverage and its last-verified date.

Tools

verify_quote is the unusual one: assistants invent plausible-but-wrong values roughly 19% of the time in our own measurements, and this is the check. Four verdicts come back:

Where a record is found, the answer carries the stored value, the record URL, the source URL and the verbatim quote, so the claim can be traced upstream — plus an attestation saying plainly that the verdict is about what our source states, not about what is true in the world. Asking whether the 2026 conforming loan limit for Autauga County, Alabama is $806,500 returns differs, stored value $832,750, quoting the FHFA row it came from.

Scope, stated so nobody overclaims: these tools search referencesource.org's own published records. They do not fetch arbitrary URLs and cannot check a claim against a page we have not harvested. not_found means "not in this dataset", never "false".

Setup

Claude Desktop — add to claudedesktopconfig.json:

{
  "mcpServers": {
    "referencesource": {
      "command": "npx",
      "args": ["-y", "referencesource-mcp"]
    }
  }
}

Cursor / other stdio MCP clients — same idea: command npx, args ["-y", "referencesource-mcp"].

Clients that support remote servers directly don't need this package at all — point them at the streamable-HTTP endpoint: https://referencesource.org/mcp.

Notes

the stateless server at referencesource.org/mcp.

  • Zero dependencies; Node 18+. The package is a thin stdio→HTTPS bridge to

(see referencesource.org/privacy).

  • No accounts, no keys, no tracking beyond standard server request logs

package just makes it callable mid-conversation.

  • Data is free to read on the site in HTML, Markdown, and JSON; this

MIT licensed.

The data behind it

  • Site: https://referencesource.org — canonical, re-verified on a schedule
  • Bulk data: https://github.com/joelp22-maker/referencesource-data
  • Archived snapshot with a DOI: 10.5281/zenodo.22115966
  • Hugging Face: https://huggingface.co/datasets/referencesource

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-10-30downgradeA → Bscore 84

US federal rules taking effect: common questions

Is US federal rules taking effect MCP server safe?
Mostly: it is graded B (84/100). Read the US federal rules taking effect safety report
How do I install US federal rules taking effect?
It runs remotely at referencesource.org. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does US federal rules taking effect need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is US federal rules taking effect maintained?
The last commit was 44 days ago (2026-09-21). The latest release is v1.0.0.
Is US federal rules taking effect up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does US federal rules taking effect compare with other MCP servers?
safety score 84/100 (higher than 68% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from joelp22-maker →