KRS Poland MCP Server
Related Servers
Alternatives to KRS Poland MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables 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
- 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.202 npmMIT
- AlicenseAqualityBmaintenanceMCP server for the Polish company register (KRS) via the official Ministry of Justice API — entities, boards and shareholders with verifiable citations.3112 npm1MIT
- FlicenseNot gradedqualityDmaintenanceProvides access to Poland's largest business registry database, enabling company search, beneficiary checks, and financial document retrieval via natural language.1-
- AlicenseNot gradedqualityDmaintenanceMCP server for verifying Polish business entities from the National Court Register (KRS) and VAT White List. Allows querying by KRS, NIP, or REGON to retrieve official company data including name, address, board, and capital.Apache 2.0
- AlicenseAqualityDmaintenanceEnables querying the Polish KNF e-RUP payment institution registry, including entity search, details, services, agents, branches, and history.8MIT
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.