Is ch.swisslivingindex/swiss-living-index up? Live MCP status
Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.
| Endpoint | https://swisslivingindex.ch/mcp |
|---|---|
| Page built |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Published, does not validate: an A2A 0.3 card: no `supportedInterfaces`, which 1.0 requires in place of `url` and `protocolVersion`. A2A 0.3 shape; 48 skills; mcp-streamable-http./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://swisslivingindex.ch/mcp/server-card |
| MCP server card (SEP-1649 location) | Not published (HTTP 404)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://swisslivingindex.ch with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 39 tools: book_consultation, cheapest_health_insurer, commune_tax, commute_cost, compare_cantons, compare_health_insurers, estimate_net_move, ev_charging_near, fuel_prices_near, get_canton, get_commune, get_dataset, get_electricity_price, get_family_tax_deductions, get_housing_costs, get_minimum_wage, get_payroll_rates, get_premium_subsidy, get_reference_rate, get_salary, get_trend, health_deductible_advice, health_premium_increase, household_budget, leaving_switzerland, list_datasets, list_metrics, naturalisation_timing, pension_figures, permit_types, pillar3a_tax, plan_move, rank_by_metric, recommend_canton, salary_by_occupation, search_commune, switch_health_insurer, tax_by_commune, upcoming_votes.
Its tools changed between 2026-09 and 2026-10:
- Added (28):
cheapest_health_insurer,commute_cost,compare_health_insurers,ev_charging_near,fuel_prices_near,get_commune,get_dataset,get_electricity_price,get_family_tax_deductions,get_housing_costs,get_minimum_wage,get_payroll_rates,get_premium_subsidy,get_reference_rate,get_salary,health_deductible_advice,health_premium_increase,household_budget,leaving_switzerland,list_datasets,naturalisation_timing,pension_figures,permit_types,pillar3a_tax,plan_move,salary_by_occupation,switch_health_insurer,tax_by_commune
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | ch.swisslivingindex/swiss-living-index |
|---|---|
| Endpoint | https://swisslivingindex.ch/mcp |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt