Companies House vs License Verify MCP
A side-by-side look at the Companies House 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 Companies House for legal work as a local process; 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 Companies House when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
COMPANIES_HOUSE_API_KEY.
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 | 49/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Not declared | Paid service |
| Required env vars | COMPANIES_HOUSE_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 13 | 0 |
| Directory activity | 5 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Companies House | View License Verify MCP |
Tools & capabilities
Companies House 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.
Companies House
{
"mcpServers": {
"companies-house": {
"command": "npx",
"args": [
"-y",
"companies-house-mcp"
],
"env": {
"COMPANIES_HOUSE_API_KEY": "YOUR_COMPANIES_HOUSE_API_KEY_HERE"
}
}
}
}
License Verify MCP
{
"mcpServers": {
"lmaniraruta-license-verify-mcp": {
"command": "npx",
"args": [
"-y",
"apify"
]
}
}
}
Frequently asked questions
Companies House is categorized under Legal and uses a local stdio subprocess. License Verify MCP belongs to Legal and uses a local stdio subprocess. Pick Companies House for legal work and License Verify MCP 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.
Companies House has no declared pricing — check the project's own site. Auth: api key required. License Verify MCP is listed as a paid service. 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 companies-house and lmaniraruta-license-verify-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Companies House has a quality signal of 49/100 (Fair) with 5 views, 0 installs and 13 GitHub stars. License Verify MCP has 57/100 (Good) with 5 views, 0 installs and 0 GitHub stars.