FRTracker — Federal Regulatory Research

app.frtrackerPublished by frtracker.appOfficial publisherv1.0.0Updated Oct 24, 2026

Source-linked US federal regulations: CFR provision history, obligations, rules, comments.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

A remote MCP endpoint that gives an assistant source-linked access to US federal regulations, including CFR provision history, obligations, rules and comments.

What you can do
Look up US federal regulatory material with links back to the source, covering CFR provisions and their history, obligations, rules and comments. The manifest lists no individual tools, so the exact operations are not documented here. It is a hosted endpoint rather than a local package, so the assistant connects to it directly.
When to use it
Useful when an assistant needs to research or cite US federal regulations, trace how a CFR provision changed, or find obligations, rules and public comments tied to a source.
Requirements
A remote streamable HTTP endpoint at frtracker.app; no local runtime, packages, environment variables or headers are declared. The manifest declares no authentication, so no account or API key setup is described.
Before you install
The manifest declares no authentication and no credentials, so nothing sensitive is requested. Regulatory content is third-party and should be checked against the linked primary sources before being relied on; the manifest does not describe any write or delete actions.

Installation

In SourceWeft

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

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.frtracker%2Fregulatory-research/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "frtracker-federal-regulatory-research": {
      "type": "http",
      "url": "https://frtracker.app/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 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.