Skip to main content
Glama
matematicsolutions

mcp-krs

by matematicsolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-krs

No user-submitted related servers found.

    Related Servers

    • krs-verify

      apiotrowski-afk
      A
      license
      Not graded
      quality
      D
      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

    • rejestr-io-mcp

      QuverLabs
      F
      license
      A
      quality
      C
      maintenance
      MCP server providing access to Polish business registers (KRS, CRBR) via the rejestr.io API, enabling search, retrieval of organizations, beneficial owners, financial documents, and more.
      12
      -

    • nip-krs-mcp

      bartosz-kuc
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Polish company registries that enables looking up companies by NIP or KRS using public government APIs with no authentication required.
      2
      MIT

    • mcp-polish-data

      emilpinski
      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

    • mcp-wl-vat

      pwasniowski
      A
      license
      A
      quality
      B
      maintenance
      MCP server for querying the Polish VAT taxpayer white list via the official Ministry of Finance API. Enables search by NIP, REGON, or bank account, and verification of NIP-bank account pairs, with built-in daily limit protection.
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct use case: get_board for quick board composition summary, get_entity for current full entity data, and get_entity_full for historical records. There is no ambiguity or overlap between them.

    Naming Consistency5/5

    All tool names follow a consistent get_ prefix pattern with snake_case (get_board, get_entity, get_entity_full), making the naming predictable and easy to understand.

    Tool Count5/5

    Three tools is an appropriate number for a specialized KRS data retrieval server. Each tool serves a distinct purpose covering the main query needs without being excessive or too sparse.

    Completeness4/5

    The tools cover the main read operations for KRS entities (current data, full history, board summary). However, a search tool by name or NIP is missing, which would be a natural complement for a complete data retrieval surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources