Zügle
REMOTE · ZUEGLE.COM · SCANNED SEP 26
Swiss income tax by municipality, cheaper-town ranking, apartment listings and commute times.
Available components
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 Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 988 tokens (~123/item across 8 items; 8 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 Management83
- Stability observed for 25 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 8 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
How do I install the Zügle MCP server?
Zügle is a hosted endpoint at https://zuegle.com/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 · zuegle.com
claude mcp add --transport http com-zuegle-zugle 'https://zuegle.com/mcp'
{
"mcpServers": {
"com-zuegle-zugle": {
"url": "https://zuegle.com/mcp"
}
}
} {
"servers": {
"com-zuegle-zugle": {
"type": "http",
"url": "https://zuegle.com/mcp"
}
}
} [mcp_servers.com-zuegle-zugle] url = "https://zuegle.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-zuegle-zugle": {
"type": "remote",
"url": "https://zuegle.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-zuegle-zugle --url 'https://zuegle.com/mcp' --transport streamable-http
mcp_servers:
com-zuegle-zugle:
url: "https://zuegle.com/mcp" {
"McpServers": {
"com-zuegle-zugle": {
"Transport": "http",
"Url": "https://zuegle.com/mcp"
}
}
} assistant mcp add com-zuegle-zugle -t streamable-http -u 'https://zuegle.com/mcp'
{
"mcpServers": {
"com-zuegle-zugle": {
"type": "http",
"url": "https://zuegle.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 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.
- 13 Sept 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.
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 26 Sept 2026 · Probed https://zuegle.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zuegle.com | CN=WE1,O=Google Trust Services,C=US | 17 Aug 2026 | 15 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 1bbbe1bf11e8b6310e8485fd1c3f74b0 |
| SANs: zuegle.com, *.zuegle.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of zuegle.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| zuegle.com. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; img-src 'self' data: https://images.unsplash.com https://flatfox.ch https://*.flatfox.ch https://*.homegate.ch https://*.googlesyndication.com https://*.doubleclick.net https://*.adtrafficquality.google https://fundingchoicesmessages.google.com https://www.gstatic.com; connect-src 'self' https://pagead2.googlesyndication.com https://googleads.g.doubleclick.net https://*.adtrafficquality.google https://fundingchoicesmessages.google.com; script-src 'self' https://pagead2.googlesyndication.com https://*.adtrafficquality.google https://fundingchoicesmessages.google.com; style-src 'self' 'unsafe-inline'; frame-ancestors 'none'; base-uri 'none'; form-action 'self'; frame-src https://pagead2.googlesyndication.com https://googleads.g.doubleclick.net https://tpc.googlesyndication.com https://*.adtrafficquality.google https://fundingchoicesmessages.google.com |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://zuegle.com/mcp | Verified | 200 | |
| http (plaintext) | http://zuegle.com/mcp | Inconclusive | 405 |
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 →
commute_cost ~90
Estimates the monthly cost in CHF of commuting between two Swiss places, as a transit-pass estimate priced from Swiss regional fare-zone data. Some pricing regimes are approximations rather than an exact tariff.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Origin as a place or station name, e.g. "Feusisberg". Not a postcode on its own. |
| to | string | – | Destination as a place or station name. |
No output schema declared.
No examples provided.
commute_time ~69
Returns the public-transport journey time in minutes between two Swiss places, using the national timetable.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Origin as a place or station name, e.g. "Uster". Not a postcode on its own. |
| to | string | – | Destination as a place or station name. |
No output schema declared.
No examples provided.
favorable_municipalities ~245
Ranks municipalities that are cheaper than, or within CHF 1000/yr of, a stated current home, by annual tax saving — municipalities near-identical in cost are included deliberately, not filtered out. Answered from cached figures only, so the ranking may be partial; the response states how many candidates were covered. Pass `near` (a town or station name) and `radiusKm` to keep only places around where the household lives or works; an unrecognised place is reported, not silently ignored.
| Name | Type | Req | Description |
|---|---|---|---|
| children | integer | – | Dependent children. |
| confession | string | – | Church-tax affiliation. |
| currentBfsId | integer | yes | BFS id of the current home. |
| currentRooms | number | – | Size of the current home in rooms, used for the rent comparison. |
| income | integer | yes | Gross annual income in CHF. |
| near | string | – | Town or station name to search around, e.g. "Winterthur". Not a postcode. |
| radiusKm | integer | – | Distance from `near` in km (default 20). Ignored without `near`. |
| relationship | string | – | Marital status. |
No output schema declared.
No examples provided.
listing_search ~110
Lists apartments currently advertised in one municipality, cheapest first, with the local median asking rent. Indicative figures for browsing only: they come from a portal feed and are not verified against the listing page.
| Name | Type | Req | Description |
|---|---|---|---|
| bfsId | integer | yes | Municipality to search in. |
| limit | integer | – | Maximum listings to return (1-25). |
| rooms | number | – | Preferred size in rooms; re-ranks, never filters. |
| surface | number | – | Preferred living space in m²; re-ranks. |
No output schema declared.
No examples provided.
municipality_detail ~132
Returns the tax picture for one municipality relative to a stated current home: the annual difference, the tax multiplier, and the multi-year trend where past years are known.
| Name | Type | Req | Description |
|---|---|---|---|
| bfsId | integer | yes | The municipality to describe. |
| children | integer | – | Dependent children. |
| confession | string | – | Church-tax affiliation. |
| currentBfsId | integer | yes | BFS id of the current home, which every difference is measured against. |
| income | integer | yes | Gross annual income in CHF. |
| relationship | string | – | Marital status. |
| years | integer | – | How many years of history to include. |
No output schema declared.
No examples provided.
municipality_search ~104
Finds Swiss municipalities by name fragment or postcode. Returns the BFS id, name, canton and postcodes for each match. The BFS id is the key every other tool here takes.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum matches to return (1-50). |
| q | string | – | Name fragment, e.g. "Uster". Case-insensitive. |
| zip | string | – | Four-digit Swiss postcode, e.g. "8308" (which alone spans three Gemeinden). |
No output schema declared.
No examples provided.
rent_benchmark ~108
Reports the Swiss Federal Statistical Office's average monthly rent for a municipality, optionally for a given apartment size in rooms. BFS does not publish rent below canton level except for 10 named cities, so the figure may describe the CANTON rather than the municipality itself; the response states which.
| Name | Type | Req | Description |
|---|---|---|---|
| bfsId | integer | yes | Municipality BFS id, from municipality_search. |
| rooms | number | – | Apartment size in rooms, e.g. 3.5. Omit for the overall average. |
No output schema declared.
No examples provided.
tax_lookup ~130
Calculates the annual Swiss income tax for one municipality and one household profile, split into federal, cantonal and municipal parts. The figures come from the federal tax administration's calculation for the given gross income.
| Name | Type | Req | Description |
|---|---|---|---|
| bfsId | integer | yes | Municipality BFS id, from municipality_search. |
| children | integer | – | Number of dependent children. |
| confession | string | – | Church-tax affiliation. |
| income | integer | yes | Gross annual household income in CHF. |
| relationship | string | – | Marital status used for the tariff. |
| year | integer | – | Tax year. Defaults to the year this installation is configured for. |
No output schema declared.
No examples provided.
What is the Zügle MCP server?
Zügle is an MCP server listed in the public MCP registry as com.zuegle/zugle. Swiss income tax by municipality, cheaper-town ranking, apartment listings and commute times. This page covers its hosted endpoint (https://zuegle.com/mcp).
Is the Zügle MCP server safe to use?
Zügle scores 74 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 Zügle MCP server expose?
Zügle exposes 8 tools: municipality_search, tax_lookup, municipality_detail, favorable_municipalities, listing_search, and 3 more. Their descriptions and schemas cost roughly 988 tokens of context every time the server is loaded.
Does the Zügle MCP server require authentication?
No. We connected to Zügle without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zügle MCP server still maintained?
Zügle is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.