Legal Entity Resolver MCP server
Resolve a company domain to its registered legal entity, company number, LEI and VAT number.
0 stars103 downloads/wk
Reviews
Write oneNobody has reviewed Legal Entity Resolver yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Legal Entity Resolver tools (1)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
resolve_legal_entity
Public scan report
scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it
- Code scan2 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 5 days ago15/15
- Maintainer identitynamespace and repository owner differ4/10
How Legal Entity Resolver compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Tools
- 1
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 103
- more than 63% of 12,191 servers with a package
What its tools let an agent do: 1 read
Release history: 4 versions in the registry since 2026-08-24, latest 2026-10-16, typically one every 10 days.
Install Legal Entity Resolver in Claude Code, Cursor or VS Code
Runs npx -y @mambalabsdev/mcp-legal-entity-resolver on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-legal-entity-resolver -- npx -y @mambalabsdev/mcp-legal-entity-resolver
What the publisher says
From the Legal Entity Resolver repository's README, as published. We do not edit it. Read it on GitHub
Legal Entity Resolver MCP Server
MCP server for the Mamba Labs Legal Entity Resolver actor on Apify.
Give it a company domain and it returns the registered legal entity behind it: legal name, company number, jurisdiction, status, LEI and VAT number. One flat row per domain, 24 fields, ready for Clay or a CRM.
Install
npx -y @mambalabsdev/mcp-legal-entity-resolverClaude Desktop
{
"mcpServers": {
"mamba-legal-entity-resolver": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-legal-entity-resolver"],
"env": { "APIFY_TOKEN": "your-apify-token" }
}
}
}Get an Apify token at console.apify.com/account/integrations.
Tool
resolvelegalentity
Company domain in, the registered legal entity behind it out.
A null is the product, not a gap
Register search endpoints are fuzzy and they always return something. Taking the top search result gives you a confidently wrong company number more often than not. This actor accepts a match only when the legal names are identical after normalization, which is why roughly 6 domains in 10 resolve instead of 10 in 10, and why the 6 are worth acting on.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Legal Entity Resolver: common questions
- Is Legal Entity Resolver MCP server safe?
- Mostly: it is graded B (77/100). Read the Legal Entity Resolver safety report
- How do I install Legal Entity Resolver?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Legal Entity Resolver need an API key?
- Yes. The registry entry asks for
APIFY_TOKEN. - Is Legal Entity Resolver maintained?
- The last commit was 8 days ago (2026-10-27). The latest release is v1.4.0.
- How does Legal Entity Resolver compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.