reg_agenda_search
Pack: reginfo · Endpoint: https://gateway.pipeworx.io/reginfo/mcp
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.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
agency | string | no | 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 its sub-agencies). |
keyword | string | no | Free-text match (case-insensitive) against the rule title and abstract, e.g. “menthol”, “PFAS”, “overtime”. |
stage | string | no | Restrict to one rulemaking stage, e.g. “Proposed Rule Stage”, “Final Rule Stage”, “Prerule Stage”, “Long-Term Actions”, “Completed Actions”. Substring match. |
edition | string | no | Restrict to one edition, YYYYMM (e.g. “202504”). Defaults to the newest edition actually loaded. |
limit | number,string | no | Max RINs to return (1-100, default 25). |
Example call
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_agenda_search","arguments":{}}}'
Connect
Add this to your MCP client config:
{
"mcpServers": {
"reginfo": {
"url": "https://gateway.pipeworx.io/reginfo/mcp"
}
}
}
See Getting Started for client-specific install steps.