sec_enforcement_actions

Pack: enforcement-actions · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/sec_enforcement_actions for the schema, then POST the same URL with its arguments for the data.

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.

Parameters

Example call

Arguments

{
  "type": "litigation"
}

curl

curl -X POST https://gateway.pipeworx.io/enforcement-actions/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"sec_enforcement_actions","arguments":{"type":"litigation"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('sec_enforcement_actions', {
  "type": "litigation"
});

More examples

{
  "type": "administrative",
  "limit": 10
}

{
  "type": "trading_suspension"
}

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}

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

See Getting Started for client-specific install steps.