com.mambabuilt/mcp-legal-entity-resolver
NPM · @MAMBALABSDEV/MCP-LEGAL-ENTITY-RESOLVER · SCANNED OCT 12
Resolve a company domain to its registered legal entity, company number, LEI and VAT number.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 555 tokens (~555/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.mambabuilt/mcp-legal-entity-resolver server?
com.mambabuilt/mcp-legal-entity-resolver runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-legal-entity-resolver. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mambalabsdev/mcp-legal-entity-resolver
claude mcp add com-mambabuilt-mcp-legal-entity-resolver -- npx -y @mambalabsdev/mcp-legal-entity-resolver
{
"mcpServers": {
"com-mambabuilt-mcp-legal-entity-resolver": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-legal-entity-resolver"
]
}
}
} {
"servers": {
"com-mambabuilt-mcp-legal-entity-resolver": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-legal-entity-resolver"
]
}
}
} codex mcp add com-mambabuilt-mcp-legal-entity-resolver -- npx -y @mambalabsdev/mcp-legal-entity-resolver
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mambabuilt-mcp-legal-entity-resolver": {
"type": "local",
"command": [
"npx",
"-y",
"@mambalabsdev/mcp-legal-entity-resolver"
],
"enabled": true
}
}
} openclaw mcp add com-mambabuilt-mcp-legal-entity-resolver --command npx --arg -y --arg @mambalabsdev/mcp-legal-entity-resolver
mcp_servers:
com-mambabuilt-mcp-legal-entity-resolver:
command: "npx"
args: ["-y", "@mambalabsdev/mcp-legal-entity-resolver"] {
"McpServers": {
"com-mambabuilt-mcp-legal-entity-resolver": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@mambalabsdev/mcp-legal-entity-resolver"
]
}
}
} assistant mcp add com-mambabuilt-mcp-legal-entity-resolver -t stdio -c npx -a -y @mambalabsdev/mcp-legal-entity-resolver
{
"mcpServers": {
"com-mambabuilt-mcp-legal-entity-resolver": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-legal-entity-resolver"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
- Package version: 1.1.0 → 1.2.1 functional
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 −4
- Stability: pass → 0.77 functional
- 30 Sept 26 +1
- Stability: 0.97 → pass security
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 12 Oct 2026 · Analysed npm/@mambalabsdev/mcp-legal-entity-resolver@1.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
resolve_legal_entity Resolve Legal Entity ~555
Give it a company domain and it returns the registered legal entity behind it: legal name, company number, jurisdiction, status, entity type, LEI and VAT number, as one flat row with a full audit trail of what was rejected and why. Three registers are queried: UK Companies House, GLEIF and SEC EDGAR. Register search endpoints are fuzzy and always return something, so by default a record is accepted only when the normalized legal names are identical. That is why roughly 6 domains in 10 resolve rather than 10 in 10, and why a null here is a trustworthy answer rather than a gap. Read match_method, match_confidence and rejected_candidates before acting on a match. Setting match_strictness to fuzzy will hand you a confidently wrong company on most domains and should be treated as a research mode, not a default. This is not a company database and not a credit or risk product. Requires an APIFY_TOKEN and consumes Apify credits. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A single company domain, for example monzo.com. Protocol and path are stripped. |
| jurisdiction_hint | string | – | ISO-2 country code. GB or UK asks Companies House and GLEIF and returns a Companies House number. US asks GLEIF and SEC EDGAR. FR asks the French Sirene register and returns a SIREN. NO asks the Norw… |
| legal_name_hint | string | – | 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. |
| match_strictness | string | – | exact accepts a register record only when the normalized legal names are equal, which is the default and the recommendation. fuzzy returns the best scoring candidate with a confidence below 100 and a… |
| skipCache | string | – | false uses the cache: 90 days for a resolved company, 7 days for a null. true forces a fresh look. Default: "false". |
| validate_vat | boolean | – | 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. |
No output schema declared.
No examples provided.
What is the com.mambabuilt/mcp-legal-entity-resolver server?
com.mambabuilt/mcp-legal-entity-resolver is listed in the public MCP registry as com.mambabuilt/mcp-legal-entity-resolver. Resolve a company domain to its registered legal entity, company number, LEI and VAT number. This page covers its npm package (@mambalabsdev/mcp-legal-entity-resolver).
Is the com.mambabuilt/mcp-legal-entity-resolver server safe to use?
com.mambabuilt/mcp-legal-entity-resolver scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 12 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mambabuilt/mcp-legal-entity-resolver server expose?
com.mambabuilt/mcp-legal-entity-resolver exposes 1 tool: resolve_legal_entity. Their descriptions and schemas cost roughly 555 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-legal-entity-resolver server still maintained?
com.mambabuilt/mcp-legal-entity-resolver is still listed as active in the MCP registry. We last reached this channel on 12 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.mambabuilt/mcp-legal-entity-resolver server under?
com.mambabuilt/mcp-legal-entity-resolver declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.