# Reginfo (npm · @pipeworx/mcp-reginfo)

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

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-reginfo/reginfo-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-reginfo/reginfo-mcp)
- npm · `@pipeworx/mcp-reginfo`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-reginfo/pipeworx-mcp-reginfo.md), [page](https://verifymcp.io/servers/pipeworx-io-reginfo/pipeworx-mcp-reginfo)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-reginfo`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-reginfo).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 823 tokens (~205/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Reginfo MCP server?

Reginfo runs locally as an npm package, launched with npx -y @pipeworx/mcp-reginfo. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-reginfo -- npx -y @pipeworx/mcp-reginfo
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-reginfo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-reginfo"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-reginfo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-reginfo"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-reginfo -- npx -y @pipeworx/mcp-reginfo
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-reginfo": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-reginfo"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-reginfo --command npx --arg -y --arg @pipeworx/mcp-reginfo
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-reginfo:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-reginfo"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-reginfo": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-reginfo"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-reginfo -t stdio -c npx -a -y @pipeworx/mcp-reginfo
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-reginfo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-reginfo"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-04 (score 82, +3)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.20
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (4)

### `reg_agenda_search` (~372 tokens)

Search the Unified Agenda of federal regulatory actions — every rule an agency has told OIRA it plans to propose, finalize, or has completed, since Fall 1995. Answers "what rules is EPA planning", "regulatory agenda for immigration", "upcoming FDA rulemaking on menthol cigarettes". Filter by agency (name, acronym, or code — e.g. "EPA", "Environmental Protection Agency"), a keyword against the rule title/abstract, and/or rule_stage (e.g. "Proposed Rule Stage", "Final Rule Stage", "Prerule Stage", "Long-Term Actions", "Completed Actions"). Defaults to the newest edition on file when edition is omitted. This is the LEADING record — an intent shows up here, often years before the same rule appears in eCFR or the Federal Register.

Input parameters:

- `agency` (string): Agency name, acronym, or code, e.g. "EPA", "Environmental Protection Agency", "2000". Matched case-insensitively against name/acronym/code, and against the PARENT agency too (so "Interior" matches it…
- `edition` (string): Restrict to one edition, YYYYMM (e.g. "202504"). Defaults to the newest edition actually loaded.
- `keyword` (string): Free-text match (case-insensitive) against the rule title and abstract, e.g. "menthol", "PFAS", "overtime".
- `limit` (number|string): Max RINs to return (1-100, default 25).
- `stage` (string): Restrict to one rulemaking stage, e.g. "Proposed Rule Stage", "Final Rule Stage", "Prerule Stage", "Long-Term Actions", "Completed Actions". Substring match.

### `reg_rin` (~139 tokens)

Full detail for one Regulation Identifier Number (RIN), across EVERY Unified Agenda edition it has appeared in — proving the rule's history rather than just its latest status. Returns the abstract, agency, and one entry per edition showing how rule_stage, rin_status, and priority_category changed over time. Answers "what is RIN 2060-AV62 about", "history of this rulemaking", "has this rule stalled or progressed".

Input parameters:

- `rin` (string, required): The RIN, e.g. "2060-AV62" (format AAAA-Bnnn — 4-char agency code, letter, 3 digits/letters).

### `reg_agency_agenda` (~181 tokens)

One agency's full regulatory agenda for a given (or the newest) edition — every RIN it has open, grouped by rule_stage. Answers "what is EPA's regulatory agenda", "how many rules does DOL have in the proposed stage". Use reg_agenda_search instead when filtering by keyword or across agencies.

Input parameters:

- `agency` (string, required): Agency name, acronym, or code, e.g. "EPA", "Department of Labor", "1200". Matched case-insensitively against name/acronym/code, and against the PARENT agency (so a sub-agency's rules are included whe…
- `edition` (string): Edition YYYYMM. Defaults to the newest edition actually loaded.
- `limit` (number|string): Max RINs to return (1-200, default 100).

### `reg_agenda_coverage` (~79 tokens)

Reports which Unified Agenda editions are currently loaded — the oldest and newest edition on file, total edition count, and total RIN-edition rows. Use to gauge coverage before relying on this for a historical range or a specific edition, since the biannual backfill drains in gradually rather than loading all history from 1995 in one pass.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-reginfo/pipeworx-mcp-reginfo#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Reginfo MCP server?

Reginfo is an MCP server listed in the public MCP registry as io.github.pipeworx-io/reginfo. reginfo MCP, the Unified Agenda of Federal Regulatory and Deregulatory Actions, from reginfo.gov… This page covers its npm package (@pipeworx/mcp-reginfo).

### Is the Reginfo MCP server safe to use?

Reginfo scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Reginfo MCP server expose?

Reginfo exposes 4 tools: reg_agenda_search, reg_rin, reg_agency_agenda, reg_agenda_coverage. Their descriptions and schemas cost roughly 771 tokens of context every time the server is loaded.

### Is the Reginfo MCP server still maintained?

Reginfo is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Reginfo MCP server under?

Reginfo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-reginfo
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-reginfo
- Repository: https://github.com/pipeworx-io/mcp-reginfo
- Website: https://pipeworx.io/packs/reginfo
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-reginfo/pipeworx-mcp-reginfo.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-reginfo/pipeworx-mcp-reginfo.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-reginfo/pipeworx-mcp-reginfo