The fields that come back are the ones a due-diligence question turns on — registered capital, the auditor, legal representatives, mergers and acquisitions, former names — arriving together rather than across separate pages. Matching is where the parameters earn their place: phoneticSearch and exactSearch cover the difference between a name you half-remember and one you must hit precisely, and includeFormerNames covers a company that has since renamed itself. It is published as the package zefix-mcp-unofficial, so the register remains the authority and this is a client onto it.
A company register lookup: one search call that resolves a name or a UID and returns the register record as semi-structured markdown.
- The register record in a single response: get_companies returns legal names, address, business identifiers, names of legal representatives, registered capital, mergers and acquisitions, auditor, purpose, former names, and the history of changes for the company it resolves.
- A query you shape with parameters rather than a query language: name_or_uid accepts either form of identifier, while cantons, legalForms and locations narrow the search.
- Control over how the name is matched: exactSearch and phoneticSearch select the matching behaviour, and includeFormerNames and includeDeleted are switches on what the search will return.
- Output in the language you need: language_key sets the language of the returned record.
Nothing — no account, no key.
One command — npx -y zefix-mcp-unofficial