Regulations.gov
PYPI · REGULATIONSGOV-MCP · 2 COMPONENTS
Regulations.gov readiness, rulemaking dockets, documents, comments, and comment periods. 9 tools.
Available components
Last scanned (4 hours ago)
Scores higher than 93% of PyPI servers
Category Education and Research
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 33 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to 1102tools-dev/federal-contracting-mcps). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2382 tokens (~264/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 9 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
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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
- 31 Oct 26 0
- Package version: 2.0.7 → 2.0.10 functional
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ 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 5 Nov 2026 · Analysed pypi/regulationsgov-mcp@2.0.10
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | 1102tools-dev/federal-contracting-mcps |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/1102tools-dev/federal-contracting-mcps/.github/workflows/publish-pypi.yml@refs/tags/v1.0.35 |
| Rekor log index | 3527328904 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:57336e0394de0d21aaccf62e7048e80b4bd12fbf5c3424e756f4e1c816c42212 |
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 33 packages
| Packages resolved | 33 |
|---|---|
| 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 ~313
Get the lifecycle of a FAR/DFARS rulemaking case, summary first. Returns the docket metadata (title, abstract, RIN linking to the Unified Agenda), the docket's total document count, counts by document type and of documents open for comment across the whole docket, and one page of its documents, most recent first, with types, subtypes, Federal Register document numbers, dates, and URLs. subtype tells a withdrawal, extension, or correction apart from a new proposed rule (a withdrawal keeps document_type 'Proposed Rule'). comment_deadline is the Regulations.gov metadata date in Eastern time; comment_end_date_utc preserves its UTC instant. comment_deadline_verification links to the notice/docket. Read DATES, eligibility, and later extensions before treating it as controlling; if unavailable, the controlling date cannot be established. Page 1 also gives posted_comments for the whole docket: comments posted publicly, not comments received (mass-mail duplicates and unposted comments are not in it). When the docket has more documents, truncated=true and next_page_number gives the page that continues the list. page_size: 5-100 documents per page (default 25). page_number: 1-40. docket_id examples: FAR-2023-0008, DARS-2025-0071
| Name | Type | Req | Description |
|---|---|---|---|
| docket_id | string | yes | – |
| page_number | integer | – | – |
| page_size | integer | – | – |
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 ~130
Get full details for a single comment. Returns the comment text field, organization, submitter info (if public), tracking number, and duplicate comment count. Many comments put their substance in attachments and the text field only says "See attached"; include_attachments=True returns the attachment download URLs. Some fields (firstName, lastName, organization) are agency-configurable and may be hidden. The comment text comes back as plain text (HTML breaks become newlines; tags and entities are decoded).
| 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 ~181
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. Comment deadlines: attributes.commentDeadlineEastern is the date reported by Regulations.gov metadata in Eastern time (e.g. 'Oct 22, 2026 11:59 PM ET'). The raw commentEndDateUtc is the provider UTC instant. commentDeadlineVerification links to the notice/docket: read DATES, eligibility, and later extensions before treating this metadata date as controlling. If unavailable, the controlling deadline cannot be established. 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 ~346
Find documents Regulations.gov reports as open for comment. Searches for documents where withinCommentPeriod=true, sorted by soonest reported closing date (ascending commentEndDate). Page 1 holds the earliest metadata dates; verify the notice before planning a submission. Returns document IDs, titles, agencies, document types and subtypes, Federal Register document numbers, comment deadlines, docket IDs, and the API-true total_open. comment_deadline is the Regulations.gov metadata date in Eastern time (e.g. 'Oct 22, 2026 11:59 PM ET'); comment_end_date_utc preserves its UTC instant. comment_deadline_verification links to the notice/docket. Read DATES, eligibility, and later extensions before treating it as controlling; if those sources are unavailable, the controlling date is not established. When more documents exist, truncated=true and next_page_number gives the page that continues the list (later pages have later reported dates). page_size: 5-100 documents per page (default 25). page_number: 1-40. 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. Most open DOD and VA documents are Paperwork Reduction Act and Privacy Act notices; for rules only, pass document_type='Proposed Rule' (exact casing).
| Name | Type | Req | Description |
|---|---|---|---|
| agency_ids | – | – | – |
| document_type | – | – | – |
| page_number | integer | – | – |
| page_size | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_comments ~403
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 filters comments to all documents in a docket. search_term is a full-text match, including attachment text; results follow sort, not relevance. Quote a phrase ('"Professional Services Council"') to match it exactly. posted_comments (= meta.totalElements) counts comments posted publicly, not comments received; mass-mail duplicates and unposted comments are not in it, so the agency's received count can be much higher. Search rows carry no organization (the API leaves it out), and many titles are only "Comment on FR Doc # ...". For "who commented" questions set include_organization=True (page_size up to 25): each row gets the submitter's organization from its comment detail. Rows without one were filed by individuals or the agency hid the field. Page size: 5-100; page_number 1-40. Comments sorted by '-postedDate' by default. The API serves 40 pages; when more comments match, page_limit_note (and truncated=true on page 40) says how many are out of reach. Split the query into posted_date_ge/le windows. Most comment text is in attachments; get_comment_detail with include_attachments=True returns their download URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| agency_id | – | – | – |
| comment_on_id | – | – | – |
| docket_id | – | – | – |
| include_organization | boolean | – | – |
| 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 ~307
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. sort: 'title', 'docketId', 'lastModifiedDate'; prefix '-' for descending ('-lastModifiedDate' lists the most recently active dockets first). Catch-all dockets such as DARS_FRDOC_0001 and SBA_FRDOC_0001 hold miscellaneous Federal Register documents and often top that list. Page size: 5-100; page_number 1-40. The API serves 40 pages; when more dockets match, page_limit_note (and truncated=true on page 40) says how many are out of reach. Split the query into last_modified_date_ge/le windows.
| 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 ~605
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: - search_term: full-text match, including attachment text. Results follow sort (newest first by default), not relevance, so an unquoted multi-word term puts loosely matching recent documents first; quote a phrase ('"Pay Equity and Transparency"') to match it exactly. - agency_id: FAR, DARS, GSA, SBA, OFPP, DOD, NASA, VA, etc. Comma-separate for multiple agencies ('FAR,GSA'). Empty string is rejected. - 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 meta.facets gives the top counts by document type, agency, and comment period status; a facet the query filtered on is left out, because the API counts it site-wide. meta.totalElements is the full match count. Comment deadlines: attributes.commentDeadlineEastern is the date reported by Regulations.gov metadata in Eastern time (e.g. 'Oct 22, 2026 11:59 PM ET'). The raw commentEndDateUtc is the provider UTC instant. commentDeadlineVerification links to the notice/docket: read DATES, eligibility, and later extensions before treating this metadata date as controlling. If unavailable, the controlling deadline cannot be established. Page size: 5-100. page_number: 1-40. The API serves 40 pages; when more records match, page_limit_note (and truncated=true on page 40) says how many are out of reach. Split the query into posted_date_ge/le windows. sort: '-postedDate' (newest first, default), 'postedDate', '-commentEndDate',…
| 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.
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
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 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 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 2,382 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 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 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.