@pipeworx/mcp-fcc-ecfs
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 1 of 2 tools tried
Contacts while installing and starting: gateway.pipeworx.io
What it contacted
gateway.pipeworx.io
Hosts it looked up or connected to while installing and starting with no input, watched from outside its sandbox. The npm registry is left out. Says nothing about what its tools contact when called.
Starting it
npx -y @pipeworx/mcp-fcc-ecfs@0.2.1
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
2 tools that take no input and look read-only were called once with nothing. 1 returned a result.
ecfs_search_filings | No usable answer tool reported an error: {"error":"tool_error","message":"supply query (full-text search) or filer (company name) or both","retry_hint":"Retry the same tool with |
ecfs_search_proceedings | Returned a result 0.7 s · 6,422 characters |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
ecfs_search_filings query, filer, limit, offset, _apiKey
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.
ecfs_docket_filings proceeding, limit, offset, _apiKey
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.
ecfs_filing_detail submission_id, _apiKey
Retrieve one FCC ECFS filing by submission ID with all public proceedings, filers, authors, law firms, status, and official document/attachment URLs.
ecfs_search_proceedings proceeding, query, limit, offset, _apiKey
Search FCC ECFS proceedings/dockets by exact number or public API query and return descriptions, bureau, dates, and docket links.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=18 |
| Source | github.com/pipeworx-io/mcp-fcc-ecfs |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-K9JrWpNHOWwc7xIO7Gou5bUw1pUJr/Ce7oxMiuvXTCIcH/+autncgzwDhRsPNbtdaoCXlrm3Dc6Loy/9e6Nm5A== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40pipeworx/mcp-fcc-ecfs)
New version out? Ask for a fresh report.