Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Zügle is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Swiss income tax by municipality, cheaper-town ranking, apartment listings and commute times.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http zugle-mcp https://zuegle.com/mcp
# 2 — ask your agent for something these tools do
# municipality_search, tax_lookup, municipality_detail and 5 more
Zügle costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http zugle-mcp https://zuegle.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Name fragment, e.g. "Uster". Case-insensitive. |
| zip | string | no | Four-digit Swiss postcode, e.g. "8308" (which alone spans three Gemeinden). |
| limit | integer | no | Maximum matches to return (1-50). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bfsId | integer | yes | Municipality BFS id, from municipality_search. |
| income | integer | yes | Gross annual household income in CHF. |
| relationship | string | no | Marital status used for the tariff. |
| confession | string | no | Church-tax affiliation. |
| children | integer | no | Number of dependent children. |
| year | integer | no | Tax year. Defaults to the year this installation is configured for. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bfsId | integer | yes | The municipality to describe. |
| 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 | no | Marital status. |
| confession | string | no | Church-tax affiliation. |
| children | integer | no | Dependent children. |
| years | integer | no | How many years of history to include. |
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 wh
| Parameter | Type | Required | Notes |
|---|---|---|---|
| currentBfsId | integer | yes | BFS id of the current home. |
| income | integer | yes | Gross annual income in CHF. |
| relationship | string | no | Marital status. |
| confession | string | no | Church-tax affiliation. |
| children | integer | no | Dependent children. |
| currentRooms | number | no | Size of the current home in rooms, used for the rent comparison. |
| near | string | no | Town or station name to search around, e.g. "Winterthur". Not a postcode. |
| radiusKm | integer | no | Distance from near in km (default 20). Ignored without near. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bfsId | integer | yes | Municipality to search in. |
| rooms | number | no | Preferred size in rooms; re-ranks, never filters. |
| surface | number | no | Preferred living space in m²; re-ranks. |
| limit | integer | no | Maximum listings to return (1-25). |
Returns the public-transport journey time in minutes between two Swiss places, using the national timetable.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | yes | Origin as a place or station name, e.g. "Uster". Not a postcode on its own. |
| to | string | no | Destination as a place or station name. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | yes | Origin as a place or station name, e.g. "Feusisberg". Not a postcode on its own. |
| to | string | no | Destination as a place or station name. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bfsId | integer | yes | Municipality BFS id, from municipality_search. |
| rooms | number | no | Apartment size in rooms, e.g. 3.5. Omit for the overall average. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Zügle or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| municipality_search | no tags | |
| tax_lookup | no tags | |
| municipality_detail | no tags | |
| favorable_municipalities | no tags | |
| listing_search | no tags | |
| commute_time | no tags | |
| commute_cost | no tags | |
| rent_benchmark | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Zügle can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.