Regulations.gov
PYPI · REGULATIONSGOV-MCP · SCANNED SEP 20
Regulations.gov readiness, rulemaking dockets, documents, comments, and comment periods. 9 tools.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 34 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1421 tokens (~157/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Regulations.gov MCP server?
Regulations.gov runs locally as a PyPI package, launched with uvx regulationsgov-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · regulationsgov-mcp
claude mcp add com-1102tools-regulations-gov-mcp -- uvx regulationsgov-mcp
{
"mcpServers": {
"com-1102tools-regulations-gov-mcp": {
"command": "uvx",
"args": [
"regulationsgov-mcp"
]
}
}
} {
"servers": {
"com-1102tools-regulations-gov-mcp": {
"command": "uvx",
"args": [
"regulationsgov-mcp"
]
}
}
} codex mcp add com-1102tools-regulations-gov-mcp -- uvx regulationsgov-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-1102tools-regulations-gov-mcp": {
"type": "local",
"command": [
"uvx",
"regulationsgov-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-1102tools-regulations-gov-mcp --command uvx --arg regulationsgov-mcp
mcp_servers:
com-1102tools-regulations-gov-mcp:
command: "uvx"
args: ["regulationsgov-mcp"] {
"McpServers": {
"com-1102tools-regulations-gov-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"regulationsgov-mcp"
]
}
}
} assistant mcp add com-1102tools-regulations-gov-mcp -t stdio -c uvx -a regulationsgov-mcp
{
"mcpServers": {
"com-1102tools-regulations-gov-mcp": {
"command": "uvx",
"args": [
"regulationsgov-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
- Package version: 1.0.8 → 1.0.9 functional
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 −15
- Malware scan: pass → unverified ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/regulationsgov-mcp@1.0.9
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 34 packages
| Packages resolved | 34 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
far_case_history ~147
Get the full lifecycle of a FAR/DFARS rulemaking case. Fetches the docket metadata (title, abstract, RIN) plus the documents filed under the docket, sorted by most recent first. Follows pagination up to 1,000 documents (4 pages); larger dockets set truncated=true (FAR/DARS dockets are far smaller, but the tool accepts any docket). docket_id examples: FAR-2023-0008, DARS-2025-0071 Returns the docket abstract, RIN (links to Unified Agenda), and the documents with their types, dates, and URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| docket_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_access_status ~20
Check Regulations.gov credential presence without returning or validating it.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_comment_detail ~78
Get full details for a single comment. Returns the full comment text, organization, submitter info (if public), tracking number, and duplicate comment count. Some fields (firstName, lastName, organization) are agency-configurable and may be hidden.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | – |
| include_attachments | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_docket_detail ~77
Get full details for a single docket. Returns title, abstract, RIN (links to Unified Agenda), agency, keywords, and modification date. docket_id format: FAR-2023-0008, DARS-2025-0071, SBA-2024-0002
| Name | Type | Req | Description |
|---|---|---|---|
| docket_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_document_detail ~89
Get full details for a single Regulations.gov document. Returns fileFormats (download URLs), cfrPart, displayProperties, and other detail fields not available in search results. Set include_attachments=True to get attachment objects with download URLs. document_id format: FAR-2023-0008-0023
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | – |
| include_attachments | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
open_comment_periods ~155
Find documents with currently open comment periods. Searches for documents where withinCommentPeriod=true, sorted by soonest closing deadline (ascending commentEndDate, so even when the result set is truncated it keeps the deadlines you can still act on). Returns document IDs, titles, agencies, comment end dates, docket IDs, the API-true total_open, and a truncated flag when more exist than the 250 returned. Default searches FAR, DARS, GSA, SBA, OFPP, DOD, NASA, VA in a single comma-joined query. Pass agency_ids to narrow or expand the scope. An empty list is rejected; pass None to use the defaults.
| Name | Type | Req | Description |
|---|---|---|---|
| agency_ids | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_comments ~181
Search public comments on Regulations.gov. To find comments on a specific document, use comment_on_id with the hex objectId from document detail/search results (attributes.objectId, e.g. '0900006486531e6b'). The human-readable documentId is REJECTED here because the API silently returns 0 comments for it. docket_id can also filter comments to all documents in a docket (undocumented upstream but verified working live). Page size: 5-250. Comments sorted by '-postedDate' by default.
| Name | Type | Req | Description |
|---|---|---|---|
| agency_id | – | – | – |
| comment_on_id | – | – | – |
| docket_id | – | – | – |
| page_number | integer | – | – |
| page_size | integer | – | – |
| posted_date_ge | – | – | – |
| posted_date_le | – | – | – |
| search_term | – | – | – |
| sort | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_dockets ~178
Search Regulations.gov dockets. Dockets are containers for related regulatory documents (proposed rules, comments, supporting materials). FAR cases, DFARS cases, and agency rulemaking actions each have a docket. docket_type is CASE-SENSITIVE: 'Rulemaking' or 'Nonrulemaking'. lastModifiedDate format: 'YYYY-MM-DD HH:MM:SS' (space-separated, NOT ISO). This is a Regulations.gov quirk; ISO 8601 is rejected. Limited filters: only searchTerm, agencyId, docketType, lastModifiedDate.
| Name | Type | Req | Description |
|---|---|---|---|
| agency_id | – | – | – |
| docket_type | – | – | – |
| last_modified_date_ge | – | – | – |
| last_modified_date_le | – | – | – |
| page_number | integer | – | – |
| page_size | integer | – | – |
| search_term | – | – | – |
| sort | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_documents ~459
Search Regulations.gov documents (proposed rules, final rules, notices). Filter values are CASE-SENSITIVE. Use exact casing: - document_type: 'Proposed Rule', 'Rule', 'Notice', 'Supporting & Related Material', 'Other' - Lowercase values silently return 0 results (no error) Key parameters: - agency_id: FAR, DARS, GSA, SBA, OFPP, DOD, NASA, VA, etc. Comma-separate for multiple agencies ('FAR,GSA'). Empty string is REJECTED (previously returned all 1.95M records). - docket_id: e.g., 'FAR-2023-0008' for a specific FAR case - within_comment_period: True to find documents currently accepting comments. False is NOT supported by the API (it 400s); omit the parameter instead to search regardless of comment status. - posted_date_ge/le: YYYY-MM-DD format (calendar-checked) - comment_end_date_ge/le: YYYY-MM-DD format Response includes meta.aggregations with counts by document type, agency, and comment period status. Page size: 5-250. page_number: 1-40 (10,000 reachable records per query; the live API allows 40 pages even though the docs say 20). For larger sets, partition with date ranges, or use the API's deep pagination recipe: sort='lastModifiedDate,documentId' plus lastModifiedDate windows on search_dockets/search_comments. sort: '-postedDate' (newest first, default), 'postedDate', '-commentEndDate', 'lastModifiedDate', 'title', 'documentId'. Comma-separate for multi-field sorts ('lastModifiedDate,documentId').
| Name | Type | Req | Description |
|---|---|---|---|
| agency_id | – | – | – |
| comment_end_date_ge | – | – | – |
| comment_end_date_le | – | – | – |
| docket_id | – | – | – |
| document_type | – | – | – |
| page_number | integer | – | – |
| page_size | integer | – | – |
| posted_date_ge | – | – | – |
| posted_date_le | – | – | – |
| search_term | – | – | – |
| sort | string | – | – |
| within_comment_period | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Regulations.gov MCP server?
Regulations.gov is an MCP server listed in the public MCP registry as com.1102tools/regulations-gov-mcp. Regulations.gov readiness, rulemaking dockets, documents, comments, and comment periods. 9 tools. This page covers its PyPI package (regulationsgov-mcp).
Is the Regulations.gov MCP server safe to use?
Regulations.gov scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 Regulations.gov MCP server expose?
Regulations.gov exposes 9 tools: get_access_status, search_documents, get_document_detail, search_comments, get_comment_detail, and 4 more. Their descriptions and schemas cost roughly 1,384 tokens of context every time the server is loaded.
Is the Regulations.gov MCP server still maintained?
Regulations.gov is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Regulations.gov MCP server under?
Regulations.gov declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.