ecfr-mcp
Related Servers
Alternatives to ecfr-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceA production-quality MCP server that exposes the official eCFR API as structured tools for AI-driven contract compliance, enabling retrieval of relevant Code of Federal Regulations by clauses extracted from contracts.8-
- 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.19 npmMIT
- AlicenseAqualityBmaintenanceEnables searching and reading the US Code of Federal Regulations through tools that return excerpts, full text, legal citations, and linked source URLs, with read-only, stateless access.3MIT
- FlicenseNot gradedqualityAmaintenanceFind federal contract opportunities, research awards and vendors, and review exclusion evidence with linked official sources. Public research is free and needs no account.-
- AlicenseAqualityAmaintenanceThe most comprehensive keyless federal-data MCP server. 36 tools for SAM.gov + USAspending + Federal Register + eCFR + Grants.gov. No API key, no registration, no signup. Works in Claude Desktop, Claude Code, Codex CLI, Cursor, Continue, Gemini CLI, and any MCP-aware host.153163 npm13MIT
- FlicenseNot gradedqualityDmaintenanceFederal procurement intelligence toolkit that searches SAM.gov contract opportunities, analyzes agency spending patterns, tracks competitor wins, and monitors small business set-aside programs (8a, HUBZone, SDVOSB, WOSB). 4 tools using SAM.gov and USASpending.gov data.3-
TDQS
Scored across 13 tools
Most tools target distinct actions: search, structure, ancestry, version history, recent changes, definitions, corrections, and agency lookup are clearly differentiated. The main overlap is get_cfr_content versus lookup_far_clause, since both retrieve current section/clause text, though lookup_far_clause is framed as a convenience wrapper and the descriptions help distinguish them.
All tool names use snake_case and generally follow an action_scope pattern such as get_cfr_content, get_version_history, list_sections_in_part, find_recent_changes, and compare_versions. The verbs vary by purpose but remain predictable and there is no mixing of naming conventions.
With 13 tools, the server is well-scoped for a read-only CFR/FAR research domain. Each tool covers a meaningful operation such as content retrieval, search, hierarchy, version history, corrections, or agency metadata, without obvious filler.
The surface covers the core needs of CFR research: content retrieval, search, definitions, structure, ancestry, version history, recent changes, corrections, agency mapping, and version comparison. Minor gaps remain, such as no explicit title-listing or broader metadata tool, but the main regulatory workflows are well supported.