Enforcement Actions vs RegAffairs AI
A side-by-side look at the Enforcement Actions and RegAffairs AI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
R
RegAffairs AILegal · Remote HTTP/SSECited answers on chemical, food, pharma, device, cosmetic and pesticide rules, linked to sources.43FairAuth: no auth requiredVerdict: choose Enforcement Actions for legal work as a local process; choose RegAffairs AI for legal over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Enforcement Actions when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- You want tools like
enforcement_search, enforcement_recent, sec_enforcement_actions.
RChoose RegAffairs AI when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | R RegAffairs AI | |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 53/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Enforcement Actions | View RegAffairs AI |
Tools & capabilities
Enforcement Actions tools 3
enforcement_searchSearch 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.enforcement_recentRecent 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.sec_enforcement_actionsSEC 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.
RegAffairs AI tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Enforcement Actions
{
"mcpServers": {
"enforcement-actions": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-enforcement-actions"
]
}
}
}
RegAffairs AI
{
"mcpServers": {
"regaffairs-ai": {
"url": "https://regaffairsai.com/docs/mcp"
}
}
}
Frequently asked questions
Enforcement Actions is categorized under Legal and uses a local stdio subprocess. RegAffairs AI belongs to Legal and uses a remote HTTP/SSE transport. Pick Enforcement Actions for legal work and RegAffairs AI for legal.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Enforcement Actions has no declared pricing — check the project's own site. RegAffairs AI has no declared pricing — check the project's own site. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add enforcement-actions and regaffairs-ai as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Enforcement Actions has a quality signal of 53/100 (Good) with 1 views, 0 installs and 0 GitHub stars. RegAffairs AI has 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.