Skip to main content
Glama
ishumilin

Zefix MCP Server

by ishumilin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Zefix MCP Server

No user-submitted related servers found.

    Related Servers

    • swissco by prospex-ch

      swisscoofficial

      prospex-ch
      A
      license
      A
      quality
      B
      maintenance
      An MCP server for Swiss company data. Nine tools that look a company up by UID, search 790,000 of them by name or by statutory purpose, trace what changed in the commercial register, browse public tenders, check a bank licence, resolve a UID to an LEI and its group parent, and find federally funded research a company took part in. Built by https://prospex.ch
      9
      MIT

    • register-mcp

      malkreide
      A
      license
      A
      quality
      A
      maintenance
      Provides access to the Swiss Federal Commercial Register (Zefix) for company search, verification, and reference data, enabling natural language queries for public administration use cases.
      9
      MIT

    • bexio-mcp

      valmiremini
      A
      license
      A
      quality
      C
      maintenance
      A standalone MCP server for the bexio REST API, enabling interaction with bexio resources like contacts, invoices, and projects through natural language from any MCP client.
      21
      4 npm
      MIT
    • bexio-mcp by nolen-ai

      bexio-mcpofficial

      nolen-ai
      A
      license
      A
      quality
      A
      maintenance
      MCP server for the bexio API, enabling interaction with contacts, sales, accounting, projects, and more through 35 tools. Supports both PAT and OAuth authentication with read-only mode and tool group filtering.
      35
      4 npm
      3
      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

    B3.4/5.0

    Scored across 9 tools

    Disambiguation3/5

    There is notable overlap between 'get_company_by_uid' and 'get_company_details_uid' (both retrieve company details via UID but from different sources), as well as between 'search_companies' and 'advanced_search' (both perform searches with slightly different filter sets). While descriptions clarify differences, an agent could easily select the wrong tool in many scenarios.

    Naming Consistency3/5

    Tool names predominantly follow a verb_noun pattern, but inconsistencies exist: 'advanced_search' uses an adjective prefix instead of a verb, while 'get_company_by_uid' and 'get_company_details_uid' include prepositions in the noun part. The mix of 'search_' and 'get_' verbs is acceptable, but the varying structures reduce predictability.

    Tool Count5/5

    With 9 tools, the set is well-scoped for a Swiss company registry server. Each tool addresses a distinct functional need (search, details, validation, publications, report generation) without unnecessary bloat or missing essential operations for this domain.

    Completeness5/5

    The tool surface covers all typical use cases for a read-only company registry: searching, retrieving detailed company info (via two complementary services), validating identifiers (UID and VAT), fetching publications and daily registrations, and generating due diligence reports. No obvious gaps are present.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources