Skip to main content
Glama
przemonides

CRU MCP Server

by przemonides

Related Servers

Alternatives to CRU MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Ukrainian public procurement (Prozorro) that exposes tools to search tenders, retrieve tender details and cards, list and read tender documents.
      -
    • A
      license
      A
      quality
      B
      maintenance
      MCP server that provides access to Polish individual tax interpretations (KIS) via the official EUREKA API, enabling search and retrieval of rulings with signatures, theses, and full text.
      4
      4
      MIT
    • 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
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for the Polish company register (KRS) via the official Ministry of Justice API — entities, boards and shareholders with verifiable citations.
      3
      214 npm
      1
      MIT
    • 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

    TDQS

    A4.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one searches for contracts with various filters, the other retrieves full details of a specific contract. No overlap or ambiguity.

    Naming Consistency5/5

    Both tool names follow a consistent pattern: 'rejestr_umow_' prefix with a verb (search/get) followed by 'contracts' or 'contract'. The naming is predictable and unambiguous.

    Tool Count4/5

    With only 2 tools, the server is minimal but well-scoped for a read-only registry query domain. It feels slightly thin, but each tool serves a distinct purpose without unnecessary bloat.

    Completeness5/5

    For a read-only contract registry, the pair of search and get detail covers the essential functionality completely. No obvious gaps—users can find contracts and retrieve full information.

    Maintenance

    ActivityStale
    ResponsivenessNo issues