Registrum Mcp

io.github.vdmeu由 GitHub 账号 vdmeu 发布v2.0.12更新于 Nov 4, 2026

UK company data: profiles, iXBRL financials, directors, PSC chains, ECCTA. Hosted, no key.

已验证Streamable HTTP可网页运行金融数据与分析商业与电商

概览

AI 生成的概览

让助手获取英国 Companies House 实时数据:公司档案、解析后的财报、董事、PSC 股权链和 ECCTA 身份核验状态。

可以做什么
  • 按名称搜索公司,获取档案、状态、SIC 行业描述和逾期标记
  • 读取从 iXBRL 解析出的营业额、净资产、盈亏和员工人数(英镑)
  • 列出在任董事及其任职历史,并查找通过共同董事关联的公司
  • 查询重要控制人(PSC)及穿透至最终受益人的股权链
  • 检查 ECCTA 身份核验状态,含已核验、待核验、逾期数量及个人截止日期
  • 用一次 bundle 调用同时获取档案、合规、财报、PSC 和董事,或以 MCP 资源模板方式读取
适用场景
适合英国公司尽职调查、KYB 和股权研究:查私人公司最终由谁控制、董事是否已按 ECCTA 完成身份核验、公司财务变化,或哪些公司共用董事。可省去自行注册 Companies House 开发者密钥和解析 iXBRL 的工作。
运行要求
可使用托管远程端点(无需密钥、无需注册),或通过 npx 运行本地 npm 包(需要 Node.js)。可选环境变量 REGISTRUM_API_KEY 可提高额度;不设置时使用无密钥托管端点,有较小的每日上限。需要能访问服务方的网络。
安装前请注意
无密钥端点每日额度较小;免费密钥提供 60 天完整访问,PSC 股权链穿透和 ECCTA 合规等高级端点需付费方案。请求会发送给第三方服务,其会缓存响应并按调用 IP 的哈希限流;npm 包会发送标识自身的 User-Agent。某部分返回 null 表示数据不可用,而非该事实不存在。

安装

在 SourceWeft 中

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

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.vdmeu%2Fregistrum-mcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "registrum": {
      "type": "http",
      "url": "https://registrum.co.uk/api/mcp"
    }
  }
}

README

[Registrum]

UK Companies House MCP Server: due diligence and KYB (Registrum)

UK company due diligence and KYB: trace ownership to the beneficial owners, pull director histories, check ECCTA identity-verification status and deadlines, read parsed accounts. Live Companies House data, hosted, no key.

[MCP Registry] [npm] [Status] [Docs]

No Companies House developer account, no rate-limit handling, no iXBRL parsing. Works in Claude Desktop, Claude Code, Cursor, VS Code, and any MCP-compatible client. It also answers ChatGPT search and fetch.

[Install in VS Code] [Install in VS Code Insiders] [Install in Cursor] [Smithery]

Dependabot alerts and update pull requests are enabled on all six Registrum repositories; SECURITY.md says where to see the live alert count.

Try it now — no signup, no key, no install

Point your client at the hosted endpoint and every tool answers with real data:

https://registrum.co.uk/api/mcp
json
{  "mcpServers": {    "registrum": {      "url": "https://registrum.co.uk/api/mcp"    }  }}

That is the whole setup. Ask it "Who ultimately owns BrewDog?" and it will trace the ownership chain to the named individuals who hold control.

One thing worth knowing before you test it on a household name: companies listed on a regulated market — Tesco, Rolls-Royce, most of the FTSE — are exempt from the PSC regime, so their ownership chain is legitimately empty and get_psc_chain says so rather than inventing a tree. Ownership questions are interesting on private companies, which is where the register actually records who is behind them.

The hosted endpoint has small daily caps, enough to see exactly what comes back. When you reach one, the tool tells you so and points at a free key; nothing silently degrades.

Three ways to use it

  1. Try it - no key. Point your MCP client at https://registrum.co.uk/api/mcp and ask about any UK company. No signup.
  2. Build with it - free key. 60 days of full access: every endpoint, no monthly cap, no card. After that the key stays free for light use.
  3. Run on it - paid plan. When you need volume, premium endpoints or an SLA. Live prices and limits: GET /v1/plans.

Why this instead of the Companies House API directly

Companies House publishes the raw register for free, and you can absolutely call it yourself. What you then own is the plumbing:

Doing it yourselfWith Registrum
Register for a CH developer key, manage OAuthNothing, or one REGISTRUM_API_KEY
600 requests/5min, and you handle the 429sServer-side throttling on a higher negotiated budget
Accounts arrive as iXBRL documents you must parseget_financials returns turnover, net assets, profit/loss as numbers
PSC control types are raw codesDecoded to plain English
Ownership chains: recurse yourself, handle cyclesget_psc_chain returns the resolved tree with termination reasons
Director networks: N+1 queries across appointmentsget_network traverses to depth 2
Retry, cache, and survive CH outages yourself24h/7d caching, circuit breaker, stale-while-revalidate

Other Companies House MCP servers make you bring your own CH key and hand back the raw response. This one does the enrichment.


Running it with your own key

Use a key to build on it (60 days of full access), or when you would rather run the server locally than call ours.

Claude Desktop — ~/.claude/claude_desktop_config.json Cursor — .cursor/mcp.json (per project) or ~/.cursor/mcp.json (global)

json
{  "mcpServers": {    "registrum": {      "command": "npx",      "args": ["-y", "@registrum/mcp"],      "env": { "REGISTRUM_API_KEY": "reg_live_..." }    }  }}

Get a free key — 60 days of full access, no card.


Tools

ToolWhat you get
search_companyFind a company by name → company number
get_bundleProfile, compliance, financials, PSCs and directors in one call - start here
get_companyProfile: status, age, SIC descriptions, overdue flags
get_financialsTurnover, net assets, profit/loss, employees — parsed from iXBRL, in GBP
get_directorsCurrent board with appointment history across all their companies
get_pscPersons with Significant Control, control types in plain English
get_psc_chainOwnership traversed to ultimate beneficial owners, with termination reasons
get_complianceECCTA identity-verification status — who has verified, who is pending, who is overdue
get_networkCompanies connected by shared directors, to depth 2
searchFor ChatGPT connectors and deep research: returns {results: [{id, title, url}]} for a company name
fetchFor ChatGPT connectors and deep research: takes a company:<number> id from search, returns the profile as a citable document

Resources

The same data is also exposed as MCP resource templates, for clients that attach context by URI. Each returns the JSON of the matching tool, goes through the same usage limits, and accepts a short numeric number (it is zero-padded to 8 characters).

ResourceSame JSON as
company://{number}/profileget_company
company://{number}/financialsget_financials
company://{number}/pscget_psc
company://{number}/complianceget_compliance

On get_bundle

Most questions about a company need several of these views at once. get_bundle returns them in a single request: one call and one credit instead of five, and one round trip instead of five. Pass include to fetch a subset, or omit it for all five sections.

Each section carries exactly what its own endpoint returns, because the bundle is composed from those same handlers rather than reimplemented - so plan gates, caching and the ECCTA rules behave identically either way.

A null section is not an error. Financials come back null for a company that has filed no machine-readable accounts, and compliance requires a Pro plan. Only a missing company is an error, and that is a 404. Report a null section as "not available", never as an absence of the underlying fact.

On get_compliance

The Economic Crime and Corporate Transparency Act requires every UK director and PSC to verify their identity with Companies House. Deadlines are per company, not one date: each existing director is due by their company's next confirmation-statement due date, so the date differs from company to company. Unverified officers can block filings once it passes.

The tool returns verified / pending / overdue counts plus each unverified person and their individual deadline. It deliberately distinguishes pending (deadline not yet reached — not a failure) from overdue (missed). Treating those as the same thing is the single easiest way to report a compliant company as non-compliant.


Example prompts

"Is Tesco PLC compliant with ECCTA director verification, and who still needs to verify?"

"Pull the last filed financials for 00445790 and tell me if turnover grew."

"Who ultimately owns BrewDog? Trace the ownership chain to the individuals."

"Which companies share directors with Barratt Developments?"

"Search for 'Monzo' and show me status, incorporation date and directors."


Plans

The anonymous endpoint needs no account at all. A free key gives 60 days of full access, then stays free for light use; paid tiers add volume, premium endpoints such as PSC chain traversal and the ECCTA compliance endpoint, and an SLA.

Prices and quotas are served live from GET /v1/plans — that endpoint is the source of truth, so this README does not duplicate the numbers and cannot go stale against them. Human-readable version at registrum.co.uk.


Notes

  • Company numbers are zero-padded 8-character strings: 00445790, SC000268.
  • Responses are JSON, cached server-side (24h profiles/directors, 7d financials).
  • The hosted endpoint is stateless and anonymous: it stores no account, and rate limiting is keyed on a hash of the calling IP rather than anything about you.
  • The npm package sends User-Agent: @registrum/mcp/<version> so we can see which features developers actually use. No telemetry runs on your machine.

API reference · Issues · [email protected]

来源:README.md,提交 b806aa8

工具

0
SourceWeft 尚未读取此服务器的工具。

版本历史

3
  1. v2.0.12最新Oct 7, 2026
  2. v2.0.10Oct 4, 2026
  3. v2.0.7Sep 16, 2026

评分

已满足适用检查项的 50%

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

  • 近 30 天内可连通必需25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式必需10 分

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

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分