Ftc Enforcement
NPM · @PIPEWORX/MCP-FTC-ENFORCEMENT · 2 COMPONENTS
FTC Enforcement MCP — FTC cases, orders, and merger/non-merger enforcement.
Available components
Last scanned (5 hours ago)
Scores higher than 72% of npm servers
Category Security
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-ftc-enforcement). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-ftc-enforcement@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-ftc-enforcement |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-ftc-enforcement/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637319941 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:17b93b4e10776e8acdd82bc0689ff3a4d4bff29893fa4cecc21356d4649b8af689d56e0e4fa7df306edf7f33358fba0a09e2463ec55460c2a1a700939 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ftc_case_detail ~188
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" }).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The case's ftc.gov slug (last URL path segment), or the full cases-proceedings URL — either is accepted. |
No output schema declared.
No examples provided.
ftc_recent_actions ~178
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 }).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
ftc_search_cases ~284
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" }).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-ftc-enforcement
claude mcp add pipeworx-io-ftc-enforcement -- npx -y @pipeworx/mcp-ftc-enforcement
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.