Mcp Legal Entity Resolver

com.mambabuilt由 mambabuilt.com 发布v1.4.1更新于 Nov 7, 2026

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

已验证STDIO仅桌面金融商业与电商

概览

AI 生成的概览

通过 Apify actor 将公司域名解析为对应的注册法人实体，返回法定名称、公司编号、辖区、LEI 和增值税号。

可以做什么
  • 根据单个公司域名解析其背后的注册法人实体，返回法定名称、公司编号、辖区、状态、实体类型、LEI 和增值税号等一行扁平数据。
  • 查询英国 Companies House、GLEIF、SEC EDGAR、法国 Sirene 和挪威 Brreg 等登记库，可用辖区提示或法定名称提示缩小范围。
  • 选择精确或模糊名称匹配，并查看匹配方式、置信度与被拒候选记录。
  • 将查到的增值税号提交欧盟 VIES 服务做交叉核验。
  • 使用缓存结果（匹配保留 90 天、空结果 7 天）或强制重新查询，并可设置单次调用的费用上限。
适用场景
适合需要获取公司网站背后注册法人实体、公司编号、LEI 或增值税号的场景，例如为 CRM 或表格补充经核验的公司记录。适用于合规、客户尽职调查类调研和数据补全，这类场景更看重确认过的登记匹配，而非填满每一行。
运行要求
通过 npx（Node.js）以 stdio 本地进程运行。需要 Apify 账户和 APIFY_TOKEN 环境变量。每次调用还需提供使用者本人的姓名和邮箱，作为 EDGAR 请求方身份发送给 SEC。需要能访问 Apify 平台及各公司登记库的网络。
安装前请注意
每次调用都会消耗 Apify 额度：无论是否匹配到登记记录，都按域名计费，另加 actor 启动事件费用；可用 max_charge_usd 限制花费。APIFY_TOKEN 是付费账户凭据。提供的姓名和邮箱会发送给 SEC，域名会发送给第三方登记库和 VIES。模糊匹配可能给出看似确定但错误的公司，行动前应核对匹配置信度和被拒候选。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Mcp Legal Entity Resolver，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Legal Entity Resolver MCP Server

[Glama score] [MCP Registry] [npm version] [npm downloads] [license] [mcpservers.org]

[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

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

Claude Desktop

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

resolve_legal_entity

Company domain in, the registered legal entity behind it out.

InputTypeRequiredNotes
sec_requester_namestringyesYour own name or your company's name, sent to the SEC.
sec_requester_emailstringyesYour own working email, sent to the SEC with your name.
domainstringyesA single company domain, for example monzo.com. Protocol and path are stripped.
legal_name_hintstringnoSkips 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_hintstringnoISO-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_strictnessenumnoexact 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_vatbooleannoRuns 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.
skipCacheenumnofalse uses the cache, 90 days for a resolved company and 7 days for a null. true forces a fresh look. Default false.
max_charge_usdnumbernoOptional spending cap for this call, in USD. The actor stops before any charge that would take the run past this amount and keeps every row already charged.

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.

Why the SEC fields are required. The SEC requires every automated request to EDGAR to identify the requester by name and email, as a User-Agent of the form Name [email protected] (SEC: Accessing EDGAR data). The actor sends your sec_requester_name and sec_requester_email and never a default or shared identity. A call without both fails before any request, naming the two fields.

Billing

You are charged per domain resolved, plus the platform's actor start event. Prices from the live pricing record, read 2026-10-05:

EventPrice per event (USD)Fires when
domain-resolved$0.007 on the Free plan, down to $0.00595 on higher Apify plansOne domain looked up: the company's own pages fetched and read for a legal name, then up to three company registers queried for an exact match. Charged whether or not a register matches, because the work is the same either way and charging only for matches would push this Actor toward guessing. Not charged when the domain cannot be reached at all.
apify-actor-start$0.00005Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).

Cached results are 90 days for a resolved company and 7 days for a null. The actor's Apify page carries the current prices. 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.

How each call runs

Each call starts the actor run, polls it until it finishes, then reads the dataset. The run is allowed 1,800 seconds. If the run is still going when this call stops waiting, the call returns the run id and a console link instead of a timeout, so the result is never lost.

Source

The actor is on the Apify Store. This wrapper is MIT licensed.

Built by Mamba Labs

来源：README.md，提交 af842d6

工具

1

版本历史

6
  1. v1.4.1最新Nov 5, 2026
  2. v1.4.0Oct 16, 2026
  3. v1.3.0Oct 16, 2026
  4. v1.2.1Oct 6, 2026
  5. v1.2.0Oct 6, 2026
  6. v1.1.0Sep 16, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分