# Regulations.gov (pypi · regulationsgov-mcp)

Regulations.gov readiness, rulemaking dockets, documents, comments, and comment periods. 9 tools.

- Trust score: 64/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `regulationsgov-mcp`: 64/100 (this document), [markdown](https://verifymcp.io/servers/com-1102tools-regulations-gov-mcp/regulationsgov-mcp.md), [page](https://verifymcp.io/servers/com-1102tools-regulations-gov-mcp/regulationsgov-mcp)

## Channel facts

- Registry: `pypi`
- Package: `regulationsgov-mcp`
- Version: `1.0.9`
- 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-09-20.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 1 of 34 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

### Claude

```bash
claude mcp add com-1102tools-regulations-gov-mcp -- uvx regulationsgov-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-1102tools-regulations-gov-mcp": {
      "command": "uvx",
      "args": [
        "regulationsgov-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-1102tools-regulations-gov-mcp": {
      "command": "uvx",
      "args": [
        "regulationsgov-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-1102tools-regulations-gov-mcp -- uvx regulationsgov-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-1102tools-regulations-gov-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "regulationsgov-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-1102tools-regulations-gov-mcp --command uvx --arg regulationsgov-mcp
```

### Hermes

```yaml
mcp_servers:
  com-1102tools-regulations-gov-mcp:
    command: "uvx"
    args: ["regulationsgov-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-1102tools-regulations-gov-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "regulationsgov-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-1102tools-regulations-gov-mcp -t stdio -c uvx -a regulationsgov-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-1102tools-regulations-gov-mcp": {
      "command": "uvx",
      "args": [
        "regulationsgov-mcp"
      ]
    }
  }
}
```

## 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-09-19 (score 64, +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.

### 2026-09-17 (score 63, +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.

### 2026-09-15 (score 62, +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.

### 2026-09-13 (score 61, +1)

- [functional] Package version: 1.0.8 → 1.0.9

### 2026-09-10 (score 60, +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.

### 2026-09-08 (score 59, +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.

### 2026-09-06 (score 58, +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.

### 2026-09-05 (score 57, −15)

- [security regression] Malware scan: pass → unverified

## MCP tools (9)

### `get_access_status` (~20 tokens)

Check Regulations.gov credential presence without returning or validating it.

### `search_documents` (~459 tokens)

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').

Input parameters:

- `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`

### `get_document_detail` (~89 tokens)

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

Input parameters:

- `document_id` (string, required)
- `include_attachments` (boolean)

### `search_comments` (~181 tokens)

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.

Input parameters:

- `agency_id`
- `comment_on_id`
- `docket_id`
- `page_number` (integer)
- `page_size` (integer)
- `posted_date_ge`
- `posted_date_le`
- `search_term`
- `sort` (string)

### `get_comment_detail` (~78 tokens)

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.

Input parameters:

- `comment_id` (string, required)
- `include_attachments` (boolean)

### `search_dockets` (~178 tokens)

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.

Input parameters:

- `agency_id`
- `docket_type`
- `last_modified_date_ge`
- `last_modified_date_le`
- `page_number` (integer)
- `page_size` (integer)
- `search_term`
- `sort`

### `get_docket_detail` (~77 tokens)

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

Input parameters:

- `docket_id` (string, required)

### `open_comment_periods` (~155 tokens)

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.

Input parameters:

- `agency_ids`

### `far_case_history` (~147 tokens)

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.

Input parameters:

- `docket_id` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-1102tools-regulations-gov-mcp/regulationsgov-mcp#diagnostics

## Score history

- 2026-09-20: 64
- 2026-09-19: 64
- 2026-09-18: 63
- 2026-09-17: 63
- 2026-09-16: 62
- 2026-09-15: 62
- 2026-09-14: 61
- 2026-09-13: 61
- 2026-09-12: 60
- 2026-09-11: 60
- 2026-09-10: 60
- 2026-09-09: 59
- 2026-09-08: 59
- 2026-09-07: 58
- 2026-09-06: 58
- 2026-09-05: 57
- 2026-09-04: 72
- 2026-09-03: 56
- 2026-09-02: 56
- 2026-09-01: 70
- 2026-08-31: 55
- 2026-08-30: 69
- 2026-08-29: 69
- 2026-08-28: 68
- 2026-08-27: 53
- 2026-08-26: 52
- 2026-08-25: 64
- 2026-08-24: 49

## Common questions

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

## Links

- PyPI project: https://pypi.org/project/regulationsgov-mcp/
- Socket report: https://socket.dev/pypi/package/regulationsgov-mcp
- Repository: https://github.com/1102tools-dev/federal-contracting-mcps
- Website: https://1102tools.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-1102tools-regulations-gov-mcp/regulationsgov-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-1102tools-regulations-gov-mcp/regulationsgov-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-1102tools-regulations-gov-mcp/regulationsgov-mcp