MCP.Market

Reginfo MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/reginfo·v0.2.0

reginfo MCP — the Unified Agenda of Federal Regulatory and Deregulatory Actions, from reginfo.gov…

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Reginfo yet.

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

Reginfo tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Reginfo compares

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

Safety score
77/100
higher than 50% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
70 ms
faster than 89% of 30,031 servers

Release history: 4 versions in the registry since 2026-09-16, latest 2026-10-29, typically one every 8 days.

Install Reginfo in Claude Code, Cursor or VS Code

claude mcp add --transport http reginfo https://gateway.pipeworx.io/reginfo/mcp
Add to Cursor

What the publisher says

From the Reginfo repository's README, as published. We do not edit it. Read it on GitHub

@pipeworx/reginfo

The Unified Agenda of Federal Regulatory and Deregulatory Actions — every RIN (Regulation Identifier Number) a federal agency has told OIRA it intends to propose, finalize, or has completed, published biannually since Fall 1995. This is the LEADING record ahead of ecfr/federal-register's trailing one: an agency's "planning to propose X" shows up here, edition by edition, often years before the same rule actually publishes or takes effect.

Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.

Tools

  • regagendasearch(agency?, keyword?, stage?, edition?, limit?) — search RINs by agency, free-text keyword, and/or rulemaking stage. Defaults to the newest edition on file.
  • reg_rin(rin) — full detail for one RIN across EVERY edition it has appeared in, showing how its stage/status changed over time.
  • regagencyagenda(agency, edition?, limit?) — one agency's full regulatory agenda for an edition, grouped by rule_stage.
  • regagendacoverage() — which editions are currently loaded (oldest/newest, total rows).

Auth

Keyless — no operator key needed. Backed by reginfo_rins, refreshed monthly by workers/data-pipeline (dataset reginfo).

Data sources

report index. — one biannual edition's full XML (~16.5MB, ~3,800 RININFO records). Editions run REGINFORINDATA199510.xml .. present, April(04)/October(10) each year.

  • — the Unified Agenda

A missing edition answers HTTP 200, not 404. reginfo.gov serves a ~50KB HTML "no such report" page (Content-Type: text/html) for an edition that was never published — a real edition answers Content-Type: application/xml. The ingest HEAD-probes content-type before ever GETting a file, so a not-yet- published edition (or a genuine off-cycle gap in the pre-2000 grid) costs a cheap HEAD request rather than leaking an HTML page into the data.

One row PER (rin, publicationid), not per RIN. A RIN's rulestage changes edition to edition ("Proposed Rule Stage" → "Final Rule Stage" → "Completed Actions") — that history is the whole point of this dataset, so a newer edition never overwrites an older one. reg_rin returns every edition a RIN has appeared in, newest first.

Coverage grows in gradually, not all at once. The backfill drains in edition by edition rather than loading all ~60 editions back to 1995 in one pass; regagendacoverage reports exactly which editions are loaded right now, so a caller can tell "not backfilled yet" apart from "genuinely never published".

Agency matching covers name, acronym, AND code, and matches on either the direct agency or its PARENT — asking for "Interior" also surfaces its sub-agencies' (e.g. Fish & Wildlife) rules, since the source records both levels per RIN.

The abstract is HTML wrapped in CDATA in the source XML. The ingest strips tags and decodes entities before writing the abstract column, so callers only ever see plain text.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "reginfo": {
      "url": "https://gateway.pipeworx.io/reginfo/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/reginfo/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

Shortened. The full README is on GitHub.

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

Reginfo: common questions

Is Reginfo MCP server safe?
Mostly: it is graded B (77/100). Read the Reginfo safety report
How do I install Reginfo?
It runs remotely at gateway.pipeworx.io. 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 Reginfo need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Reginfo maintained?
The last commit was 39 days ago (2026-09-26). The latest release is v0.2.0.
Is Reginfo up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Reginfo compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 70 ms (faster than 89% of 30,031 servers). Full comparison.

More from pipeworx-io →