License Verify MCP vs Loppee
A side-by-side look at the License Verify MCP and Loppee 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 Loppee for legal over a hosted endpoint. 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.
Choose Loppee when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
lookup_business, get_trust_card, get_business_reviews.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 57/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| 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 | 0 |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | 5 |
| Full listing | View License Verify MCP | View Loppee |
Tools & capabilities
License Verify MCP tools 3
jurisdictionlicense_numberbusiness_name
Loppee tools 5
lookup_businessUse this when the user names a business and wants its Loppee Registry match. Returns exact and genuine-prefix name matches with stable ids, coarse public city/state, and truthful Verified, Listed, or Registry disclosure. It does not perform category discovery, accept or return caller location, or return a street address or ZIP.get_trust_cardUse this when a business is already identified and the user wants its public Loppee Trust Card. Returns the exact business status, disclosure, coarse public city/state, public facts, review context, and citation without account authority, street address, ZIP, or signed media links.get_business_reviewsUse this when the user wants the public customer reviews for one Loppee business id. Supports pagination and star-rating filters, preserves reviewer and interaction labels, masks reviewer identity, and changes nothing.explain_recommendationUse this when the user asks why a known published business is or is not recommendable on Loppee. Returns the published class, disclosure, recommendation basis, commercial-neutrality statement, and citation without exposing private weighting.compare_businessesUse this when the user wants a side-by-side comparison of two to twenty known published Loppee business ids. Returns each business's exact class, disclosure, review context, and citation; unknown or unavailable ids are listed as unresolved rather than fabricated.
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
{
"mcpServers": {
"lmaniraruta-license-verify-mcp": {
"command": "npx",
"args": [
"-y",
"apify"
]
}
}
}
Loppee
{
"mcpServers": {
"loppee-3": {
"url": "https://loppee.com/mcp/discovery"
}
}
}
Frequently asked questions
License Verify MCP is categorized under Legal and uses a local stdio subprocess. Loppee belongs to Legal and uses a remote HTTP/SSE transport. Pick License Verify MCP for legal work and Loppee 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. Loppee 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 lmaniraruta-license-verify-mcp and loppee-3 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 57/100 (Good) with 5 views, 0 installs and 0 GitHub stars. Loppee has 56/100 (Good) with 0 views, 0 installs and 0 GitHub stars.