# US Federal Rules Taking Effect Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## US Federal Rules Taking Effect

Track which US federal rules take effect between two dates and what CFR parts they change.

- Record: https://musedirectory.ai/connector/us-federal-rules-taking-effect
- Category: Legal
- Developer: joelp22-maker (https://referencesource.org/federal-rules-taking-effect)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 377ms, checked 2026-09-28T07:15:53Z
- Endpoint: https://referencesource.org/mcp/rules
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-09-25T08:41:29Z)
- Source: Found in the official MCP Registry (io.github.joelp22-maker/referencesource-rules) https://registry.modelcontextprotocol.io/v0/servers?search=io.github.joelp22-maker%2Freferencesource-rules

Queries published US federal final rules by effective date range or CFR part. Returns rule titles, agencies, affected CFR sections, document numbers, and Federal Register records. Helps businesses and compliance teams monitor regulatory changes.

Example request: "Show me all EPA rules taking effect in the next quarter that affect air quality standards."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use US Federal Rules Taking Effect to help me. It is a free service with an MCP server at https://referencesource.org/mcp/rules. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- list_rules_taking_effect: 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
- get_rule: 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. Do
- list_agencies: 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 — "Federa
- list_rules_amending_cfr_part: 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 pa
- verify_quote: 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

Screening checks:
- MCP handshake: pass (Answered in 8ms)
- Domain against threat feeds (Cloudflare security DNS): pass (referencesource.org not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (5 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 51 days ago)
- AI review of purpose and tool behavior: pass (No concerns)