# com.mambabuilt/mcp-legal-entity-resolver (npm · @mambalabsdev/mcp-legal-entity-resolver)

Resolve a company domain to its registered legal entity, company number, LEI and VAT number.

- Trust score: 73/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-22

## Components

- npm · `@mambalabsdev/mcp-legal-entity-resolver`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-mambabuilt-mcp-legal-entity-resolver/mambalabsdev-mcp-legal-entity-resolver.md), [page](https://verifymcp.io/servers/com-mambabuilt-mcp-legal-entity-resolver/mambalabsdev-mcp-legal-entity-resolver)

## Channel facts

- Registry: `npm`
- Package: `@mambalabsdev/mcp-legal-entity-resolver`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-22.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 471 tokens (~471/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add com-mambabuilt-mcp-legal-entity-resolver -- npx -y @mambalabsdev/mcp-legal-entity-resolver
```

### Cursor

```json
{
  "mcpServers": {
    "com-mambabuilt-mcp-legal-entity-resolver": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-legal-entity-resolver"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-mambabuilt-mcp-legal-entity-resolver": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-legal-entity-resolver"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-mambabuilt-mcp-legal-entity-resolver -- npx -y @mambalabsdev/mcp-legal-entity-resolver
```

### opencode

```json
{
  "$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

```bash
openclaw mcp add com-mambabuilt-mcp-legal-entity-resolver --command npx --arg -y --arg @mambalabsdev/mcp-legal-entity-resolver
```

### Hermes

```yaml
mcp_servers:
  com-mambabuilt-mcp-legal-entity-resolver:
    command: "npx"
    args: ["-y", "@mambalabsdev/mcp-legal-entity-resolver"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-mambabuilt-mcp-legal-entity-resolver": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@mambalabsdev/mcp-legal-entity-resolver"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-mambabuilt-mcp-legal-entity-resolver -t stdio -c npx -a -y @mambalabsdev/mcp-legal-entity-resolver
```

### Other

```json
{
  "mcpServers": {
    "com-mambabuilt-mcp-legal-entity-resolver": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-legal-entity-resolver"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-21 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-19 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-18 (score 71, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-08-12 (score 68, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-08-11 (score 53)

First indexed and scored.

## MCP tools (1)

### `resolve_legal_entity` (~471 tokens)

Resolve Legal Entity

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.

Input parameters:

- `domain` (string, required): A single company domain, for example monzo.com. Protocol and path are stripped.
- `jurisdiction_hint` (string): ISO-2 country code, for example GB or US. Narrows which registers are queried and cuts latency. Leave empty to query every register.
- `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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-mambabuilt-mcp-legal-entity-resolver/mambalabsdev-mcp-legal-entity-resolver#diagnostics

## Score history

- 2026-08-22: 73
- 2026-08-21: 73
- 2026-08-20: 72
- 2026-08-19: 72
- 2026-08-18: 71
- 2026-08-17: 68
- 2026-08-16: 68
- 2026-08-15: 68
- 2026-08-14: 68
- 2026-08-13: 68
- 2026-08-12: 68
- 2026-08-11: 53

## Common questions

### 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 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 August 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 471 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 22 August 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.

## Links

- npm package: https://www.npmjs.com/package/@mambalabsdev/mcp-legal-entity-resolver
- Socket report: https://socket.dev/npm/package/@mambalabsdev/mcp-legal-entity-resolver
- Repository: https://github.com/mambalabsdev/mcp-legal-entity-resolver
- Changelog RSS feed: https://verifymcp.io/servers/com-mambabuilt-mcp-legal-entity-resolver/mambalabsdev-mcp-legal-entity-resolver.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mambabuilt-mcp-legal-entity-resolver/mambalabsdev-mcp-legal-entity-resolver.json
- HTML version of this page: https://verifymcp.io/servers/com-mambabuilt-mcp-legal-entity-resolver/mambalabsdev-mcp-legal-entity-resolver