
Fcc Regulations MCP server
online · 100% uptimeFCC Regulations MCP — US Federal Communications Commission rules (47 CFR).
not scanned yet
1 stars
Reviews
Write oneNobody has reviewed Fcc Regulations yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Fcc Regulations tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Fcc Regulations compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 100 ms
- faster than 84% of 30,031 servers
- GitHub stars
- 1
- more than 65% of 28,688 servers
Release history: 4 versions in the registry since 2026-07-26, latest 2026-11-01, typically one every 34 days.
Install Fcc Regulations in Claude Code, Cursor or VS Code
claude mcp add --transport http fcc-regulations https://gateway.pipeworx.io/fcc-regulations/mcp
What the publisher says
From the Fcc Regulations repository's README, as published. We do not edit it. Read it on GitHub
mcp-fcc-regulations
FCC Regulations MCP — US Federal Communications Commission rules (47 CFR).
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tools
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"fcc-regulations": {
"url": "https://gateway.pipeworx.io/fcc-regulations/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/fcc-regulations/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Fcc Regulations: common questions
- Is Fcc Regulations MCP server safe?
- Mostly: it is graded B (77/100). Read the Fcc Regulations safety report
- How do I install Fcc Regulations?
- It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Fcc Regulations need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Fcc Regulations maintained?
- The last commit was 47 days ago (2026-09-18). The latest release is v0.2.1.
- Is Fcc Regulations up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Fcc Regulations compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 100 ms (faster than 84% of 30,031 servers). Full comparison.