Every official registry, as tools your agent can call.
One MCP server exposes 38 tools over 35 government and court registries in 16 jurisdictions. Ask in natural language; the agent resolves beneficial owners, insolvency filings and adverse media from the official source.
$ npx -y getregdata-mcp Three steps. Five minutes.
The server runs the actors in your own Apify account, so all it needs is your token. Nothing is stored on our side.
Sign up at Apify and copy your API token. New accounts include $5 of credits - no card required.
One command in Claude Code, or one config block in Claude Desktop, Cursor, Cline or Windsurf.
“Resolve the beneficial owners of NIP 6770065406 and check them against the debtor register.”
Five questions that work today.
Paste any of these into your agent once the server is connected. It picks the registries and chains the calls.
38 tools, grouped by jurisdiction.
Two helpers handle routing. The other 35 each read one official registry.
REGISTRIES 35
JURISDICTIONS 16
regdata_catalog Lists every registry tool and what it returns, so the agent can pick before it spends.
regdata_describe Fetches an actor’s live input schema so the call is constructed correctly the first time.
regdata_poland_kyb_check One call: identity, beneficial owners and insolvency screened against the company and every owner, as a single verdict.
regdata_crbr_beneficial_owners Ultimate beneficial owners from the Central Register of Beneficial Owners.
regdata_poland_krs_financial Annual financial statements and filings from the National Court Register.
regdata_krs_fullnames Management and board members registered in the National Court Register.
regdata_krz_debtor Insolvency and restructuring entries from the National Debtor Register.
regdata_ekw_ksiegi_wieczyste Ownership and mortgage entries from the electronic land and mortgage register.
regdata_polish_regon Company identity, PKD activity and status from the official GUS registry.
regdata_knf_registry Regulated financial entities from the KNF supervision registers.
regdata_msig Official court and commercial announcements from Monitor Sądowy i Gospodarczy.
regdata_uokik_clauses Abusive contract clauses from the UOKiK consumer-protection registry.
regdata_bdo_waste_registry Waste-management registration entries from the BDO database.
regdata_poland_parliamentary_pep Politically exposed persons from the Polish parliament for KYC/AML screening.
regdata_polish_premises Local units and premises (jednostki lokalne) from the REGON registry.
regdata_borme_corporate_acts Corporate acts and appointments from the official BORME gazette.
regdata_spain_company_directory Company register search for Spain - identity and directory data referencing the Registro Mercantil.
regdata_spain_concursal Insolvency and disqualification entries from the public insolvency register.
Before you wire it in.
Do I need an Apify account? +
Yes. The MCP server runs the registry actors in your own Apify account, so it needs an APIFY_TOKEN. Signing up is free and new accounts include $5 of credits, which is enough to trial every tool.
What does it cost? +
The MCP server itself is free and open source. You are billed by Apify only for the records you actually pull, at each actor’s published per-result rate. There is no subscription and no seat cost.
Where does the registry data go? +
Into your Apify account. The actors run under your token and the results land in your dataset. getregdata never receives, stores or warehouses the records you pull, which means you remain the data controller for anything you query.
Which MCP clients are supported? +
Any client that speaks the Model Context Protocol over stdio - Claude Code, Claude Desktop, Cursor, Cline, Windsurf. The server is listed on the official MCP Registry as io.github.Nolpak14/getregdata. Hosted clients that need a remote endpoint (claude.ai web, ChatGPT developer mode, Gemini) connect via Apify’s hosted MCP server at mcp.apify.com with OAuth, where every regdata registry is available as a tool.
How does the agent know which registry to use? +
Three helper tools do the routing. regdata_catalog lists all 35 registry tools and what each returns, and regdata_describe fetches an actor’s live input schema so the model can construct a correct call before it spends anything. regdata_run_result collects a check that was still running when its call returned - long checks hand back a runId rather than failing, so a slow run is never a charge without a result.
Is the data official? +
Every tool reads a named government or court registry at query time - never a resold aggregator - and the source registry travels with the record, so any answer your agent gives can be traced back to its filing.