Skip to main content
Glama
Sign In
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.
      870 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.
      671 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.
      12 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

    Disambiguation4/5

    Most tools have clearly distinct purposes: filing lookup, document download, document listing, proceeding search, and inbox listing. Minor overlap comes from ecfs_raw_request being a universal escape hatch and from ecfs_get_download_plan sharing filters with ecfs_search_filings, though both descriptions clarify when to use them.

    Naming Consistency4/5

    All tools use a consistent ecfs_ snake_case prefix and mostly follow a verb_noun pattern such as ecfs_get_filing, ecfs_search_documents, and ecfs_list_inboxes. The main deviation is ecfs_raw_request, which is still readable but does not follow the same action-verb style.

    Tool Count5/5

    Eight tools is well within the expected range for a focused ECFS API server. Each tool covers a meaningful operation, and the set is not padded with redundant endpoints.

    Completeness5/5

    For a read-only ECFS research server, the surface covers the core lifecycle: searching proceedings, searching filings, fetching a filing, listing documents, downloading documents, and handling non-docketed inboxes. The raw request tool also provides an escape hatch for any uncovered API paths.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources