Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

zzd: Swiss everyday data

REMOTE · MCP.ZZD.CH

Swiss grocery prices, wedding venues, rents by canton, EV cost per km and map posters, by zzd.

Available components

+3 this week 76 Trust /100

Last scanned (23 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1515 tokens (~216/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “compare_grocery_prices” rewrote its description, which is the text the model reads security
    • Tool “ev_cost_per_km” rewrote its description, which is the text the model reads security
    • Tool “find_map_posters” rewrote its description, which is the text the model reads security
    • Tool “find_wedding_venues” rewrote its description, which is the text the model reads security
    • Tool “get_wedding_venue” rewrote its description, which is the text the model reads security
    • Tool “rent_reference” rewrote its description, which is the text the model reads security
    • Tool “search_grocery_prices” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • Schema quality: excellent → good functional
    • “compare_grocery_prices” reworded the description of “productId” cosmetic
    • “get_wedding_venue” reworded the description of “id” cosmetic
Diagnostics

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 21 Nov 2026 · Probed https://mcp.zzd.ch/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.zzd.ch CN=YE2,O=Let's Encrypt,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA384 6920b97d41eb55d3ca79e02c61f587c950a
SANs: mcp.zzd.ch
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.zzd.ch. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ch. DS published 58745 13 Verified
zzd.ch. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.zzd.ch/mcp Verified 200
http (plaintext) http://mcp.zzd.ch/mcp HTTPS enforced 308 https://mcp.zzd.ch/mcp
MCP tools · 7 exposed · ~1,357 tokens

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 →

Tool Tokens
compare_grocery_prices ~122

For one product id from a Schnäppchen Jäger search, returns its price, the identical article in the other Swiss shops (matched by barcode) and the cheapest similar product per shop for the same amount, each with the date it was read and a link. Similar products are not the same article. By zzd (schnaeppchenjaeger.zzd.ch). Not counted against the search allowance.

NameTypeReqDescription
langstring–Language of names and links. Default de.
productIdintegeryesThe product id from a grocery search result.

No output schema declared.

No examples provided.

ev_cost_per_km ~249

Electric cars offered in Switzerland ranked by total cost in CHF per km (depreciation, capital, tax, insurance, tyres and service, energy, wallbox, import fees, monthly fees), across buying new or used, importing from Germany, leasing and subscriptions, from the EV cost comparison (ev.zzd.ch, free, by zzd). Optional driving profile. The offers are a dated, hand-collected snapshot, not live prices; the model is calibrated for canton Aargau. The result links the comparison page.

NameTypeReqDescription
acquisitionTypestring–How the car is obtained. Without it, all ways are ranked.
annualKminteger–Default 15000.
holdingYearsinteger–Default 5.
homeChargingSharenumber–Share charged at home, 0-1.
homeElectricityChfPerKwhnumber–Home electricity price in CHF per kWh.
limitinteger–Default 5.
makestring–Only this make, e.g. 'Renault'.
publicChargingChfPerKwhnumber–Public charging price in CHF per kWh.

No output schema declared.

No examples provided.

find_map_posters ~120

Find the ready poster page for a town or place on MappaMuse (mappamuse.zzd.ch, personalised map posters printed to order, by zzd), with the sizes and prices that page lists, in CHF. Any other place can be designed on the custom-poster page. The result links the page; the page and checkout are binding.

NameTypeReqDescription
langstring–Language of names and links. Default de.
placestringyesA town or place, e.g. 'Aarau', 'Lugano'.

No output schema declared.

No examples provided.

find_wedding_venues ~314

Find places for a civil wedding in Switzerland as cantons and municipalities publish them (registry offices and outside venues such as castles), from Trauungslokale Schweiz (traulokale.zzd.ch, a free finder by zzd). Filter by canton (code, slug or name), town, text, guests, or a published ceremony date or date range. Important: most offices publish no dates; and where datesShowAvailability is false a published date is NOT known to be free. The date is always booked with the registry office. Each venue links its page.

NameTypeReqDescription
cantonstring–Canton code (AG), slug (aargau) or name (Argovie).
datestring–Only venues with a published ceremony date on this day.
fromstring–First day of a date range for published ceremony dates, YYYY-MM-DD. Use with to.
langstring–Language of names and links. Default de.
limitinteger–Default 10.
minGuestsinteger–Only venues that hold at least this many guests.
querystring–Text in the venue name, town or address, e.g. 'Schloss'.
tostring–Last day of a date range for published ceremony dates, YYYY-MM-DD. Use with from.
townstring–Town or municipality, e.g. 'Aarau'.
typestring–office = registry office, external = outside venue.

No output schema declared.

No examples provided.

get_wedding_venue ~97

Details for one venue id from a venue search: address, guests, costs as published, all published dates, the responsible registry office with phone, e-mail and official page, and the source the data was read from. By zzd (traulokale.zzd.ch).

NameTypeReqDescription
idstringyesThe venue id from a venue search result.
langstring–Language of names and links. Default de.

No output schema declared.

No examples provided.

rent_reference ~215

The usual net monthly rent by flat size in a Swiss canton, from the Federal Statistical Office (BFS), via Mietcheck (mietcheck.zzd.ch, free, by zzd). Give a canton or a place (postal code or municipality); with rooms and the net rent it also says whether that rent is below, within or above the usual range. A place in several cantons returns the candidates to choose from. Cantonal averages only: not street level, not legal advice. The result links the matching Mietcheck page.

NameTypeReqDescription
cantonstring–Canton code (ZH), slug or name. Use this or place.
langstring–Language of the answer and links. Default de.
netRentnumber–Monthly NET rent in CHF (without service charges and heating). Needs rooms.
placestring–Postal code or municipality, e.g. '8001' or 'Winterthur'.
roomsinteger–Number of rooms; 6 means 6 or more.

No output schema declared.

No examples provided.

search_grocery_prices ~240

Search the grocery catalogue of Schnäppchen Jäger (schnaeppchenjaeger.zzd.ch, a free Swiss price comparison by zzd) across Migros, Coop, Lidl, Aldi, Denner and Volg, plus Aligro's weekly promotions. Returns products with pack price, price per unit, offer flag, the date each price was read, and a link to each product's comparison page. Prices are the shops' online prices, not branch shelf prices. Counts as one search of the site's free daily allowance (5 a day per connection without an account; calls through Claude's connectors share 300 a day). Each product links its comparison page.

NameTypeReqDescription
langstring–Language of names and links. Default de.
limitinteger–How many products, 1-10. Default 8.
querystringyesWhat to look for, e.g. 'Vollmilch', 'Butter 250g'. German product names match best.
sortstring–Default relevance; unit-price puts the cheapest per kg/litre first.
storestring–Only this shop.

No output schema declared.

No examples provided.

Install

How do I install the zzd: Swiss everyday data MCP server?

zzd: Swiss everyday data is a hosted endpoint at https://mcp.zzd.ch/mcp, 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.zzd.ch

# add to Claude Code
claude mcp add --transport http ch-zzd-mcp 'https://mcp.zzd.ch/mcp'
Common questions

What is the zzd: Swiss everyday data MCP server?

zzd: Swiss everyday data is an MCP server listed in the public MCP registry as ch.zzd/mcp. Swiss grocery prices, wedding venues, rents by canton, EV cost per km and map posters, by zzd. This page covers its hosted endpoint (https://mcp.zzd.ch/mcp).

Is the zzd: Swiss everyday data MCP server safe to use?

zzd: Swiss everyday data scores 76 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 zzd: Swiss everyday data MCP server expose?

zzd: Swiss everyday data exposes 7 tools: search_grocery_prices, compare_grocery_prices, find_wedding_venues, get_wedding_venue, rent_reference, and 2 more. Their descriptions and schemas cost roughly 1,357 tokens of context every time the server is loaded.

Does the zzd: Swiss everyday data MCP server require authentication?

No. We connected to zzd: Swiss everyday data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the zzd: Swiss everyday data MCP server still maintained?

zzd: Swiss everyday data is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the zzd: Swiss everyday data MCP server?

VerifyMCP ran 13 checks on zzd: Swiss everyday data, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.