Skip to main content
Glama

Related Servers

Alternatives to krs-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP 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
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides access to Poland's largest business registry database, enabling company search, beneficiary checks, and financial document retrieval via natural language.
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI assistants access to Polish public registers, enabling company lookups in KRS, VAT whitelist and bank-account checks, KRS extract retrieval, and offline validation of NIP, REGON, KRS, NRB, and KW numbers.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server providing AI assistants access to Polish public registries (KRS, CEIDG) and statistical data (GUS BDL) for querying companies, sole proprietorships, and regional statistics.
      7
      MIT

    TDQS

    A4.1/5.0

    Scored across 4 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessLimited data