# Fcc Ecfs (npm · @pipeworx/mcp-fcc-ecfs)

FCC Electronic Comment Filing System public search and retrieval.

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-fcc-ecfs/fcc-ecfs-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-fcc-ecfs/fcc-ecfs-mcp)
- npm · `@pipeworx/mcp-fcc-ecfs`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-fcc-ecfs/pipeworx-mcp-fcc-ecfs.md), [page](https://verifymcp.io/servers/pipeworx-io-fcc-ecfs/pipeworx-mcp-fcc-ecfs)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-fcc-ecfs`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-fcc-ecfs).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 533 tokens (~133/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 69% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Fcc Ecfs MCP server?

Fcc Ecfs runs locally as an npm package, launched with npx -y @pipeworx/mcp-fcc-ecfs. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-fcc-ecfs -- npx -y @pipeworx/mcp-fcc-ecfs
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-fcc-ecfs": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-fcc-ecfs"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-fcc-ecfs": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-fcc-ecfs"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-fcc-ecfs -- npx -y @pipeworx/mcp-fcc-ecfs
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-fcc-ecfs": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-fcc-ecfs"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-fcc-ecfs --command npx --arg -y --arg @pipeworx/mcp-fcc-ecfs
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-fcc-ecfs:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-fcc-ecfs"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-fcc-ecfs": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-fcc-ecfs"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-fcc-ecfs -t stdio -c npx -a -y @pipeworx/mcp-fcc-ecfs
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-fcc-ecfs": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-fcc-ecfs"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 81, +2)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (4)

### `ecfs_search_filings` (~201 tokens)

Search FCC ECFS filings using the public API. Use filer to list filings submitted BY a specific company (exact name match); use query for full-text search across all filings. Returns filer/author, proceeding, submission type, dates, and official document links. Search matches are filings in the public record, not FCC findings or endorsements.

Input parameters:

- `_apiKey` (string): Optional api.data.gov key for higher limits; defaults to DEMO_KEY.
- `filer` (string): Filter to filings submitted BY this exact company or person name (e.g. "T-Mobile USA, Inc."). Use instead of query when searching for a specific filer's submissions.
- `limit` (number): Results (1-100, default 25).
- `offset` (number): Pagination offset (default 0).
- `query` (string): Full-text search across all ECFS filings — matches ANY mention of the term, not just filings BY that party.

Output parameters:

- `filings` (array)
- `returned` (number)
- `source` (string)

### `ecfs_docket_filings` (~105 tokens)

List FCC ECFS filings in an exact proceeding/docket, newest first, including documents and parties. A filing reflects the submitter’s position and is not an FCC decision.

Input parameters:

- `_apiKey` (string): Optional api.data.gov key for higher limits; defaults to DEMO_KEY.
- `limit` (number)
- `offset` (number)
- `proceeding` (string, required): Exact docket/proceeding number, e.g. 11-42.

Output parameters:

- `filings` (array)
- `returned` (number)
- `source` (string)

### `ecfs_filing_detail` (~73 tokens)

Retrieve one FCC ECFS filing by submission ID with all public proceedings, filers, authors, law firms, status, and official document/attachment URLs.

Input parameters:

- `_apiKey` (string): Optional api.data.gov key for higher limits; defaults to DEMO_KEY.
- `submission_id` (string, required)

Output parameters:

- `documents` (array)
- `proceedings` (array)
- `source_url` (string)
- `submission_id` (string)

### `ecfs_search_proceedings` (~96 tokens)

Search FCC ECFS proceedings/dockets by exact number or public API query and return descriptions, bureau, dates, and docket links.

Input parameters:

- `_apiKey` (string): Optional api.data.gov key for higher limits; defaults to DEMO_KEY.
- `limit` (number)
- `offset` (number)
- `proceeding` (string): Exact proceeding number.
- `query` (string): Optional proceeding search text.

Output parameters:

- `proceedings` (array)
- `returned` (number)
- `source` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-fcc-ecfs/pipeworx-mcp-fcc-ecfs#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Fcc Ecfs MCP server?

Fcc Ecfs is an MCP server listed in the public MCP registry as io.github.pipeworx-io/fcc-ecfs. FCC Electronic Comment Filing System public search and retrieval. This page covers its npm package (@pipeworx/mcp-fcc-ecfs).

### Is the Fcc Ecfs MCP server safe to use?

Fcc Ecfs scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Fcc Ecfs MCP server expose?

Fcc Ecfs exposes 4 tools: ecfs_search_filings, ecfs_docket_filings, ecfs_filing_detail, ecfs_search_proceedings. Their descriptions and schemas cost roughly 475 tokens of context every time the server is loaded.

### Is the Fcc Ecfs MCP server still maintained?

Fcc Ecfs is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Fcc Ecfs MCP server under?

Fcc Ecfs declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-fcc-ecfs
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-fcc-ecfs
- Repository: https://github.com/pipeworx-io/mcp-fcc-ecfs
- Website: https://pipeworx.io/packs/fcc-ecfs
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-fcc-ecfs/pipeworx-mcp-fcc-ecfs.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-fcc-ecfs/pipeworx-mcp-fcc-ecfs.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-fcc-ecfs/pipeworx-mcp-fcc-ecfs