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.
      98 npm
      1
      Apache 2.0

    • mcp-data-fcc

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

    • mcp-ferc-elibrary

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      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.
      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.9/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct action and resource: searching filings, retrieving a filing, searching proceedings, planning exhaustive downloads, listing documents, listing inboxes, or making raw API calls. The only potentially overlapping pair (ecfs_search_filings vs ecfs_get_download_plan) is clearly differentiated by the download plan's explicit purpose of returning date-bucketed query plans rather than results.

    Naming Consistency5/5

    All tool names share the consistent 'ecfs_' prefix followed by a clear verb_noun structure: search_filings, get_filing, search_proceedings, get_download_plan, search_documents, list_inboxes, raw_request. The verbs (search/get/list) are standard and applied appropriately to each operation, making the naming pattern predictable and easily parseable.

    Tool Count5/5

    With exactly 7 tools, the server is compactly scoped to the FCC ECFS public API domain—covering the main search/retrieval workflows without unnecessary bloat. Each tool serves a clear purpose, and the addition of an escape hatch (ecfs_raw_request) keeps the surface lean while ensuring full API coverage.

    Completeness5/5

    The tool set covers the core workflows for the domain: searching and retrieving filings, exploring proceedings, managing large result sets with a download plan, listing document metadata, and accessing inboxes. The ecfs_raw_request tool acts as a catch-all for any uncovered API endpoints, so the surface has no obvious dead ends for public read-only ECFS queries.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources