Skip to main content
Glama
eCFR.io MCP server

eCFR.io MCP server

by lrehmann

Related Servers

Alternatives to eCFR.io MCP server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      197 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      7
      49 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching and retrieving U.S. Federal Register documents — final and proposed rules, notices, executive orders, and public inspection filings — plus facet counts, agency listings, open comment deadlines, and FAR/DFARS case histories, through eight tools backed by the keyless public API v1.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables searching and reading federal statutes with linked legal and inline citations, listing published titles, and retrieving complete sections with bounded pagination through hosted HTTP or local stdio.
      3
      MIT

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues