Enforcement Actions MCP server

@pipeworx/enforcement-actions

US federal enforcement actions from primary sources — DOJ prosecutions and settlements, SEC litigation releases, administrative proceedings and trading suspensions. The branded entry point for "what has the government brought against COMPANY".

Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.

Tools

(~270,000 back to 2009) by company, person or topic. Newest first, dated, linked, with the DOJ components involved.

• enforcement_search({ query, limit?, since? }) — search DOJ press releases

merged newest-first. source = all | doj | sec.

• enforcement_recent({ source?, limit? }) — recent actions across DOJ and SEC,

(civil actions in federal court), administrative (before an ALJ or the Commission), trading_suspension.

• secenforcementactions({ type?, limit? }) — SEC by type: litigation

Auth

Keyless. Both upstreams are public.

Data sources

sibling administrative-proceedings/rss and trading-suspensions/rss feeds.

• — DOJ press releases.
• — and the

Things worth not rediscovering

The DOJ API silently ignores most of its plausible parameters. Measured 2026-08-05 against the live API:

An ignored filter returning 200 with every record looks like "nothing was excluded", not like "your filter did nothing". None of the ignored parameters are exposed by this pack; since is applied client-side after fetching, and says so in its description.

Search matches the TITLE only. A company named in the body of a release but not in the headline will not be found. enforcement_search says so in its finding when a query returns nothing, and suggests the short form of the name.

One action, many announcements. DOJ routinely publishes the same case from Public Affairs and the relevant US Attorney's office — "Binance and CEO Plead Guilty" returns twice. Results are collapsed on title+date, with the extra URLs kept under alsoannouncedby.

A few DOJ records have malformed dates (raw HTML in the date field), so date parsing is defensive and returns null rather than a garbage timestamp.

SEC feeds are a recent window, not an archive (~25 items each) and are not searchable. Any "has the SEC ever sued X" question is out of scope for this pack; only DOJ has history here.

Not included in v1

FTC. No structured feed survives. Probed live 2026-08-05, all failing:

Including FTC would mean scraping its Drupal listing pages, which is a separate decision rather than a keyless-first integration.

State attorneys general. No common format; each state publishes its own press page. Would be one pack per jurisdiction under the standing rule, not a multiplexed state argument.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "enforcement-actions": {
      "url": "https://gateway.pipeworx.io/enforcement-actions/mcp"
    }
  }
}

What this endpoint actually serves

Shortened. The full README is on GitHub.