KRS Poland MCP Server
This server exposes read-only KRS lookup tools for Polish court-register entities.
Fetch the current KRS extract (odpis aktualny) as JSON using a 10-digit KRS number and register
P/S.Fetch the full KRS extract (odpis pełny), including complete entry history, using a KRS number and register
P/S.Run it as an MCP tool provider via
npx; README notes a 10-minute in-memory cache by default.Note: README documents additional tools and a prompt, but the provided schema exposes only the two extract tools.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@KRS Poland MCP Server Show me the current KRS record for KRS 0000123456"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.

KRS Poland MCP Server
An MCP server for the Polish National Court Register (KRS) public API.
Usage
This server is designed to be run with npx, allowing you to use it as a tool provider for LLM clients without a global installation.
Running with npx
Requires Node.js 18 or newer (tested on 22 and 24 in CI).
To start the server, run the following command:
npx krs-poland-mcp-serverConfiguration for LLM Clients
To integrate this server with an LLM client (like LM Studio or others that support MCP), you can configure it to spawn the server process. Here is an example configuration:
{
"mcpServers": {
"krs-poland-mcp-server": {
"command": "npx",
"args": [
"-y",
"krs-poland-mcp-server"
]
}
}
}This configuration tells the client how to start the KRS tool server.
Cache
Responses of the KRS API are kept in memory for 10 minutes (up to 50 most recently used requests), so the status check, the profile and the history of the same entity do not download its extract again. Set KRS_CACHE_TTL_SECONDS in the server's environment to change the lifetime, or to 0 to turn the cache off:
"env": { "KRS_CACHE_TTL_SECONDS": "0" }Related MCP server: mcp-krs
Server Functions
The server provides the following tools (checklist):
Get Current KRS Record (
get-krs-current-extract): Returns the raw current extract (odpis aktualny) of an entity as JSON. The register (P/S) is optional; both are checked when it is omitted.dzialylimits the answer to selected sections (see below).Get Full KRS Record (
get-krs-full-extract): Returns the raw full extract (odpis pełny) — current data plus the complete history of entries — as JSON; also available for entities struck off the register. The register (P/S) is optional. Withdzialyonly the selected sections are returned, and the list of entries in the header is narrowed to the entries that introduced or struck out their fields.The full extract of a large company is long — ORLEN S.A. (KRS 0000028860) has about 212,000 characters as single-line JSON, of which section 2 alone is about 86,000. The sections (
dzialy, numbers 1–6) are: 1 — the entity: name, seat and address, capital, shareholders, branches; 2 — representation: the board and how it acts, supervisory board, commercial proxies, attorneys; 3 — PKD activity codes, filed financial statements, end of the financial year; 4 — arrears, receivables, asset security, dismissed bankruptcy petitions; 5 — court-appointed curator; 6 — liquidation, dissolution, bankruptcy, restructuring, mergers, divisions, transformations, suspension of business. Example arguments:{ "krs": "0000028860", "rejestr": "P", "dzialy": [2] }Check KRS Status (
check-krs-status): Checks whether an entity is active and returns a compact report of risk signals found in its register entry — liquidation, bankruptcy, restructuring, suspension, dissolution, arrears with enforcement, asset security, dismissed bankruptcy petitions, court-appointed curator, missing board, overdue annual financial statements, a NIP revoked by the tax office for a false or fictitious address (critical) or annulled (warning), and deletion from the register. The register (P/S) is optional; both are checked when it is omitted.Get KRS Entity Profile (
get-krs-entity-profile): A compact profile of the entity from its current extract — NIP/REGON with NIP status, seat and address, contact and e-delivery address, share capital, representation (the board's composition by function and the rule for acting on the entity's behalf, commercial proxies, attorneys, liquidators when applicable), supervisory board, owners (companies are named, people are not), PKD codes, the purpose and public-benefit status of associations, branches, and a one-line status assessment. Personal data is never returned. The register (P/S) is optional.Get KRS Entry History (
get-krs-entry-history): Returns a compact history of the entity's register entries, computed from the full extract (which for large companies runs to hundreds of thousands of characters). By default it lists entries newest first — date, description, case reference and the fields each entry changed — optionally filtered withodDaty(dd.mm.yyyyoryyyy-mm-dd) andlimit(default 20, max 100). WithnumerWpisuit shows what that single entry introduced, struck out and changed: name, address, capital, board members, PKD codes and so on. Works for entities struck off the register as well; the register (P/S) is optional.Check KRS Watchlist (
check-krs-watchlist): Takes up to 50 watched KRS numbers and a day (data) or a date range (odDaty/doDaty, up to 31 days;doDatydefaults to today) and tells which of the entities had an entry in the register in that period, based on the daily KRS bulletin. For each such entity it returns the bulletin days and — unlessszczegolyisfalse— its name, last register entry (number, date, case reference, court; for an entity struck off also the entry description) and the status assessment ofcheck-krs-status. Entities without entries and bulletin days that could not be fetched are listed separately.Example arguments:
{ "krs": ["0000019193", "0000109411"], "odDaty": "2026-11-01", "doDaty": "2026-11-12" }
Prompts
Weryfikacja kontrahenta w KRS (
weryfikacja-kontrahenta): argumentskrs(required),rejestrandkontekst(e.g. "umowa dostawy na 200 tys. zł"). Walks the model through the entity profile, the status check and the last 12 months of register entries, and asks for a report with a green/yellow/red assessment and a plain answer to who can sign a contract on the entity's behalf.
All tools are read-only and none of the analytic tools return personal data of natural persons (the KRS API masks names and PESEL numbers but not, for example, birth dates).
Development
To run the server in a development environment:
Clone the repository.
Install dependencies:
npm installBuild the project:
npm run buildRun the server:
npm start
Author
Piotr Kolawa (@pkolawa) / (Linkedin)
License
This project is licensed under the MIT License - see the LICENSE file for details.
Available Tools
2 toolsGet_Current_KRS_Recordget-krs-current-extractB
Get current status of the entity in KRS
Inputs: krs (required), rejestr (required).
Get_Full_KRS_Recordget-krs-full-extractC
Get full status of the entity in KRS
Inputs: krs (required), rejestr (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
Both tools retrieve KRS records, and their names ('Current' vs 'Full') are unclear in differentiation. Descriptions do not explain what additional data 'Full' provides, leading to potential confusion for an agent.
Both tools use 'Get_' prefix with PascalCase, which is consistent. However, the second word ('Current' vs 'Full') is somewhat arbitrary and not part of a clear pattern (e.g., Get_Current vs Get_Full).
With only 2 tools, the server is very narrowly scoped. This can be appropriate if the sole purpose is retrieving two variants of a record, but it feels thin for a typical MCP server.
Only retrieval operations are provided, lacking search, creation, or updates. If the domain requires any interaction beyond fetching records, the tool surface is severely incomplete.
Maintenance
Related MCP Connectors
Polish company records from the official KRS register API, with alerts on new registry entries.
Polish company data from KRS: profiles, historical connections, financials, state aid.
Polish companies and people: KRS, CEIDG, financials, boards, VAT, sanctions. Free, no API key.
Polish company registry: 4.4M firms, KRS/REGON data, VAT white list checks, financial statements
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceProvides access to Poland's largest business registry database, enabling company search, beneficiary checks, and financial document retrieval via natural language.1-
- AlicenseAqualityCmaintenanceMCP server for the Polish company register (KRS) via the official Ministry of Justice API — entities, boards and shareholders with verifiable citations.3148 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables looking up Polish companies by NIP, REGON, or KRS number to retrieve their registered name, legal address, and entity type from Statistics Poland's official register.78 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to look up Polish company registry data from KRS, including registry profiles, current and historical board, shareholder and proxy connections with dates, change timelines, financial statements, state aid and public contracts. All tools are read-only and reachable over a remote Streamable HTTP endpoint, with the same data also exposed through a REST API.MIT