Get_Current_KRS_Record
Get current status of the entity in KRS
LABSCO SUMMARY
It answers one question — what does the KRS hold on this entity — and lets you choose between the current record and the full one.
Get_Current_KRS_Record and Get_Full_KRS_Record take identical inputs, krs and rejestr, so the decision is purely about which depth of record the task needs rather than about how to ask. Neither call takes a company name, which means the KRS number has to be known before either one can run: this fits after whatever supplies that number, not in place of it.
What it is
A lookup onto Poland's KRS register, exposing an entity's current record and its full record for a given KRS number.
What you get
- Get_Current_KRS_Record returns the entity's current KRS record for a krs number within the named rejestr.
- Get_Full_KRS_Record returns that entity's full KRS record from the same krs and rejestr inputs.
Requirements
Nothing — no account, no key.
Setup effort
One command — npx -y krs-poland-mcp-server
USE CASES
01
Verifying a Polish counterparty against the register
Take the KRS number you were given and read the entity's entry back, at whichever depth the check calls for.
2 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
Get_Full_KRS_Record
Get full status of the entity in KRS
BEFORE YOU INSTALL
What to know first
Tools you get
2 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"krs-poland-mcp-server": {
"command": "npx",
"args": [
"-y",
"krs-poland-mcp-server"
]
}
}
}npx
TERMINAL
npx -y krs-poland-mcp-server
