Skip to main content
Glama
Reid-n0rc

fcc-ecfs-mcp

by Reid-n0rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to fcc-ecfs-mcp

No user-submitted related servers found.

    Related Servers

    • federal-regulations-mcp-server

      cyanheads
      A
      license
      Not graded
      quality
      A
      maintenance
      Search and trace US federal rules across the Federal Register (proposed/final rules and notices), the eCFR (codified, point-in-time CFR full text, locally mirrored), and Regulations.gov (rulemaking dockets and public comments) via MCP.
      708 npm
      1
      Apache 2.0

    • mcp-data-fcc

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying and exploring FCC Open Data datasets via Socrata SoQL, including dataset search, metadata retrieval, and data querying.
      26 npm
      MIT

    • mcp-ferc-elibrary

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching the Federal Energy Regulatory Commission's public docket and document record, with full-text search across dockets and browsing of document class types, via a keyless JSON API.
      28 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: filing lookup, proceeding search, document metadata listing, document download, inbox listing, raw API escape hatch, and a specialized download-plan helper. The potential overlap between ecfs_search_filings and ecfs_get_download_plan is explicitly resolved in the description, and search_documents vs download_document are cleanly separated by metadata vs file retrieval.

    Naming Consistency4/5

    All tools share the ecfs_ prefix and snake_case formatting, and nearly all follow a verb_noun pattern (get_filing, search_proceedings, download_document). The main deviation is ecfs_raw_request, which is an adjective_noun phrase rather than a verb_noun action, but it remains readable and stylistically consistent.

    Tool Count5/5

    Eight tools is well-scoped for the FCC ECFS domain, covering search, retrieval, document handling, and an escape hatch without excessive surface area. Each tool appears to earn its place, and there is no sign of redundant or filler operations.

    Completeness4/5

    The core ECFS read workflows are covered: search/get filings, search proceedings, list/get document metadata, download documents, list inboxes, and raw API access. Minor gaps exist, such as a direct proceeding-detail lookup and inbox-specific filing retrieval, but the raw_request tool provides a workaround for uncovered API paths.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources