docket-mcp
Related Servers
Alternatives to docket-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables access to federal regulatory dockets, documents, and public comments from Regulations.gov via tools like get_docket and get_comment.410 npmMIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables interaction with the Regulations.gov API to search federal rulemaking dockets, proposed and final rules, public comments, and comment periods. Supports tracking FAR/DFARS case histories and monitoring open comment periods across federal agencies with optional API key authentication for higher rate limits.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search and track US federal regulations, documents, and executive orders from the Federal Register, with no API keys required.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to search and retrieve executive orders, presidential documents, rules, and agency information from the Federal Register API through natural language queries.1264 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables querying the US Federal Register API for federal register documents and data through natural language.241 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to access US FDA regulations (21 CFR) through natural language queries, providing tools for retrieving regulatory information.216 npmMIT
TDQS
Scored across 4 tools
Each tool has a distinct role: ping is health-only, search_dockets is the fuzzy query entry point, get_docket is exact-ID detail lookup, and list_documents returns child documents. The descriptions explicitly cross-reference IDs, so an agent should not confuse which tool to call.
The three data tools follow a clean verb_noun snake_case pattern: search_dockets, get_docket, list_documents. ping is a conventional health-check exception, but it is the only minor deviation and does not create confusion.
Four tools are well-scoped for a docket-browsing server: health check, search, detail lookup, and document listing. There is no redundancy, and the count fits comfortably within an appropriate MCP server size.
The core docket workflow is covered end-to-end: search dockets, fetch full docket details, and list the documents within a docket. The main gap is the absence of a per-document detail/search tool, so deeper document-level retrieval is not possible.