`reg_rin`

Pack: reginfo · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/reg_rin for the schema, then POST the same URL with its arguments for the data.

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”.

Parameters

Name	Type	Required	Description
`rin`	string	yes	The RIN, e.g. “2060-AV62” (format AAAA-Bnnn — 4-char agency code, letter, 3 digits/letters).

Example call

Arguments

{
  "rin": "2060-AV62"
}

curl

curl -X POST https://gateway.pipeworx.io/reginfo/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"reg_rin","arguments":{"rin":"2060-AV62"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('reg_rin', {
  "rin": "2060-AV62"
});

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

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

Connect to just the reginfo pack

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

See Getting Started for client-specific install steps.

reg_rin