UK Companies House (Registrum) - no API key

io.github.RegistrumUKv2.0.14更新于 Oct 8, 2026

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

已验证Streamable HTTP可网页运行Business & CommerceFinance

概览

AI 生成的概览

让助手无需 Companies House 开发者账号即可查询英国公司数据，包括公司档案、财务、董事、股权链和 ECCTA 合规状态。

功能
提供针对英国 Companies House 登记册的工具：search_company 按名称查找公司编号；get_company 返回档案、状态和 SIC 描述；get_financials 将 iXBRL 解析为营业额、净资产、盈亏和员工人数等数值；get_directors、get_psc 和 get_psc_chain 覆盖董事会与所有权；get_compliance 报告 ECCTA 身份验证状态；get_network 查找由共同董事关联的公司。get_bundle 一次调用返回档案、合规、财务、PSC 和董事。响应为 JSON，并在服务端缓存。
适用场景
当助手需要英国公司事实——所有权、申报文件、董事或 ECCTA 验证状态——又不想自行搭建 Companies House 相关管线（OAuth、限流处理、iXBRL 解析）时适用。所有权问题对私营公司更有意义；在受监管市场上市的公司豁免 PSC 制度，其所有权链为空是正常的。
运行要求
可使用远程端点（ npx 以 stdio 在本地运行 npm 包 @registrum/mcp。可选密钥 REGISTRUM_API_KEY 可提高限额；不提供时使用无密钥托管端点，有较小的每日上限。需要网络访问。
安装前请注意
匿名托管端点无状态，限流基于调用方 IP 的哈希。npm 包会发送标识包名和版本的 User-Agent 头；本地不运行遥测。bundle 中某节为 null 表示不可用而非事实不存在；合规功能还需要付费方案。付费层级提供更高用量、高级端点和 SLA。

安装

在 SourceWeft 中

  1. 打开 控制台中的 UK Companies House (Registrum) - no API key，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

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

其他 MCP 客户端

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

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

README

Registrum MCP Server

UK company data in your AI agent — without building Companies House plumbing.

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

No Companies House developer account, no rate-limit handling, no iXBRL parsing. Works in Claude Desktop, Claude Code, Cursor, and any MCP-compatible client.

Dependabot is enabled on all six Registrum repositories; as of 2026-10-08 there are zero open dependency alerts. See SECURITY.md.

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

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. Enforcement begins 18 November 2026, after which unverified officers can block filings.

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，提交 c4ea259

工具

0
工具元数据尚未被收录。

版本历史

1
  1. v2.0.14最新Oct 8, 2026