A side-by-side look at the License Verify MCP and Sejm RP 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 Sejm RP 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 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.
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.
License Verify MCP is categorized under Legal and uses a local stdio subprocess. Sejm RP belongs to Legal and uses a local stdio subprocess. Pick License Verify MCP for legal work and Sejm RP 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.
License Verify MCP is listed as a paid service. Auth: no auth required. Sejm RP is listed as free. Auth: no auth required. 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 lmaniraruta-license-verify-mcp and sejm-rp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, License Verify MCP has a quality signal of 59/100 (Good) with 4 views, 0 installs and 0 GitHub stars. Sejm RP has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.