Resolve a company domain to its registered legal entity, company number, LEI and VAT number.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Not yet automatically verified
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Choose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Capabilities & Tool Schemas (1)
Inspect callable tools, capabilities, and parameters exposed to AI agents by MCP Legal Entity Resolver.
resolve_legal_entityCompany domain in, the registered legal entity behind it out.
Documentation Overview
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
Claude Desktop
Get an Apify token at console.apify.com/account/integrations.
Tool
resolve_legal_entity
Company domain in, the registered legal entity behind it out.
| Input | Type | Required | Notes |
|---|---|---|---|
domain | string | yes | A single company domain, for example monzo.com. Protocol and path are stripped. |
legal_name_hint | string | no | Skips the domain lookup and goes straight to the registers with this name. Use it when you already have the legal name and just want the register record. |
jurisdiction_hint | string | no | ISO-2 country code. GB/UK asks Companies House, US asks SEC EDGAR, FR asks the French Sirene register (SIREN), NO asks the Norwegian Brreg register (organisasjonsnummer). Each asks GLEIF alongside. Any other code asks GLEIF alone. Leave empty to query all five. |
match_strictness | enum | no | exact accepts a register record only when the normalized legal names are equal. fuzzy returns the best scoring candidate with a confidence below 100 and a warning in rejected_candidates. Default exact. |
validate_vat | boolean | no | Runs any VAT number found on the company's own pages through the EU VIES service and returns the name VIES holds for it, as a cross-check against the register name. Default true. |
skipCache | enum | no | false uses the cache, 90 days for a resolved company and 7 days for a null. true forces a fresh look. Default false. |
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.
Read match_method, match_confidence and rejected_candidates before acting on a match. fuzzy strictness is a research mode: it will hand you a confidently wrong company on most domains.
Three registers are queried: UK Companies House, GLEIF and SEC EDGAR.
Billing
You are charged per domain resolved, plus a small actor start fee. Cached results are 90 days for a resolved company and 7 days for a null.
Pricing is on the actor's Apify page. Running this server consumes Apify credits.
What this server does and does not do
It is a thin client for the Apify actor. It passes your input through and returns the actor's output unchanged. Every behavior described above lives in the actor, not here.
This is not a company database and not a credit or risk product. It does not score companies, rate them, or tell you whether to trade with them. It answers one question: which registered legal entity sits behind this domain.
Errors are surfaced, never swallowed. An invalid input, an invalid token, an exhausted balance, a timeout, or a run that returns anything other than a dataset all come back as an explicit tool error rather than as an empty result.
Source
The actor is on the Apify Store. This wrapper is MIT licensed.
Built by Mamba Labs
Related MCP Servers
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about MCP Legal Entity Resolver
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/mcp-legal-entity-resolver)HTML Embed
<a href="https://allmcps.com/mcp/mcp-legal-entity-resolver"><img src="https://allmcps.com/api/badge/mcp-legal-entity-resolver?style=directory" alt="MCP Legal Entity Resolver on AllMCPs" /></a>Technical Specs & Signals
CategoryLegal
51Quality signal: Good · 51/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership10/20
Documentation & tools24/30
Adoption & activity4/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.