getregdata

getregdata MCP server

An MCP server that gives any MCP-capable agent (Claude Desktop, Claude Code, Cursor, Cline, Windsurf, ...) direct access to official business-registry actors for KYC/AML, credit-risk, due-diligence and B2B data across Poland, Germany, Italy, Spain, Austria, France, Belgium, Czechia, Slovakia, Norway, Denmark, Estonia, Cyprus, Ireland, Portugal, Nigeria, Colombia, the US (California, Illinois, county clerks) and the UAE - plus a cross-border adverse-media screener.

Where it is strongest: insolvency and restructuring proceedings from official gazettes in Poland, Germany, Austria, France, Spain and Czechia, and Central and Eastern European registers that global databases carry thinly - KRS financial statements, CRBR beneficial owners, Polish land and mortgage registers, Czech annual accounts and the Slovak UBO register.

For a Polish company, regdata_poland_kyb_check answers the whole question in one call - identity, beneficial owners, and insolvency screened against the company and every beneficial owner, returned as a single verdict. The per-registry tools are the depth behind that answer, and the way to run the same jobs elsewhere.

Each registry is exposed as its own tool (e.g. regdata_crbr_beneficial_owners, regdata_germany_handelsregister, regdata_adverse_media), plus three helpers:

• regdata_catalog - list every registry tool and what it returns.
• regdata_describe - fetch a specific actor's live input schema so the agent builds a correct call.
• regdata_run_result - collect a check that was still running when its tool call returned.

Long checks return a handle, not a failure

Most calls return dataset items directly. If a run is still going after ~45 seconds, the tool returns {status, runId, datasetId, note} instead. That run is still going and is already billed, so call regdata_run_result with the runId to collect it - re-running the check to "retry" charges the user twice.

This matters most for the Poland KYB composite: 20-30 seconds typically, up to ~2.5 minutes for a company with many beneficial owners. Set "timeout": 600000 on the server in your MCP config so the common case still returns inline.

Treat a runId as a secret: Apify resolves run and dataset IDs without checking ownership, so anyone holding the ID can read that check's result.

Setup

You need an Apify API token (free, includes $5 credits): apify.com.

Claude Desktop / Claude Code

Add to your MCP config (claude_desktop_config.json, or .mcp.json for Claude Code):

{
  "mcpServers": {
    "getregdata": {
      "command": "npx",
      "args": ["-y", "getregdata-mcp"],
      "env": { "APIFY_TOKEN": "apify_api_xxxxx" },
      "timeout": 600000
    }
  }
}

Cursor / Cline / Windsurf

Same block in the client's MCP settings (mcp.json / MCP servers panel). The server speaks stdio, so npx -y getregdata-mcp with APIFY_TOKEN in env is all you need.

Hosted clients - claude.ai web, ChatGPT developer mode, Gemini (no install)

This npm server is stdio-only. For hosted agents that need a remote HTTPS endpoint, connect Apify's hosted MCP server with OAuth instead - the regdata actors are first-class tools there:

https://mcp.apify.com/?actors=regdata/crbr-beneficial-owners-scraper,regdata/krz-debtor-scraper,regdata/germany-handelsregister-scraper,regdata/poland-krs-financial-scraper,regdata/adverse-media-screener

Swap in any regdata actor, or connect plain https://mcp.apify.com and let the agent discover them via search-actors ("Poland beneficial owners", "Germany insolvency", ...). OAuth signs you into your own Apify account, so billing and the free credit work exactly like the local server.

Usage

Once connected, just ask your agent in natural language:

• "Run a KYB check on Polish NIP 6770065406." -> regdata_poland_kyb_check (one verdict)
• "Screen Wirecard for adverse media." -> regdata_adverse_media
• "Who are the beneficial owners of Polish NIP 5260250995?" -> regdata_crbr_beneficial_owners
• "Is this German company in the Handelsregister?" -> regdata_germany_handelsregister
• "Check this company against the Czech insolvency register." -> regdata_czech_isir

If the agent is unsure of a registry's exact input fields, it calls regdata_describe first, then runs the tool.

Pricing

Pay-per-result on Apify, no subscription - from ~$0.003/result depending on actor and plan tier. The $5 monthly free credit covers hundreds to ~1,600 lookups. Each actor's current price is on its Store page at apify.com/regdata.

How it works

The server calls Apify's run-sync-get-dataset-items endpoint for each actor and returns the dataset items as JSON. No data passes through any third party - it is your token, the Apify platform, and the official registry source.

Local development

npm install
npm run smoke          # verify all tools load with real input schemas
APIFY_TOKEN=xxx npm start

License

MIT - part of github.com/Nolpak14/getregdata.