cfr-free
Related Servers
Alternatives to cfr-free
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables 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.782 PyPI1MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code to perform local hybrid search over crawled web pages and personal PDF, Markdown, HTML, and text documents, returning cited passages with source, section, page, and score details. It also exposes tools to list documents, retrieve full document text, and check index status.1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access US FDA regulations (21 CFR) through natural language queries, providing tools for retrieving regulatory information.90 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables agents to search a local, fully offline personal document library (Markdown/txt/PDF/docx) via SQLite FTS5 trigram search with subject-terminology expansion, returning every hit with its domain, document title, section path, and page or offset provenance. It also exposes domain statistics, incremental ingestion, and document deprecation as tools, alongside a read-only, runtime-persona-scoped ask/coverage mode.-
- 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
- AlicenseNot gradedqualityBmaintenanceGives AI agents fast, read-only access to a local knowledge base of Markdown notes and other text documents via a SQLite full-text index. Enables ranked section-level search, reading whole notes or single sections, heading outlines, note listing, and link/backlink navigation without slow disk walks.Apache 2.0
TDQS
Scored across 9 tools
The core research verbs (search_regulations, get_section, get_section_at, diff_issues, redline) are cleanly separated by resource and time dimension. Two pairs blur slightly: health vs index_status both report staleness/readiness, and list_parts vs browse_title38 both serve part/hierarchy discovery, though the descriptions do draw a one-call-gate vs detail distinction.
Seven of nine names follow verb_noun (search_regulations, get_section, browse_title38, list_parts, diff_issues, etc.), but 'health' and 'redline' are bare nouns with no verb, and scope suffixes are inconsistent (_title38 vs _regulations). Readable, but not a single predictable pattern.
Nine tools is squarely in the well-scoped range for a legal-research server, and each maps to a distinct capability: status gating, discovery, search, current read, point-in-time read, diff, and redline.
The surface covers discovery, full-text search, full-text retrieval, historical point-in-time reads, and both title-level and provision-level change tracking, with no obvious dead ends for a read-only Title 38 domain. Minor gaps remain, such as no flat section listing within a part or bulk part export, but agents can work around these via browse_title38 and get_section.