Federal Regulations

io.github.stark256-specPublished by GitHub account stark256-specv0.1.0Updated Oct 24, 2026

Search the Federal Register, read & diff CFR sections, query Regulations.gov. Any LLM supported.

The publisher's own server: Regulations.ai — Global AI Law Tracker

Overview

AI-generated overview

A local MCP server that lets an assistant search the Federal Register, read and diff CFR sections, and query Regulations.gov for US federal regulatory research.

What you can do
Search the Federal Register for federal rules and notices, and query Regulations.gov for regulatory dockets and documents (the latter needs an API key). Read sections of the Code of Federal Regulations (CFR) and compare versions with diffs. Works with any LLM supported by the client.
When to use it
Useful when you need to look up US federal rules, track changes to CFR sections, or research regulatory dockets and public comments without leaving the assistant.
Requirements
Runs as a local process installed from the PyPI package regulations-mcp over stdio, so a Python environment is needed. The Federal Register and eCFR tools need no key; the Regulations.gov search tools need a free API key supplied through the REGULATIONS_GOV_API_KEY environment variable. Network access is required.
Before you install
The server asks for an API key in REGULATIONS_GOV_API_KEY; keep it private and note that queries to Regulations.gov are sent to that third-party service. The tools are read-only lookups, but verify regulatory text against official sources before relying on it.

Installation

In SourceWeft

  1. Open Federal Regulations in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Regulations integrations