Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Track Regulations.gov dockets, documents and public comments; open comment periods, FAR cases.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"docketwatch": {
"command": "npx",
"args": [
"-y",
"@reneturcios/docketwatch",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add docketwatch -- npx -y @reneturcios/docketwatch mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"docketwatch": {
"command": "npx",
"args": [
"-y",
"@reneturcios/docketwatch",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"docketwatch": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/docketwatch",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 CloudCorpRecords 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.0)于3天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js, Docker。
同一分类中有:Spec Driven Development, Remote Desktop Commander, FOGA node
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
A Finch OG Agent cell as an MCP server: read the world, dry-run and take ERC-8414 tenders by policy.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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:
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.
Each tool is a subcommand taking one JSON argument string (get_access_status takes none):
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_status npx @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.
npx -y @reneturcios/docketwatch mcp
MCP client config:
{
"mcpServers": { "docketwatch": { "command": "npx", "args": ["-y", "@reneturcios/docketwatch", "mcp"], "env": { "REGULATIONS_GOV_API_KEY": " " } } } }
docker run -i -e REGULATIONS_GOV_API_KEY="<your key>" ghcr.io/cloudcorprecords/docketwatch
docker run --rm -e REGULATIONS_GOV_API_KEY=" " ghcr.io/cloudcorprecords/docketwatch get_access_status
npm install
npm 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
MIT — Copyright (c) 2026 Rene Turcios