Vetari

ch.vetariPublished by vetari.chOfficial publisherv1.0.0Updated Oct 24, 2026

Swiss company-register intelligence: new GmbHs by canton, shared addresses, UID history, SHAB text

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Vetari gives an assistant Swiss company-register intelligence: new GmbHs by canton, shared addresses, UID history and SHAB text.

What you can do
  • Look up Swiss company-register data: new GmbHs by canton, shared addresses, UID history and SHAB text.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
  • Access is through a hosted remote endpoint rather than a local package.
When to use it
Useful when you need to research Swiss companies, track new incorporations by canton, check shared addresses or UID history, or read SHAB notices while working in an assistant.
Requirements
A remote MCP endpoint at api.vetari.ch over streamable HTTP. Authentication is required: either OAuth sign-in (login.vetari.ch, discovered automatically) or a Vetari MCP API key sent in the X-API-Key header. Either way needs a Vetari account; the free tier is enough to try it.
Before you install
You must supply a Vetari account and either OAuth sign-in or an API key in the X-API-Key header; treat that key as a secret. Queries about companies and addresses go to a third-party service. No write, payment or deletion behaviour is described in the available information.

Installation

In SourceWeft

  1. Open Vetari in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ch.vetari%2Fvetari/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "vetari": {
      "type": "http",
      "url": "https://api.vetari.ch/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.0LatestOct 1, 2026
  2. v0.1.0Sep 26, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.