MCP Legal Entity Resolver

What mcp-legal-entity-resolver MCP server does

mcp-legal-entity-resolver MCP server connects an MCP client to Mamba Labs’ Legal Entity Resolver actor on Apify. It takes a company domain and returns the registered entity associated with that domain. The returned record can contain the legal name, company number, jurisdiction, registration status, Legal Entity Identifier (LEI), and VAT number, along with other fields produced by the actor.

The result is intended to identify the legal organization behind a website, not to assess that organization. The server does not provide credit scoring, risk ratings, trading recommendations, or a general company database. It passes inputs to the actor and returns the actor’s output without transforming it.

How it works

Each tool call starts an Apify actor run, waits for it to finish, and then reads the resulting dataset. The run can continue for up to 1,800 seconds. If the waiting period ends while the actor is still running, the response includes the run ID and an Apify console link so the run can be followed rather than discarded.

The actor first examines the company’s own pages for a legal name, then queries relevant registers for a match. Supported jurisdiction hints include GB or UK for Companies House, US for SEC EDGAR, FR for the French Sirene register, and NO for the Norwegian Brreg register. Each of these also checks GLEIF; other jurisdiction codes use GLEIF alone, while an empty hint queries all supported sources.

Exact matching is the default. In that mode, a candidate is accepted only when normalized legal names are equal. fuzzy mode returns the highest-scoring candidate with a confidence below 100 and a warning in rejected_candidates, so it should be treated as research output rather than confirmation. Review match_method, match_confidence, and rejected_candidates before using a result.

Setup and configuration

Install the package with:

npx -y @mambalabsdev/mcp-legal-entity-resolver

The server requires an Apify token supplied as the APIFY_TOKEN environment variable. The token can be obtained from the Apify account integrations page. A Claude Desktop configuration uses npx as the command, passes the package name in the arguments, and places the token in the MCP server’s environment.

Apify usage consumes credits. Billing includes a per-domain resolution event and an actor-start event. Cached resolved results are retained for 90 days, while null results are cached for 7 days. Set skipCache to true to force a fresh lookup.

Tools and capabilities

The mcp-legal-entity-resolver MCP server exposes one tool:

• resolve_legal_entity: accepts one required domain string. Protocols and paths are removed from the supplied value.
• legal_name_hint: optionally skips domain lookup and searches registers using a known legal name.
• jurisdiction_hint: optionally limits the register strategy with an ISO-2 country code.
• match_strictness: selects exact or fuzzy matching; the default is exact.
• validate_vat: optionally checks a VAT number found on the company’s pages through EU VIES; the default is true.
• skipCache: chooses cached data or a fresh actor run; the default is false.

Limitations and notes

A null result is an expected outcome when the actor cannot establish an exact registry match. Register search endpoints can return plausible but incorrect candidates, so accepting the first result is not equivalent to resolving the entity. Fuzzy mode increases recall but can return a wrong company.

The wrapper surfaces failures instead of replacing them with empty results. Invalid input or token errors, exhausted Apify balance, timeouts, and non-dataset actor results are returned as explicit tool errors. The server itself is MIT licensed; the underlying lookup behavior belongs to the Apify actor.