What the Polish KYB MCP server does
The Polish KYB MCP server provides read-only company due-diligence queries through Compabase. It is designed for checking Polish businesses using registry and public-record information rather than changing records or submitting filings.
The service can locate a company and return its KRS profile and VAT status. It can also identify management and supervisory board members, shareholders, and beneficial owners recorded in the Central Register of Beneficial Owners (CRBR). Additional checks cover insolvency and restructuring proceedings in KRZ, Court and Commercial Gazette notices in MSiG, sanctions lists, and the KNF financial supervision register.
The remaining company records concern secured liabilities and articles of association. Together, these tools support structured review of a Polish counterparty from an MCP-compatible AI client.
How it works
The Polish KYB MCP server is a hosted remote MCP service using Streamable HTTP. Its endpoint is:
https://compabase.com/api/mcp/kyb
An MCP client sends requests to that endpoint, and the model can select the relevant read-only tool. Example checks include finding a company by NIP, looking up beneficial owners by KRS number, or checking whether a business appears in insolvency or sanctions records.
The tool names documented by the service include search_companies, get_company_people, get_company_debt_registry, get_company_court_gazette, get_company_sanctions, and get_company_secured_liabilities. The README also lists related aliases such as get_company, get_company_beneficiaries, get_company_financial_supervision, and get_company_articles.
Setup and configuration
Connect the endpoint in an MCP client that supports remote HTTP servers. Clients documented in the README include Claude, Cursor, VS Code, Windsurf, ChatGPT, and Gemini CLI; setup guides are also provided for Claude Code and several other products.
Authentication can use Compabase OAuth where the client supports it. Alternatively, create an MCP key in Compabase and provide it as an HTTP bearer header:
Authorization: Bearer mcpk_YOUR_KEY
The key may also be supplied as an apiKey URL parameter. For clients using an MCP configuration file, the service’s example uses the endpoint under a named server and places the bearer key in a headers object. Gemini CLI requests the Compabase key during extension installation. Queries are counted against the Compabase plan.
Limitations and notes
The Polish KYB MCP server is read-only, so the documented capabilities are retrieval and checking rather than updates to company records. Access requires Compabase authentication through OAuth or an MCP key. The endpoint is hosted by Compabase, and use is subject to the query limits or plan terms associated with that account.
The service focuses on Polish company information: KRS and VAT status, company people and CRBR ownership, KRZ proceedings, MSiG notices, sanctions, KNF supervision records, secured liabilities, and articles of association. Choose another integration if the required source or operation is not represented by these tools.