OpenRegistry documentation

Live, unmodified company-registry data from 27 national governments via a single MCP endpoint. 27 tools, 10 pre-built Claude skills, streamable HTTP transport.

Getting started

OpenRegistry is a Model Context Protocol server. Connect your AI client to the MCP endpoint and sign in for the free tier.

Free tier: 30 requests/min per user, all tools, all jurisdictions. See pricing for paid tiers.

Tools (27)

Every tool returns live data from the statutory source. The top-level response is unified across countries; registry-specific fields come through verbatim under jurisdiction_data.

Discovery

  • list_jurisdictions Per-country schema reference + cross-country support-matrix for any tool.
  • about Server-level info - principles, tool list, data licences, fan-out caps, rate limits.

Search

  • search_companies Find companies by name or filter - single jurisdiction, or multi-country fan-out with user confirmation.
  • search_companies_near_point Geospatial search: candidates within a radius of a lat/lng point (where upstream supports it).
  • count_companies Count-only endpoint (currently IE) - fast totals without fetching candidates.
  • search_officers Find people by name across a registry - each hit returns an officer_id to pipe into appointments.
  • search_addresses Resolve free-text addresses to structured registry codes (e.g. CZ RÚIAN kodObce).
  • search_specialised_records Search non-company registers (FR associations, NZ financial-service providers, etc.).

Company profile

Filings & financials

  • list_filings Filing history with normalised categories + optional document_id round-trip.
  • get_financials Annual-accounts filings normalised with period_end, document_id, source_url.

Officers, PSC, shareholders, charges

Documents

Utility

Claude Agent Skills (10)

Pre-built workflows for common due-diligence tasks. Install with npx skills add sophymarine/openregistry, or clone individual SKILL.md files from the repo.

Agent framework integrations

OpenRegistry is a standards-compliant MCP server, so every major AI agent framework can use it out of the box. Pick your stack for a working code sample:

MCP directory listings

API

Endpoints exposed by this server

MethodPathDescription
POST/mcpMCP 2025-06-18 Streamable HTTP transport.
GET/.well-known/mcp.jsonMCP discovery manifest.
GET/.well-known/oauth-protected-resourceOAuth 2.0 Protected Resource Metadata (RFC 9728).
GET/.well-known/oauth-authorization-serverOAuth 2.1 Authorization Server Metadata (RFC 8414).
GET/.well-known/jwks.jsonPublic JSON Web Key Set for access-token verification.
POST/oauth/registerDynamic Client Registration (RFC 7591) - public clients with PKCE.
GET/oauth/authorizeOAuth 2.1 authorization endpoint with consent screen.
POST/oauth/tokenAuthorization-code + refresh-token grants.
GET/loginPasswordless magic-link sign-in.
GET/accountSigned-in account overview and session management.
GET/account/upgradePick a paid tier - Stripe Checkout handoff.
GET/healthzHealth check with jurisdiction inventory.
GET/privacy · /termsPolicies.