Zefix MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CACHE_TTL | No | Default cache lifetime in seconds; some API methods use their own TTL. | 3600 |
| LOG_LEVEL | No | Pino log level: trace, debug, info, warn, error, or fatal. | info |
| CACHE_ENABLED | No | Set to true to enable the in-memory response cache. | false |
| UID_PUBLIC_URL | No | UID Public Services WSDL. | https://www.uid-wse.admin.ch/V5.0/PublicServices.svc?wsdl |
| ZEFIX_BASE_URL | No | Zefix REST API base URL. | https://www.zefix.admin.ch/ZefixPublicREST/api/v1 |
| ZEFIX_PASSWORD | Yes | Your Zefix API password. | |
| ZEFIX_USERNAME | Yes | Your Zefix API username. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_companiesA | Search for Swiss companies using the Zefix API. Supports filtering by name, canton, legal form, and active status. Names match by prefix; start with * to match anywhere. Zefix rejects searches that match too many companies (e.g. ab), so add canton or legalFormUid or use a more specific name. |
| get_company_by_uidC | Get detailed company information from Zefix by UID. Optionally enriches data with UID Webservice information. |
| advanced_searchC | Advanced company search using the UID Webservice. Supports multiple filters including person names, legal forms, and canton. |
| validate_uidB | Validate a Swiss UID (Unternehmens-Identifikationsnummer) using the UID Webservice. Checks if the UID exists in the official register. |
| validate_vat_numberB | Validate a Swiss VAT (MWST) number using the UID Webservice. Checks if the VAT number is valid and currently active. |
| get_daily_registrationsA | Get company registrations and publications from SOGC (Swiss Official Gazette of Commerce) for a specific date using the Zefix API. A day has ~1,000 publications, so results are compact summaries; filter by canton and mutationType, page with offset, and set includeText for the full publication text. |
| get_company_publicationsA | Get SOGC publications for a specific company by UID using the Zefix API, most recent first; page with maxResults and offset. |
| generate_due_diligence_reportC | Generate a due diligence report for a Swiss company using Zefix and UID Webservice data. |
| get_company_details_uidB | Get detailed company information using only the UID Webservice. This does not require Zefix authentication. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools have distinct purposes: validation of UID vs VAT, daily vs company publications, and Zefix vs UID Webservice detail lookups. However, search_companies and advanced_search overlap in company search, and get_company_by_uid and get_company_details_uid both retrieve company details from different sources, which could cause some selection hesitation.
The set mostly follows a snake_case verb_noun pattern such as validate_uid, get_company_by_uid, and generate_due_diligence_report. The main deviation is advanced_search, which is adjective_noun rather than verb-first, and get_company_details_uid puts the source qualifier after the noun.
Nine tools is well-scoped for a Swiss company registry and validation server. Each tool covers a distinct data source or operation area without excessive surface area.
The server covers the full read-only lifecycle: UID and VAT validation, company search and advanced search, company details via both Zefix and UID Webservice, daily and company-specific publications, and a due diligence report. No obvious operational gaps exist for the stated registry lookup domain.