Commonwealth Corporate Registry

Name: Commonwealth Corporate Registry
Author: apifyforge

@apifyforge

Repository Homepage Documentation

About Commonwealth Corporate Registry

Commonwealth corporate registry intelligence for AI agents, delivered via the Model Context Protocol.

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "commonwealth-corporate-registry-mcp": {
      "url": "https://ryanclinton--commonwealth-corporate-registry-mcp.apify.actor/mcp"
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Commonwealth Corporate Registry?

Commonwealth Corporate Registry is a Model Context Protocol (MCP) server that queries Australian ABN, Canadian Corporation, New Zealand Companies Office, UK Companies House, OpenCorporates, GLEIF LEI, and Wikipedia simultaneously. It returns cross-jurisdiction entity data, concordance scores, and identity verification grades in a single structured response. Built for KYB analysts, compliance teams, and AI agents needing authoritative company registration data across Commonwealth jurisdictions.

How to use Commonwealth Corporate Registry?

Add the server URL (https://commonwealth-corporate-registry-mcp.apify.actor/mcp) and your Apify API token as a Bearer Authorization header to your MCP client configuration (Claude Desktop, Cursor, Windsurf, Cline, or any MCP-compatible agent). Then call any of the eight available tools — for example, verify_global_identity with a company name to get a confidence grade, or cross_reference_registries to compare entity presence across registries.

Key features of Commonwealth Corporate Registry

Parallel 7-actor dispatch across government and LEI registries
Unified registry graph with typed nodes and edges
Concordance scoring (0–1) for cross-jurisdiction match confidence
Identity confidence grading (A–F) from registration, LEI, and Wikipedia
Name variation detection across all registry records
Report severity ranking with actionable remediation steps

Use cases of Commonwealth Corporate Registry

KYB entity verification: get a single A–F identity grade for onboarding decisions
Cross-border corporate structure mapping: reveal subsidiaries, shells, and holding arrangements
AML compliance checks: detect status discordance (Active vs. Dissolved across registries)
M&A due diligence: generate structured registry reports with severity-ranked findings
AI agent corporate research: replace web scraping with deterministic, scored registry JSON

FAQ from Commonwealth Corporate Registry

How does it differ from manually searching registries?

It replaces 30–60 minutes of manual portal work per entity with a single MCP tool call that queries seven sources in parallel, returns scored intelligence, and caches results for 5 minutes to avoid redundant calls.

What runtime dependencies does it require?

No local installation. The server is hosted on Apify; you only need an Apify API token and an MCP-compatible client. All data fetching and scoring happens server-side.

Where does the data come from and how is it stored?

Data is fetched live from official government registries (Australia ABN, Canada Corporation, NZ Companies, UK Companies House), OpenCorporates, GLEIF LEI, and Wikipedia. No data is persisted beyond a 5-minute in-memory cache per session.

What are the known limits?

Each tool caps results at 40 entities and 500 dataset items per actor to maintain cost and response time. Per-tool pricing is $0.05 per call, with configurable spending limits via Apify; the server halts cleanly when the budget is reached.

Which transports and authentication are supported?

Dual transport: SSE (/sse + /messages) and Streamable HTTP (/mcp). Authentication is via an Authorization: Bearer YOUR_APIFY_TOKEN header. Legacy clients can use the SSE endpoint.