A side-by-side look at the License Verify MCP and OpenWorkProof MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose License Verify MCP for legal work as a local process; choose OpenWorkProof for legal as a local process. You can also run both side by side in one mcpServers block.
jurisdiction, license_number, business_name.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 59/100 · Good | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 287 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View License Verify MCP | View OpenWorkProof |
jurisdictionlicense_numberbusiness_nameNo tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"lmaniraruta-license-verify-mcp": {
"command": "npx",
"args": [
"-y",
"apify"
]
}
}
}
{
"mcpServers": {
"openworkproof": {
"command": "uvx",
"args": [
"openworkproof"
]
}
}
}