Skip to main content
Glama
Kymylyy

e-RUP KNF MCP Server

by Kymylyy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to e-RUP KNF MCP Server

No user-submitted related servers found.

    Related Servers

    • regon-pl

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      13 npm
      MIT

    • PolishOpenData.Mcp

      JacekSmi
      A
      license
      Not graded
      quality
      A
      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

    • Rejestr.io MCP Server

      KolegaLiterat
      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
      -

    • regon-mcp

      SmartMobileHouse
      A
      license
      A
      quality
      A
      maintenance
      Provides clean, typed access to the Polish REGON business register (GUS BIR1), enabling AI assistants to look up companies by NIP, REGON, or KRS and retrieve structured data like name, address, and legal form.
      6
      1
      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

    A3.5/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of e-RUP entities (details, agents, branches, history, services) plus registry-level operations (search, stats, types). There is no ambiguity or overlap.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., get_entity, get_entity_agents, search_entities). The naming is predictable and uniform.

    Tool Count5/5

    With 8 tools covering entity retrieval, sub-resources, search, and stats, the count is well-scoped for a read-only registry lookup server. No extraneous tools.

    Completeness5/5

    The tool surface fully covers the domain of querying e-RUP entities: entity details, related data (agents, branches, history, services), search, counts, and type taxonomy. There are no obvious gaps for a read-only service.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources