Home / MCP registry index / swiss.openhelvetia/gateway
OpenHelvetia Gateway
swiss.openhelvetia/gateway in the official MCP registry.
Endpoint https://mcp.openhelvetia.swiss/mcp.
The registry describes it as: Swiss federal law (Fedlex) and political data (LINDAS) for agents, every answer with sources
We read its 65 tools on 2026-10-31. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http gateway https://mcp.openhelvetia.swiss/mcp{
"mcpServers": {
"gateway": {
"url": "https://mcp.openhelvetia.swiss/mcp"
}
}
}code --add-mcp '{"name":"gateway","type":"http","url":"https://mcp.openhelvetia.swiss/mcp"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.
Let Claude Code check servers as it adds them
With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.
claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
directory.get facts.badge facts.latest fedlex.check_in_force fedlex.check_quote fedlex.cite fedlex.compare_versions fedlex.detect_foreign_content fedlex.explore_node fedlex.extract_tables fedlex.find_related_topic fedlex.find_treaties fedlex.get_article_history fedlex.get_citations fedlex.get_consultation_documents fedlex.get_consultations fedlex.get_drafts fedlex.get_fga_documents fedlex.get_law_metadata fedlex.get_memorial fedlex.get_modifications fedlex.get_oc_act fedlex.get_references fedlex.get_structure fedlex.get_subdivisions fedlex.get_taxonomy fedlex.get_treaty_info fedlex.list_annexes fedlex.list_expressions fedlex.list_versions fedlex.parse_reference fedlex.read_article fedlex.read_document fedlex.resolve_consolidation_at fedlex.resolve_sr fedlex.resolve_vocabulary_label fedlex.search_law fedlex.search_text i14y.api_status i14y.get_concept i14y.get_data_service i14y.get_dataset i14y.get_dataset_distributions i14y.list_catalogs i14y.list_concepts i14y.list_data_services i14y.list_datasets i14y.list_public_services i14y.list_publishers i14y.search_catalog i14y.search_codelist_entries lindas.describe lindas.describe_cube lindas.dimension_values lindas.find_cube lindas.list_cubes lindas.list_versions lindas.observations lindas.resolve_label manifest.get and 5 more
Tool changes
We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.
Fingerprint of its tools at our last full read (2026-10-31):
9c900434f8993d27. A client can hash the tools it is served the same way and compare;
the full value and a hash per tool are in this page as JSON.
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/swiss-openhelvetia-gateway)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.