A Swiss UID can survive multiple commercial register changes without breaking legal continuity. That trips people up during cross-border diligence, especially after a canton migration or a GmbH-to-AG conversion ahead of a financing round.
Zefix, Switzerland’s central business index, exposes more than a company search page. The register ties cantonal Handelsregister records together through a federal UID structure, which makes entity tracing less fractured than many finance teams assume.
For IPO diligence or AML reviews, the useful bit sits in the metadata attached to each entity record.
Fields that matter during Swiss entity checks
A standard get_company_profile call for Switzerland returns core identifiers plus canton-level Handelsregister data.
The unified schema includes:
- company name
- legal form
- registry status
- registered address
- incorporation date
- canton code
- UID number
- commercial register number
The upstream jurisdiction_data payload from Zefix also carries fields that become useful during reconciliation work:
uidehraidregistryOfCommerceCantonlegalSeatpurposestatusdeletionDate
purpose turns out to be unusually valuable during counterparty reviews. Swiss entities often describe operating activity in much more detail than equivalent UK SIC filings. A commodities subsidiary may spell out treasury activity, shipping operations, or financing mandates directly in the corporate purpose text.
Canton linkage matters too. Zug, Geneva, Zurich, and Ticino attract noticeably different mixes of holding companies and treasury vehicles. During ownership-chain mapping, the canton often gives quicker context than the company name itself.
OpenRegistry does not reinterpret any of these fields. The MCP server returns the upstream register structure directly, so extraction logic and classification stay inside the client application or assistant.
What Swiss registry data does not include
Switzerland still separates several high-value compliance datasets from the public commercial register.
You will not get beneficial ownership data comparable to AMLD5 public UBO systems because Zefix does not expose a broad public beneficial-owner register. Nominee arrangements, indirect control structures, and trust relationships still need document review outside the registry.
OpenRegistry also does not provide sanctions screening, PEP matching, or credit scoring.
Historical snapshots are another gap. Every request hits the live upstream source. If a director resigns today, the current state updates immediately. OpenRegistry does not maintain archived registry states.
Filing depth varies by canton as well. Some cantonal registers expose richer filing histories and publication references than others. During M&A diligence, material events still need cross-checking against SHAB publications and audited accounts.
Querying Swiss companies through MCP
The Swiss register is available through the OpenRegistry MCP endpoint.
A basic entity search looks like this:
{
"tool": "search_companies",
"arguments": {
"jurisdiction": "CH",
"query": "Glencore"
}
}
Once the target entity is identified, you can request the full profile:
{
"tool": "get_company_profile",
"arguments": {
"jurisdiction": "CH",
"company_number": "CH-170.3.027.129-9"
}
}
Swiss commercial register numbers are canton-specific, so formatting matters. Removing punctuation can break reconciliation against legal opinions, LEI records, or banking onboarding systems.
If filing metadata is exposed, recent registry activity can be queried directly:
{
"tool": "list_filings",
"arguments": {
"jurisdiction": "CH",
"company_number": "CH-170.3.027.129-9"
}
}
That becomes useful during financing events where authorised signatory changes or board rotations need tying back to a specific filing window.
Swiss registry quirks that show up in diligence
Swiss entities often sit inside layered holding structures spanning Zug, Luxembourg, the Caymans, plus Dutch financing vehicles. Zefix gives you the Swiss node of the structure, not the full ownership graph.
The interesting details usually sit inside status changes or legal-form transitions.
We ran into this during a review of a debt issuer that converted from GmbH to AG shortly before issuance. The operating business stayed the same. Governance mechanics changed materially because of the legal-form conversion. Registry status fields also expose dormant entities that still appear in active financing arrangements.
Language creates another operational problem. Registry entries may contain German, French, or Italian terminology depending on the canton. Pipelines built around English-only officer titles tend to misclassify Swiss signatories.
Returning the raw upstream structure helps. Finance teams can apply their own translation rules and internal classifications instead of depending on pre-processed labels pulled from stale aggregator exports.
Where this fits in KYB workflows
Swiss onboarding failures often happen at entity resolution rather than sanctions screening.
Treasury teams need to verify that the issuer named in loan documentation matches the entity recorded in the canton register. M&A analysts need to separate an active operating subsidiary from a dissolved holdco carrying a similar trading name. Compliance teams need registry pulls tied to filing dates, then stored as part of the audit trail.
Direct MCP access changes that workflow. Instead of copying records manually from cantonal portals into spreadsheets, the register query becomes part of internal tooling or assistant workflows.
OpenRegistry currently serves Switzerland alongside jurisdictions including GB, FR, NL, KY, HK, and RU through the same MCP interface. Current coverage and live jurisdiction status are listed at https://openregistry.sophymarine.com/mcp
Top comments (0)