# Regulations.gov (remote · regulations-gov.1102tools.com) Regulations.gov readiness, rulemaking dockets, documents, comments, and comment periods. 9 tools. - Trust score: 69/100 (medium) - Change this week: +4 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - remote · `regulations-gov.1102tools.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-1102tools-regulations-gov-mcp/regulations-gov.md), [page](https://verifymcp.io/servers/com-1102tools-regulations-gov-mcp/regulations-gov) - pypi · `regulationsgov-mcp`: 90/100, [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 - Endpoint: `https://regulations-gov.1102tools.com/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `2.0.10` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-11-05. - **Endpoint Security**: 63/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 59/100 - AI-judged instruction clarity (good). - Context-footprint check failed: tool/resource definitions use about 2497 tokens (~277/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**: 50/100 - Stability observed for 15 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 9 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 is a hosted endpoint at https://regulations-gov.1102tools.com/mcp, so there is nothing to install locally. 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 --transport http com-1102tools-regulations-gov-mcp 'https://regulations-gov.1102tools.com/mcp' ``` ### Cursor ```json { "mcpServers": { "com-1102tools-regulations-gov-mcp": { "url": "https://regulations-gov.1102tools.com/mcp" } } } ``` ### VS Code ```json { "servers": { "com-1102tools-regulations-gov-mcp": { "type": "http", "url": "https://regulations-gov.1102tools.com/mcp" } } } ``` ### Codex ```toml [mcp_servers.com-1102tools-regulations-gov-mcp] url = "https://regulations-gov.1102tools.com/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "com-1102tools-regulations-gov-mcp": { "type": "remote", "url": "https://regulations-gov.1102tools.com/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add com-1102tools-regulations-gov-mcp --url 'https://regulations-gov.1102tools.com/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: com-1102tools-regulations-gov-mcp: url: "https://regulations-gov.1102tools.com/mcp" ``` ### Netclaw ```json { "McpServers": { "com-1102tools-regulations-gov-mcp": { "Transport": "http", "Url": "https://regulations-gov.1102tools.com/mcp" } } } ``` ### Vellum ```bash assistant mcp add com-1102tools-regulations-gov-mcp -t streamable-http -u 'https://regulations-gov.1102tools.com/mcp' ``` ### Other ```json { "mcpServers": { "com-1102tools-regulations-gov-mcp": { "type": "http", "url": "https://regulations-gov.1102tools.com/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## 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-11-05 (score 69, +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-11-03 (score 68, +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-11-01 (score 67, +1) No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-30 (score 66, +1) No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-28 (score 65, +1) No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-27 (score 64, 0) - [functional] Server version: 2.0.9 → 2.0.10 - [functional] Server version: 2.0.8 → 2.0.9 ### 2026-10-26 (score 64, +1) No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-24 (score 63, +1) No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes. ## MCP tools (9) ### `get_access_status` (~20 tokens) Check Regulations.gov credential presence without returning or validating it. ### `search_documents` (~630 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: - 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… 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` (~191 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. 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 Input parameters: - `document_id` (string, required) - `include_attachments` (boolean) ### `search_comments` (~423 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 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. Input parameters: - `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) ### `get_comment_detail` (~136 tokens) 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). Input parameters: - `comment_id` (string, required) - `include_attachments` (boolean) ### `search_dockets` (~322 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. 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. 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` (~80 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` (~365 tokens) 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). Input parameters: - `agency_ids` - `document_type` - `page_number` (integer) - `page_size` (integer) ### `far_case_history` (~330 tokens) 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 Input parameters: - `docket_id` (string, required) - `page_number` (integer) - `page_size` (integer) ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-1102tools-regulations-gov-mcp/regulations-gov#diagnostics ## Score history - 2026-11-05: 69 - 2026-11-04: 68 - 2026-11-03: 68 - 2026-11-02: 67 - 2026-11-01: 67 - 2026-10-31: 66 - 2026-10-30: 66 - 2026-10-29: 65 - 2026-10-28: 65 - 2026-10-27: 64 - 2026-10-26: 64 - 2026-10-25: 63 - 2026-10-24: 63 - 2026-10-23: 62 - 2026-10-22: 62 - 2026-10-21: 62 ## 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 hosted endpoint (https://regulations-gov.1102tools.com/mcp). ### Is the Regulations.gov MCP server safe to use? Regulations.gov scores 69 out of 100 on VerifyMCP. 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,497 tokens of context every time the server is loaded. ### Does the Regulations.gov MCP server require authentication? No. We connected to Regulations.gov without credentials and it answered, so anything it exposes is reachable by anyone who knows the address. ### 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. ## Links - Remote endpoint: https://regulations-gov.1102tools.com/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/regulations-gov.xml - Changelog JSON feed: https://verifymcp.io/servers/com-1102tools-regulations-gov-mcp/regulations-gov.json - HTML version of this page: https://verifymcp.io/servers/com-1102tools-regulations-gov-mcp/regulations-gov