krs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_companiesA | Search Polish companies in the KRS (National Court Register) by name or partial name ("query"), KRS, NIP or REGON. Returns matching entities with their padded 10-digit KRS numbers — use this FIRST to resolve a company name to a KRS number before calling get_company / get_company_full / get_board. |
| get_companyA | Fetch the CURRENT (aktualny) official extract of a Polish company from the KRS registry by its 1-10 digit KRS number. Returns identity, address, board, capital and PKD as markdown. |
| get_company_fullA | Fetch the FULL (pelny) official semantic JSON extract of a Polish company from the KRS registry by its 1-10 digit KRS number. Preserves all historical entries. Much larger than the current extract; use get_company unless history is needed. |
| get_boardA | List the board, supervisory bodies and proxies of a Polish company from its current KRS extract. Resolve the KRS number first with search_companies. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
search_companies is clearly a resolver, and get_company vs get_company_full are distinguished by current vs historical and markdown vs JSON output. get_board overlaps noticeably with get_company, which already returns the board, though the description hints at extra supervisory-body/proxy detail.
All four names are lowercase snake_case following a verb_noun pattern (search_companies, get_company, get_board). The _full suffix on get_company_full is a readable, predictable variant rather than a convention break.
Four tools is a tight, well-scoped surface for a registry lookup server: one resolver plus three targeted retrieval variants. Nothing feels redundant or padded.
Core lifecycle is covered: search by name/KRS/NIP/REGON, current extract, full historical extract, and board data. Minor gaps remain—no shareholder/beneficial-owner or financial-statement retrieval, and search lacks PKD/address filtering—but agents can work around these.