Docketwatch

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 7, 2026

Track Regulations.gov dockets, documents and public comments; open comment periods, FAR cases.

VerifiedSTDIODesktop only

Overview

Docketwatch's local MCP server; no sign-in required; STDIO; 9 tools.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Docketwatch in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

docketwatch

Follow the federal rulemaking record without living in a browser tab. docketwatch talks to the Regulations.gov API v4 — the public record of dockets, documents and public comments behind rules published by US agencies — and answers with the API's own JSON, so a search result here is the same payload you would get from the API directly.

You will need a free api.data.gov key:

bash
export REGULATIONS_GOV_API_KEY="<your key>"

Get one at https://api.data.gov/signup. The key goes out as the X-Api-Key header on every data call. If the variable is unset the server still starts and lists its tools, but every data tool replies with setup instructions and makes no request at all — handy for checking that a client is wired up before a key exists. get_access_status is the exception: it never calls out and reports only {"configured": true} or {"configured": false}, never the key itself. The base URL defaults to https://api.regulations.gov/v4 and can be overridden with REGULATIONS_GOV_API_BASE.

The nine tools:

  • search_documents — find documents (proposed rules, rules, notices, supporting material) by keyword, agency, docket and posted/modified date windows.
  • get_document_detail — one document in full; pass include_attachments: true to ask the API to include its attachments.
  • search_comments — search the public comments by keyword, agency, docket, or the document commented on.
  • get_comment_detail — one comment's full text and submitter information.
  • search_dockets — search rulemaking and nonrulemaking dockets by keyword or agency.
  • get_docket_detail — one docket's metadata, abstract and RIN.
  • open_comment_periods — composition (labelled): not a single API call. It pages through documents posted in the last 180 days (the scan window is a local choice), keeps those whose comment period ends today or later, and returns them soonest-closing first alongside complete and truncated flags.
  • far_case_history — composition (labelled): fetches a FAR/DFARS case docket (for example FAR-2023-0008) together with every page of that docket's documents, concatenated, plus a complete flag saying whether all pages were read.
  • get_access_status — the key check described above.

Search arguments are flat names that map onto the API's documented filter[...] parameters, with sort, page[number] and page[size] for ordering and paging. Filter values are case-sensitive — the API treats EPA and epa differently — and docketwatch passes them through unchanged.

One honest gap: the API documentation used for this build does not pin a document-type or docket-type filter parameter name, so no type filter argument is exposed. Keyword, agency, docket and date filters cover the documented surface.

CLI

Each tool is a subcommand taking one JSON argument string (get_access_status takes none):

bash
npx @reneturcios/docketwatch search_documents '{"agency_id":"EPA","search_term":"emissions"}'npx @reneturcios/docketwatch get_document_detail '{"document_id":"EPA-HQ-OAR-2020-0001-0001","include_attachments":true}'npx @reneturcios/docketwatch search_comments '{"docket_id":"EPA-HQ-OAR-2020-0001"}'npx @reneturcios/docketwatch open_comment_periods '{"agency_id":"EPA","limit":20}'npx @reneturcios/docketwatch far_case_history '{"case_number":"FAR-2023-0008"}'npx @reneturcios/docketwatch get_access_statusnpx @reneturcios/docketwatch --version

Output is the tool's result text (JSON for every tool). Exit codes: 0 on success, 1 on a runtime error (including a validation, missing-key or upstream failure), 2 on a usage error.

MCP server

bash
npx -y @reneturcios/docketwatch mcp

MCP client config:

json
{  "mcpServers": {    "docketwatch": {      "command": "npx",      "args": ["-y", "@reneturcios/docketwatch", "mcp"],      "env": {        "REGULATIONS_GOV_API_KEY": "<your key>"      }    }  }}

Docker

bash
docker run -i -e REGULATIONS_GOV_API_KEY="<your key>" ghcr.io/cloudcorprecords/docketwatchdocker run --rm -e REGULATIONS_GOV_API_KEY="<your key>" ghcr.io/cloudcorprecords/docketwatch get_access_status

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # tsx --test test/*.test.ts (fake fetch + fake clock, no network)npm run dev     # run the CLI from source

License

MIT — Copyright (c) 2026 Rene Turcios

Source: README.md at commit bd97379

Tools

9

search_documents

Search Regulations.gov documents: proposed rules, rules, notices and supporting material.

Parameterssortagency_iddocket_idpage_sizepage_numberposted_datesearch_termposted_date_gteposted_date_ltelast_modified_date_gte

get_document_detail

Full details of one Regulations.gov document, optionally with attachments.

Parametersdocument_idrequiredinclude_attachments

search_comments

Search public comments by docket, document or keyword.

Parameterssortagency_iddocket_idpage_sizepage_numbersearch_termcomment_on_idposted_date_gteposted_date_lte

get_comment_detail

Full text and submitter info of one public comment.

Parameterscomment_idrequired

search_dockets

Search rulemaking and nonrulemaking dockets.

Parameterssortagency_idpage_sizepage_numbersearch_term

get_docket_detail

Docket metadata, abstract and RIN.

Parametersdocket_idrequired

open_comment_periods

Currently open comment periods across procurement agencies.

Parameterslimitagency_idsearch_term

far_case_history

A FAR/DFARS rulemaking case: its docket and documents, paged.

Parameterscase_numberrequired

get_access_status

Check whether a Regulations.gov API key is configured, without revealing it.

Takes no parameters.

Version history

1
  1. v0.1.0LatestNov 3, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts