License Verify MCP vs Getting an API Key
A side-by-side look at the License Verify MCP and Getting an API Key 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 Getting an API Key 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.
Choose Getting an API Key when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
HIATYS_API_KEY, HIATYS_BASE_URL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 57/100 · Good | 37/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 | HIATYS_API_KEYHIATYS_BASE_URL |
| 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 | Not listed |
| Full listing | View License Verify MCP | View Getting an API Key |
Tools & capabilities
License Verify MCP tools 3
jurisdictionlicense_numberbusiness_name
Getting an API Key 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.
License Verify MCP
{
"mcpServers": {
"lmaniraruta-license-verify-mcp": {
"command": "npx",
"args": [
"-y",
"apify"
]
}
}
}
Getting an API Key
{
"mcpServers": {
"mcp-server-5": {
"command": "npx",
"args": [
"-y",
"@businys/mcp-server"
],
"env": {
"HIATYS_API_KEY": "YOUR_HIATYS_API_KEY_HERE",
"HIATYS_BASE_URL": "YOUR_HIATYS_BASE_URL_HERE"
}
}
}
}
Frequently asked questions
License Verify MCP is categorized under Legal and uses a local stdio subprocess. Getting an API Key belongs to Legal and uses a local stdio subprocess. Pick License Verify MCP for legal work and Getting an API Key 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. Getting an API Key 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 mcp-server-5 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. Getting an API Key has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.