io.github.CloudCorpRecords/docketwatch
OCI · GHCR.IO/CLOUDCORPRECORDS/DOCKETWATCH · 2 COMPONENTS
Track Regulations.gov dockets, documents and public comments; open comment periods, FAR cases.
Available components
Last scanned (23 hours ago)
Scores higher than 39% of OCI 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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
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 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 640 tokens (~71/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 3 Nov 26 39
First indexed and scored.
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 4 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/docketwatch@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 ~40
A FAR/DFARS rulemaking case: its docket and documents, paged.
| Name | Type | Req | Description |
|---|---|---|---|
| case_number | string | yes | The case number for this call. |
No output schema declared.
No examples provided.
get_access_status ~23
Check whether a Regulations.gov API key is configured, without revealing it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_comment_detail ~34
Full text and submitter info of one public comment.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | The comment identifier for this call. |
No output schema declared.
No examples provided.
get_docket_detail ~31
Docket metadata, abstract and RIN.
| Name | Type | Req | Description |
|---|---|---|---|
| docket_id | string | yes | Identifier of the docket. |
No output schema declared.
No examples provided.
get_document_detail ~50
Full details of one Regulations.gov document, optionally with attachments.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | The document identifier for this call. |
| include_attachments | boolean | – | The include attachments for this call. |
No output schema declared.
No examples provided.
open_comment_periods ~55
Currently open comment periods across procurement agencies.
| Name | Type | Req | Description |
|---|---|---|---|
| agency_id | string | – | Identifier of the agency. |
| limit | integer | – | Maximum number of results to return (optional). |
| search_term | string | – | Search term. |
No output schema declared.
No examples provided.
search_comments ~149
Search public comments by docket, document or keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| agency_id | string | – | Identifier of the agency. |
| comment_on_id | string | – | The comment on identifier for this call. |
| docket_id | string | – | Identifier of the docket. |
| page_number | integer | – | Page number for paginated results (optional). |
| page_size | integer | – | Number of results per page (optional). |
| posted_date_gte | string | – | The posted date gte for this call. |
| posted_date_lte | string | – | The posted date lte for this call. |
| search_term | string | – | Search term. |
| sort | string | – | Sort order for the results (optional). |
No output schema declared.
No examples provided.
search_dockets ~86
Search rulemaking and nonrulemaking dockets.
| Name | Type | Req | Description |
|---|---|---|---|
| agency_id | string | – | Identifier of the agency. |
| page_number | integer | – | Page number for paginated results (optional). |
| page_size | integer | – | Number of results per page (optional). |
| search_term | string | – | Search term. |
| sort | string | – | Sort order for the results (optional). |
No output schema declared.
No examples provided.
search_documents ~172
Search Regulations.gov documents: proposed rules, rules, notices and supporting material.
| Name | Type | Req | Description |
|---|---|---|---|
| agency_id | string | – | Identifier of the agency. |
| docket_id | string | – | Identifier of the docket. |
| last_modified_date_gte | string | – | The last modified date gte for this call. |
| page_number | integer | – | Page number for paginated results (optional). |
| page_size | integer | – | Number of results per page (optional). |
| posted_date | string | – | The posted date for this call. |
| posted_date_gte | string | – | The posted date gte for this call. |
| posted_date_lte | string | – | The posted date lte for this call. |
| search_term | string | – | Search term. |
| sort | string | – | Sort order for the results (optional). |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/docketwatch MCP server?
io.github.CloudCorpRecords/docketwatch runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/docketwatch:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/cloudcorprecords/docketwatch
claude mcp add cloudcorprecords-docketwatch -- docker run --rm -i ghcr.io/cloudcorprecords/docketwatch:0.1.0
What is the io.github.CloudCorpRecords/docketwatch MCP server?
io.github.CloudCorpRecords/docketwatch is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/docketwatch. Track Regulations.gov dockets, documents and public comments; open comment periods, FAR cases. This page covers its container image (ghcr.io/cloudcorprecords/docketwatch).
Is the io.github.CloudCorpRecords/docketwatch MCP server safe to use?
io.github.CloudCorpRecords/docketwatch scores 39 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 io.github.CloudCorpRecords/docketwatch MCP server expose?
io.github.CloudCorpRecords/docketwatch exposes 9 tools: search_documents, get_document_detail, search_comments, get_comment_detail, search_dockets, and 4 more. Their descriptions and schemas cost roughly 640 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/docketwatch MCP server still maintained?
io.github.CloudCorpRecords/docketwatch is still listed as active in the MCP registry. We last reached this channel on 4 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 io.github.CloudCorpRecords/docketwatch MCP server under?
io.github.CloudCorpRecords/docketwatch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.