Enforcement Actions vs Licenscheck
A side-by-side look at the Enforcement Actions and Licenscheck MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
L
LicenscheckLegalVerify US contractor licenses across states: Clear, Review or Risk, with the reasons.37FairAuth: not declaredVerdict: choose Enforcement Actions for legal work as a local process; choose Licenscheck for legal. 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 | L Licenscheck | |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 49/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| 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 | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Enforcement Actions | View Licenscheck |
Tools & capabilities
Enforcement Actions tools 5
sourcealldojseclitigation
Licenscheck 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"
]
}
}
}
Licenscheck
No confirmed install command for Licenscheck yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Enforcement Actions is categorized under Legal and uses a local stdio subprocess. Licenscheck belongs to Legal and uses an install path we have not confirmed yet. Pick Enforcement Actions for legal work and Licenscheck 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. Licenscheck has no confirmed install command yet — follow its own setup instructions.
Enforcement Actions has no declared pricing — check the project's own site. Licenscheck 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 enforcement-actions and licenscheck 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 49/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Licenscheck has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.