eCFR.io MCP server
Related Servers
Alternatives to eCFR.io MCP server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables searching, browsing, and retrieving current US Code of Federal Regulations text—including full-text search across all 50 titles, title structures, and exact section or part wording—via the official eCFR API.220 npmMIT
- AlicenseAqualityAmaintenanceEnables AI assistants to retrieve, search, and track changes to US Code of Federal Regulations sections via the eCFR API, returning actual regulation text with citations and point-in-time date support.71MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying the US Federal Register API for federal register documents and data through natural language.186 npmMIT
- 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
- AlicenseNot gradedqualityDmaintenanceProvides access to 529,000+ US statute sections across all 50 states and federal codes for comprehensive legal research. Supports semantic search, citation graph traversal, jurisdictional comparisons, and regulatory risk analysis through natural language queries.37 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to access US FDA regulations (21 CFR) through natural language queries, providing tools for retrieving regulatory information.2 npmMIT
TDQS
Scored across 3 tools
Each tool targets a distinct action: search_regulations finds matching text, get_regulation retrieves full text by canonical path, and list_titles enumerates CFR titles. The descriptions clearly differentiate the retrieval-by-path use of get_regulation from the lookup nature of search_regulations. No overlapping purpose remains.
All three names follow a clear verb_noun pattern (search_regulations, get_regulation, list_titles). The minor singular/plural variation follows natural English usage and does not reduce predictability. The convention is consistent throughout.
Three tools cover the core read-only workflows of search, retrieval, and browsing. The set is well-scoped with no redundancy, though it is on the minimal side for a regulatory API. Each tool earns its place.
The surface supports search, full-text retrieval by path, and title listing, with pagination via nextOffset on get_regulation. Minor gaps include no dedicated way to list all sections within a title without traversing child links, but core regulatory lookup is covered. Read-only scope aligns with an eCFR mirror.