# Ftc Enforcement (npm · @pipeworx/mcp-ftc-enforcement)

FTC Enforcement MCP — FTC cases, orders, and merger/non-merger enforcement.

- Trust score: 82/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-ftc-enforcement/ftc-enforcement-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-ftc-enforcement/ftc-enforcement-mcp)
- npm · `@pipeworx/mcp-ftc-enforcement`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-ftc-enforcement/pipeworx-mcp-ftc-enforcement.md), [page](https://verifymcp.io/servers/pipeworx-io-ftc-enforcement/pipeworx-mcp-ftc-enforcement)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-ftc-enforcement`
- 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-ftc-enforcement).
  - 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**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 706 tokens (~235/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Ftc Enforcement MCP server?

Ftc Enforcement runs locally as an npm package, launched with npx -y @pipeworx/mcp-ftc-enforcement. 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-ftc-enforcement -- npx -y @pipeworx/mcp-ftc-enforcement
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-ftc-enforcement -- npx -y @pipeworx/mcp-ftc-enforcement
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-ftc-enforcement --command npx --arg -y --arg @pipeworx/mcp-ftc-enforcement
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 82, +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-03 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 66, −13)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.13
- [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 (3)

### `ftc_search_cases` (~284 tokens)

Search FTC (Federal Trade Commission) enforcement cases and proceedings by company name, individual name, case/matter number, or keyword, with optional date range, merger-vs-non-merger filter, and case-status filter. Covers both competition (antitrust/merger) and consumer-protection enforcement — complaints, consent orders, settlements, and federal-court actions. Returns each matching case's title, FTC slug (pass to ftc_case_detail for documents), type of action, case status, and last-updated date. Example: ftc_search_cases({ query: "Kroger", category: "merger" }).

Input parameters:

- `category` (string): Restrict to merger enforcement, non-merger (conduct) enforcement, or both ("any", the default).
- `end_date` (string): Latest "last updated" date to include, YYYY-MM-DD.
- `limit` (number): Max cases to return, newest-updated first. Default 20, max 100.
- `query` (string): Company name, individual name, case/matter number, or keyword. Omit to browse all cases (combine with category/status/dates).
- `start_date` (string): Earliest "last updated" date to include, YYYY-MM-DD.
- `status` (string): Restrict to cases in this status. Omit for any status.

### `ftc_case_detail` (~188 tokens)

Get full detail for one FTC case or proceeding: case status (pending/closed/under order), federal court (if any), the full party caption, the case summary, any linked press release, and the complete document timeline (complaint, orders, settlements, briefs) each with its filing date, document title, and PDF URL. Takes the `slug` field returned by ftc_search_cases or ftc_recent_actions — the last path segment of the case's ftc.gov URL, e.g. "hims-hers" for https://www.ftc.gov/legal-library/browse/cases-proceedings/hims-hers. Example: ftc_case_detail({ slug: "hims-hers" }).

Input parameters:

- `slug` (string, required): The case's ftc.gov slug (last URL path segment), or the full cases-proceedings URL — either is accepted.

### `ftc_recent_actions` (~178 tokens)

Get the most recent FTC enforcement actions (cases and proceedings), newest first — new complaints, settlements, and orders across both competition and consumer-protection enforcement. Optionally restrict to merger enforcement only or non-merger (conduct) enforcement only. Answers "what has the FTC done recently" / "what merger actions has the FTC taken this month." Example: ftc_recent_actions({ days: 30, category: "merger", limit: 10 }).

Input parameters:

- `category` (string): Restrict to merger enforcement, non-merger (conduct) enforcement, or both ("any", the default).
- `days` (number): How many days back from today to look, by last-updated date. Default 30.
- `limit` (number): Max actions to return, newest first. Default 20, max 100.

## Diagnostics

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

## Score history

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

## Common questions

### What is the Ftc Enforcement MCP server?

Ftc Enforcement is an MCP server listed in the public MCP registry as io.github.pipeworx-io/ftc-enforcement. FTC Enforcement MCP, FTC cases, orders, and merger/non-merger enforcement. This page covers its npm package (@pipeworx/mcp-ftc-enforcement).

### Is the Ftc Enforcement MCP server safe to use?

Ftc Enforcement scores 82 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 Ftc Enforcement MCP server expose?

Ftc Enforcement exposes 3 tools: ftc_search_cases, ftc_case_detail, ftc_recent_actions. Their descriptions and schemas cost roughly 650 tokens of context every time the server is loaded.

### Is the Ftc Enforcement MCP server still maintained?

Ftc Enforcement 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 Ftc Enforcement MCP server under?

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