# Enforcement Actions (npm · @pipeworx/mcp-enforcement-actions)

US federal enforcement actions MCP. Keyless.

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-enforcement-actions`
- 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-enforcement-actions).
  - 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**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 563 tokens (~187/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 Enforcement Actions MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-05 (score 83, +1)

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

### 2026-11-03 (score 82, +1)

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

### 2026-11-02 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

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

- [security regression] Tool safety: pass → unverified
- [security regression] Malware scan: 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 improvement] Stability: unverified → 0.10
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

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

First indexed and scored.

## MCP tools (3)

### `enforcement_search` (~228 tokens)

Search US federal enforcement actions against a company, person or topic by name — DOJ criminal charges, guilty pleas, settlements, indictments and civil resolutions. Answers 'what has DOJ charged Binance with', 'enforcement actions against Purdue Pharma', 'DOJ settlement opioid', 'who was indicted for FTX'. Returns dated actions newest-first with a link to the official release, the DOJ components involved (e.g. Antitrust Division, Criminal Division) and a summary. Searches DOJ press releases (~270,000 back to 2009) — the SEC feeds are recent-window only and are NOT searchable, so use enforcement_recent for those.

Input parameters:

- `limit` (number): How many actions to return, 1–50 (default 20), newest first.
- `query` (string, required): Company, person or topic name, e.g. "Binance", "Purdue", "opioid", "price fixing". Matched against the release TITLE.
- `since` (string): Only actions on or after this date (YYYY-MM-DD). Applied after fetching, since the DOJ API ignores date filters.

### `enforcement_recent` (~140 tokens)

Recent US federal enforcement actions across DOJ and the SEC, newest first — the 'what has been brought lately' view. Answers 'recent SEC enforcement actions', 'latest DOJ prosecutions', 'new securities fraud cases this week'. Merges DOJ press releases with SEC litigation releases, administrative proceedings and trading suspensions, each item dated and linked to the official source. Use enforcement_search to look up a specific company or topic by name.

Input parameters:

- `limit` (number): How many actions to return, 1–100 (default 25).
- `source` (string): Limit to one agency: "doj", "sec", or "all" (default).

### `sec_enforcement_actions` (~142 tokens)

SEC enforcement actions by type: litigation releases (civil actions filed in federal court), administrative proceedings (in-house actions before an ALJ or the Commission), or trading suspensions. Answers 'recent SEC litigation releases', 'SEC administrative proceedings', 'what trading suspensions has the SEC issued'. The distinction matters — an administrative proceeding is not a federal-court lawsuit. Returns dated items with links. Covers only the current feed window (about 25 items per type), not history.

Input parameters:

- `limit` (number): How many items to return, 1–25 (default 25).
- `type` (string): Which SEC action type to return (default litigation).

## Diagnostics

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

## Score history

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

## Common questions

### What is the Enforcement Actions MCP server?

Enforcement Actions is an MCP server listed in the public MCP registry as io.github.pipeworx-io/enforcement-actions. US federal enforcement actions MCP. Keyless. This page covers its npm package (@pipeworx/mcp-enforcement-actions).

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

Enforcement Actions scores 83 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 Enforcement Actions MCP server expose?

Enforcement Actions exposes 3 tools: enforcement_search, enforcement_recent, sec_enforcement_actions. Their descriptions and schemas cost roughly 510 tokens of context every time the server is loaded.

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

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

Enforcement Actions declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Enforcement Actions MCP server?

VerifyMCP ran 16 checks on Enforcement Actions, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-enforcement-actions
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-enforcement-actions
- Repository: https://github.com/pipeworx-io/mcp-enforcement-actions
- Website: https://pipeworx.io/packs/enforcement-actions
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-enforcement-actions/pipeworx-mcp-enforcement-actions.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-enforcement-actions/pipeworx-mcp-enforcement-actions/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-enforcement-actions/pipeworx-mcp-enforcement-actions.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-enforcement-actions/pipeworx-mcp-enforcement-actions