reapx Federal Register - rules, notices and orders

dev.reapxPublished by reapx.devv1.0.0Updated Oct 24, 2026

Scrape Federal Register rules, proposed rules, notices and orders by agency or date. Pay per row.

The publisher's own server: Register.gy

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Lets an assistant scrape Federal Register rules, proposed rules, notices and orders by agency or date, billed per row.

What you can do
This remote server exposes a scraping tool for the Federal Register, the U.S. government's daily journal of rules, proposed rules, notices and orders. An assistant can request records filtered by agency or by date. Results are billed per row returned.
When to use it
Useful when you need to pull Federal Register entries for a specific agency or time range into a research or compliance workflow, rather than browsing the site by hand.
Requirements
A remote streamable HTTP endpoint at mcp.apify.com. Authentication is required via OAuth, and requests carry an Authorization header holding your own Apify API token as a Bearer token. A free token can be obtained from an Apify console account, or a prepaid, spend-capped token can be bought without signup.
Before you install
Runs are billed per row, so costs grow with the amount of data returned; a spend-capped prepaid token limits exposure. The Authorization header carries a secret API token that should not be shared or logged. Data is fetched through Apify, a third-party platform.

Installation

In SourceWeft

  1. Open reapx Federal Register - rules, notices and orders in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/dev.reapx%2Ffederal-register/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "reapx-federal-register-rules-notices-and": {
      "type": "http",
      "url": "https://mcp.apify.com/?actors=reapx/federal-register-scraper"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Register integrations