# Fcc Regulations (npm · @pipeworx/mcp-fcc-regulations)

FCC Regulations MCP — US Federal Communications Commission rules (47 CFR).

- Trust score: 81/100 (high trust)
- Change this week: +3
- 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-regulations/fcc-regulations-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-fcc-regulations/fcc-regulations-mcp)
- npm · `@pipeworx/mcp-fcc-regulations`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-fcc-regulations/pipeworx-mcp-fcc-regulations.md), [page](https://verifymcp.io/servers/pipeworx-io-fcc-regulations/pipeworx-mcp-fcc-regulations)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-fcc-regulations`
- 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-regulations).
  - 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**: 58/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 772 tokens (~386/item across 2 items; 2 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**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 Regulations MCP server?

Fcc Regulations runs locally as an npm package, launched with npx -y @pipeworx/mcp-fcc-regulations. 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-regulations -- npx -y @pipeworx/mcp-fcc-regulations
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-04 (score 81, +1)

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

### 2026-11-02 (score 80, +1)

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

### 2026-11-01 (score 79, +1)

- [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] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Security disclosure: fail → 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 78, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (2)

### `fcc_regulation` (~433 tokens)

Get the full text of one FCC regulation — a US Federal Communications Commission rule codified in 47 CFR — by its citation. Returns the exact regulatory wording currently in force. Answers "what does 47 CFR 15 require", "what is the FCC rule for X", "does the FCC allow X", "read 47 CFR 15.247", "the FCC RF emissions limit". Forgiving citation input: "15.109", "47 CFR 15.109", "§15.247", "15.247(b)" (paragraph stripped to the section), "Part 97". Covers telecommunications regulation across all of Title 47: Part 15 unlicensed devices and RF emissions limits, Part 97 amateur radio, Part 2 equipment authorization and frequency allocations, Part 73 broadcast radio and TV, Part 76 cable, Part 25 satellite, Parts 24/27 wireless and spectrum, Part 64 common carrier and telephone rules, Part 11 emergency alert system, Part 9 911. Also accepts common names: "amateur radio", "unlicensed devices", "equipment authorization", "RF exposure limits". Pass a whole part (e.g. "15" or "Part 97") to get that part's section list. Example: fcc_regulation({ citation: "15.109" }) -> radiated emission limits; fcc_regulation({ citation: "97.301" }) -> amateur radio authorized frequency bands. Keyless. This pack is the FCC RULES text; the separate `fcc` and `data-fcc` packs serve FCC filings and licensing data (ULS licenses, ECFS comments, broadband maps).

Input parameters:

- `citation` (string, required): FCC rule citation. A section: "15.109", "47 CFR 15.109", "§15.247", "97.301", "15.247(b)". Or a whole part: "15", "Part 97" -> returns the part's section list. Common names also work: "amateur radio"…

### `fcc_regulations_search` (~283 tokens)

Keyword search across the FCC regulations — US telecommunications rules in 47 CFR. Answers "what FCC regulations cover X", "the FCC rule about X", "find the telecommunications regulation for X", "which radio / spectrum / wireless rule applies to X". Great for topics: unlicensed device emission limits, Part 15 intentional and unintentional radiators, RF exposure and radiofrequency radiation limits, equipment authorization and certification, amateur radio operating privileges, spectrum and frequency allocations, broadcast station licensing and ownership, cable and satellite carriage, robocalls and caller ID, 911 and emergency alerting, wireless and common carrier obligations. Returns matching FCC rules with citation (47 CFR), heading, excerpt, and source URL. Example: fcc_regulations_search({ query: "unlicensed device emission limits" }); fcc_regulations_search({ query: "amateur radio frequency bands", limit: 15 }). Keyless. Searches the FCC RULES text; the separate `fcc` and `data-fcc` packs search FCC filings and licensing data.

Input parameters:

- `limit` (number): Max results to return, 1-20 (default 10).
- `query` (string, required): Telecommunications-regulation topic or phrase, e.g. "unlicensed device emission limits", "RF exposure", "equipment authorization", "amateur radio frequency bands", "broadcast ownership".

## Diagnostics

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

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 79
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the Fcc Regulations MCP server?

Fcc Regulations is an MCP server listed in the public MCP registry as io.github.pipeworx-io/fcc-regulations. FCC Regulations MCP, US Federal Communications Commission rules (47 CFR). This page covers its npm package (@pipeworx/mcp-fcc-regulations).

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

Fcc Regulations scores 81 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 Regulations MCP server expose?

Fcc Regulations exposes 2 tools: fcc_regulation, fcc_regulations_search. Their descriptions and schemas cost roughly 716 tokens of context every time the server is loaded.

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

Fcc Regulations 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 Regulations MCP server under?

Fcc Regulations 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-regulations
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-fcc-regulations
- Repository: https://github.com/pipeworx-io/mcp-fcc-regulations
- Website: https://pipeworx.io/packs/fcc-regulations
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-fcc-regulations/pipeworx-mcp-fcc-regulations.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-fcc-regulations/pipeworx-mcp-fcc-regulations.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-fcc-regulations/pipeworx-mcp-fcc-regulations