Site vs Enforcement Actions
A side-by-side look at the Site and Enforcement Actions MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SiteLegalMiCA Requirements: the site's own MCP server — checker, enquiry (enquiry = a human handoff, not...37FairAuth: not declaredVerdict: choose Site for legal work; choose Enforcement Actions for legal as a local process. 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
source, all, doj.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Site | |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 37/100 · Fair | 49/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Site | View Enforcement Actions |
Tools & capabilities
Site tools
No tool names declared yet. Check the project README from the listing page.
Enforcement Actions tools 5
sourcealldojseclitigation
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.
Site
No confirmed install command for Site yet — follow the setup steps linked from its listing page rather than a guessed package name.
Enforcement Actions
{
"mcpServers": {
"enforcement-actions": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-enforcement-actions"
]
}
}
}
Frequently asked questions
Site is categorized under Legal and uses an install path we have not confirmed yet. Enforcement Actions belongs to Legal and uses a local stdio subprocess. Pick Site for legal work and Enforcement Actions 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. Site has no confirmed install command yet — follow its own setup instructions.
Site has no declared pricing — check the project's own site. Enforcement Actions has no declared pricing — check the project's own site. 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 site-176 and enforcement-actions as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Site has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Enforcement Actions has 49/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.