OpenSwissData
REMOTE · MCP.OPENSWISSDATA.COM · 2 COMPONENTS
Swiss customs tariff (TARES), FINMA register, NOGA/NACE/ISIC codes. 3 free tools + search trial.
Available components
Last scanned (17 minutes ago)
Scores higher than 91% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security14
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Oct 26 +4
- Stability: fail → pass ▲ security
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 75.
- 12 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “company_check” rewrote its description, which is the text the model reads security
- 9 Oct 26 0
- Schema quality: 1561 → 1747 ▼ functional
- 6 Oct 26 0
- Tool “kyc_check” rewrote its description, which is the text the model reads security
- 29 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 765 → 1529 ▼ functional
- Tool coverage: 43% → 53% ▲ functional
- New tool “classify_text” functional
- New tool “finma_search” functional
- New tool “tariff_semantic_search” functional
- 28 Sept 26 0
- Tool “tariff_semantic_search” was removed ▼ security
- Tool “entity_history” was removed ▼ security
- Tool “finma_search” was removed ▼ security
- Tool “tariff_changelog” was removed ▼ security
- Tool “classify_text” was removed ▼ security
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “cross_walk” rewrote its description, which is the text the model reads security
- Tool “kyc_check” rewrote its description, which is the text the model reads security
- Tool “tariff_lookup” rewrote its description, which is the text the model reads security
- Tool coverage: 55% → 43% ▼ functional
- Schema quality: pass → fail ▼ functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- Server version: 0.2.0 → 0.3.0 functional
- “tariff_lookup” reworded the description of “hs8” cosmetic
- “cross_walk” reworded the description of “code” cosmetic
- “kyc_check” reworded the description of “name” cosmetic
- Tool “tariff_lookup” changed its title: Swiss customs tariff line (TARES) cosmetic
- Tool “cross_walk” changed its title: NOGA / NACE / ISIC code correspondence cosmetic
- Tool “kyc_check” changed its title: FINMA register and warnings list check cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.openswissdata.com/jsonrpc
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.openswissdata.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| openswissdata.com. | present | 63640 | 13 | Verified |
| mcp.openswissdata.com. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.openswissdata.com/jsonrpc | Unreachable | ||
| http (plaintext) | http://mcp.openswissdata.com/jsonrpc | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
classify_text NOGA 2025 classification of a business description (free trial, 20 calls per day) ~227
FREE TRIAL without a key: 20 calls per day per IP address in total for tariff_semantic_search, classify_text and finma_search. Each answer states the trial calls left; check every result on the NOGA publications of the Federal Statistical Office before use. Classify a business activity description (French, German, Italian or English) into the closest NOGA 2025 subclasses (6 digits) with their class (the NACE 2.1 class), official hierarchy and a similarity score, using a pinned multilingual mpnet model. A NOGA code as text lists its subclasses. Each answer states the index provenance and the classification reference version; combine with cross_walk for NACE, ISIC or NOGA 2008.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the returned labels; the search itself covers all four languages |
| scheme | string | – | – |
| text | string | yes | Business activity description in French, German, Italian or English, or a NOGA 2025 code (e.g. 62.10) |
| top_k | integer | – | – |
No output schema declared.
No examples provided.
company_check Swiss company check by UID ~150
Look up a Swiss company by its UID (CHE-xxx.xxx.xxx): commercial register data (LINDAS), FINMA register entries and LEI records (GLEIF), each fact with its source and, when known, the date it was read, plus exact cross-checks between sources and checks of the registered address against the official localities and streets directories (swisstopo, when published). No score. When available, the commercial register status (active, in liquidation or deleted, with the deletion date) is read from Zefix (OFRC). FOSC publications, SECO sanctions and officers are not covered.
| Name | Type | Req | Description |
|---|---|---|---|
| uid | string | yes | Swiss UID (CHE-xxx.xxx.xxx) |
No output schema declared.
No examples provided.
cross_walk NOGA / NACE / ISIC code correspondence ~122
Find correspondences between NOGA 2008, NOGA 2025, NACE 2.0, NACE 2.1 and ISIC 4 activity codes (Swiss, EU and UN classifications). Returns the exact or approximate relation, its sources and the documented path. Never chains two non-exact relations; a non-exact correspondence needs expert validation.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Source code, with or without dot (01, 6201, 47.91). |
| source | string | yes | – |
| target | string | yes | – |
No output schema declared.
No examples provided.
finma_search FINMA register fuzzy name search (free trial, 20 calls per day) ~217
FREE TRIAL without a key: 20 calls per day per IP address in total for tariff_semantic_search, classify_text and finma_search. Each answer states the trial calls left; check every result on the official FINMA register before use. Search the FINMA register by entity name, tolerant of case, accents, legal forms (AG, SA, Sàrl, GmbH, Ltd), ae/oe/ue spellings and one or two typos per word. Results are ranked exact, word start, whole word, prefix, substring, all words in any order, then typo guesses, each labelled with match_type. Set include_warnings=true to also search the FINMA warnings list. Each answer states the FINMA data version.
| Name | Type | Req | Description |
|---|---|---|---|
| include_warnings | boolean | – | Also search the FINMA warnings list |
| name | string | yes | Entity name, or a distinctive part of it (typos, accents and legal forms such as AG/SA/Ltd are tolerated) |
| top_k | integer | – | – |
No output schema declared.
No examples provided.
kyc_check FINMA register and warnings list check ~142
Search the FINMA register of supervised institutions and the FINMA warnings list by name (case- and accent-insensitive). Returns the closest top_k authorised entities and warning entries (exact name, then whole word, then substring; all words in any order as a fallback) with the total number of matches. Only an identical name is reported as a FINMA warning-list match; a merely similar name is listed separately, to verify, and is never called a match. Use it for basic counterparty screening; no result is not a compliance certificate.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Entity name (or a distinctive part of it) |
| top_k | integer | – | – |
No output schema declared.
No examples provided.
tariff_lookup Swiss customs tariff line (TARES) ~177
Look up the Swiss customs tariff (TARES). An 8-digit Swiss tariff number (dots allowed) returns the full line: designations in FR/DE/IT/EN, MFN duty, preferential regimes, restrictions and customs relief codes. A 2- to 7-digit HS prefix (for example the international HS6 code) lists the Swiss 8-digit lines under it. Every result carries an unofficial-copy notice that the agent must show to the end user.
| Name | Type | Req | Description |
|---|---|---|---|
| hs8 | string | yes | Swiss tariff number: 8 digits for one line (dots allowed, e.g. 8471.3000), or a 2- to 7-digit HS prefix (e.g. the international HS6 code 847130) to list the Swiss 8-digit lines under it |
| lang | string | – | – |
No output schema declared.
No examples provided.
tariff_semantic_search TARES search by goods description (FR/DE/IT/EN) (free trial, 20 calls per day) ~240
FREE TRIAL without a key: 20 calls per day per IP address in total for tariff_semantic_search, classify_text and finma_search. Each answer states the trial calls left; check every result on the official tariff at xtares.admin.ch before use. Find Swiss customs tariff (TARES) lines from a description of the goods in French, German, Italian or English, or from a tariff number. Each line is indexed with its official hierarchy (heading, intermediate texts, 8-digit line) in the four languages; ranking puts shared official words first and uses meaning (pinned multilingual mpnet model) as a tie-breaker and for synonyms. Returns the 8-digit code, its official path, a relative score, the TARES data version and the index provenance. Always inlines a non-official disclaimer.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the returned designations; the search itself covers all four languages |
| query | string | yes | Description of a good in French, German, Italian or English, or a Swiss tariff number (2 to 8 digits, dots allowed) |
| top_k | integer | – | – |
No output schema declared.
No examples provided.
How do I install the OpenSwissData MCP server?
OpenSwissData is a hosted endpoint at https://mcp.openswissdata.com/jsonrpc, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.openswissdata.com
claude mcp add --transport http cammac-creator-openswissdata 'https://mcp.openswissdata.com/jsonrpc'
What is the OpenSwissData MCP server?
OpenSwissData is an MCP server listed in the public MCP registry as io.github.cammac-creator/openswissdata. Swiss customs tariff (TARES), FINMA register, NOGA/NACE/ISIC codes. 3 free tools + search trial. This page covers its hosted endpoint (https://mcp.openswissdata.com/jsonrpc).
Is the OpenSwissData MCP server safe to use?
OpenSwissData scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the OpenSwissData MCP server expose?
OpenSwissData exposes 7 tools: tariff_lookup, kyc_check, company_check, cross_walk, tariff_semantic_search, and 2 more. Their descriptions and schemas cost roughly 1,275 tokens of context every time the server is loaded.
Does the OpenSwissData MCP server require authentication?
Its publisher declares no required credentials for OpenSwissData. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the OpenSwissData MCP server still maintained?
OpenSwissData is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.