ClauseKeeper Compliance Scanner vs License Verify MCP
A side-by-side look at the ClauseKeeper Compliance Scanner and License Verify MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose ClauseKeeper Compliance Scanner for legal work; choose License Verify MCP 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 ClauseKeeper Compliance Scanner when
- You need dedicated capabilities in the Legal domain.
Choose License Verify MCP when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
jurisdiction, license_number, business_name.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 29/100 · Emerging | 57/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Paid service |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View ClauseKeeper Compliance Scanner | View License Verify MCP |
Tools & capabilities
ClauseKeeper Compliance Scanner tools
No tool names declared yet. Check the project README from the listing page.
License Verify MCP tools 3
jurisdictionlicense_numberbusiness_name
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.
ClauseKeeper Compliance Scanner
No confirmed install command for ClauseKeeper Compliance Scanner yet — follow the setup steps linked from its listing page rather than a guessed package name.
License Verify MCP
{
"mcpServers": {
"lmaniraruta-license-verify-mcp": {
"command": "npx",
"args": [
"-y",
"apify"
]
}
}
}