MCP Expert Witness Directory vs Enforcement Actions
A side-by-side look at the MCP Expert Witness Directory and Enforcement Actions MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Expert Witness Directory for legal work as a local process; 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 MCP Expert Witness Directory when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
APIFY_TOKEN.
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 | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 36/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | APIFY_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View MCP Expert Witness Directory | View Enforcement Actions |
Tools & capabilities
MCP Expert Witness Directory 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.
MCP Expert Witness Directory
{
"mcpServers": {
"mcp-expert-witness-directory": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-expert-witness-directory"
],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN_HERE"
}
}
}
}
Enforcement Actions
{
"mcpServers": {
"enforcement-actions": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-enforcement-actions"
]
}
}
}
Frequently asked questions
MCP Expert Witness Directory is categorized under Legal and uses a local stdio subprocess. Enforcement Actions belongs to Legal and uses a local stdio subprocess. Pick MCP Expert Witness Directory 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.
MCP Expert Witness Directory 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 mcp-expert-witness-directory and enforcement-actions as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Expert Witness Directory has a quality signal of 36/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.