Enforcement Actions
NPM · @PIPEWORX/MCP-ENFORCEMENT-ACTIONS · 2 COMPONENTS
US federal enforcement actions MCP. Keyless.
Available components
Last scanned (1 hour ago)
Scores higher than 76% of npm servers
Category Search and Retrieval
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-enforcement-actions). 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 Usability67
- AI-judged instruction clarity (good).Pass
- 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. 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.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 2 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Nov 26 −13
- Tool safety: pass → unverified ▼ security
- 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. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 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-enforcement-actions@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-enforcement-actions |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-enforcement-actions/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635921057 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e69c2eabf2128729dd963d662159ea584832259ca36cf8f299e6c3a057b1e1568984519d7c166016c156b76964e5a1267ba0028eb87fad0fbca9a74cd |
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 →
enforcement_recent ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many actions to return, 1–100 (default 25). |
| source | string | – | Limit to one agency: "doj", "sec", or "all" (default). |
No output schema declared.
No examples provided.
enforcement_search ~228
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many actions to return, 1–50 (default 20), newest first. |
| query | string | yes | 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. |
No output schema declared.
No examples provided.
sec_enforcement_actions ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many items to return, 1–25 (default 25). |
| type | string | – | Which SEC action type to return (default litigation). |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-enforcement-actions
claude mcp add pipeworx-io-enforcement-actions -- npx -y @pipeworx/mcp-enforcement-actions
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.