Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
InfraNode 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.
96/100
tool-list score
12
tools declared
remote
at its publisher
—
calls last 7d
What it does
Keyless open data for 84 German cities: 12 lean read-only MCP tools covering 67 data types.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http infranode-mcp https://mcp.infranode.dev/mcp
# 2 — ask your agent for something these tools do
# get_city, get_city_overview, get_city_resource and 9 more
InfraNode costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
INAll 1 server
infranode1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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.
Claude Codedeclared by this listing
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 infranode-mcp https://mcp.infranode.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
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.
What you approve
12 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.
Get base data for a German city (population, area, coordinates). Sourced from Wikidata. Read-only. Useful as a first lookup to confirm a city exists and get its core attributes. For a broader question about the city (what data is available at all) use `get_city_overview` instead.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | City identifier, e.g. 'berlin' or 'hamburg'. Resolved leniently: the German name with or without umlauts, any casing, a common English exonym or short form also works (München/munich/munchen -> muench |
Get a ONE-CALL overview of everything InfraNode knows about a German city. Start here for any city question. Returns: the city's base data, a CATALOG of all 80 available data types (weather, air quality, public transit, trains, traffic, charging, parking, solar, energy, demographics, taxes, accidents, tourism, heritage, trees, population density, playgrounds, post boxes and many more), each with
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | City identifier, e.g. 'berlin' or 'hamburg'. Resolved leniently: the German name with or without umlauts, any casing, a common English exonym or short form also works (München/munich/munchen -> muench |
Fetch ANY per-city data type by its key (generic accessor, 80 data types). One tool for the whole breadth of InfraNode: live data (air, traffic, transit stops, parking, charging, water-level, flood, sharing, fuel-prices, station-departures/-arrivals/stations, ...), statistics (demographics, unemployment, tourism, accidents, crime-stats, indicators, land-values, tax-rates, insolvencies, ...), mult
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | City identifier, e.g. 'berlin' or 'hamburg'. Resolved leniently: the German name with or without umlauts, any casing, a common English exonym or short form also works (München/munich/munchen -> muench |
| resource | string | yes | Data type key to fetch, exactly as listed by get_city_overview / the infranode://catalog resource (the 'type' field), e.g. 'charging', 'parking', 'demographics', 'solar', 'district-heating'. |
Get official air quality for a German city (PM10, NO2 and more). Sourced from the Umweltbundesamt (UBA). Read-only. For live nearest-station hourly readings use `get_city_resource(slug, resource='air')` instead.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | City identifier, e.g. 'berlin' or 'hamburg'. Resolved leniently: the German name with or without umlauts, any casing, a common English exonym or short form also works (München/munich/munchen -> muench |
Get current weather observations for a German city. Sourced from the Deutscher Wetterdienst (DWD): temperature, wind, precipitation and related fields. Read-only, current conditions only (not a forecast). For warnings use `get_city_resource(slug, resource='weather-warnings'). For a broader question about the city (not just weather) use get_city_overview` instead, which already includes a li
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | City identifier, e.g. 'berlin' or 'hamburg'. Resolved leniently: the German name with or without umlauts, any casing, a common English exonym or short form also works (München/munich/munchen -> muench |
Get points of interest in a German city, filtered by type. Sourced from OpenStreetMap. Read-only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | City identifier, e.g. 'berlin' or 'hamburg'. Resolved leniently: the German name with or without umlauts, any casing, a common English exonym or short form also works (München/munich/munchen -> muench |
| type | string | yes | POI type from the API allowlist, one of: hospital, school, pharmacy, restaurant, police, kindergarten. |
Get live departures for ANY railway station by its EVA number. Covers all train categories including local/regional (S/RB/RE) and long distance, with real-time delays, cancellations and disruption messages. Get the EVA from `get_city_resource(slug, resource='stations')`. Read-only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| eva | string | yes | Station EVA number (digits only) from get_city_resource(slug, resource='stations'), e.g. '8011160' (Berlin Hbf). |
Get live arrivals for ANY railway station by its EVA number. Mirror of `station_board_departures for arriving trains (all categories, real-time delays, disruption messages). Get the EVA from get_city_resource(slug, resource='stations')`. Read-only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| eva | string | yes | Station EVA number (digits only) from get_city_resource(slug, resource='stations'), e.g. '8000105' (Frankfurt Hbf). |
Get live public-transport departures with real-time delays for a stop. Sourced from GTFS-RT/HVV/VGN. Unlike the static stop list (`get_city_resource(slug, resource='transit')), this returns minute-fresh departures including delay for ONE stop. A stop_id` is required: fetch the city's transit stops first to discover valid stop IDs, then pass one here. Read-only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | City identifier, e.g. 'berlin' or 'hamburg'. Resolved leniently: the German name with or without umlauts, any casing, a common English exonym or short form also works (München/munich/munchen -> muench |
| stop_id | no | Required stop ID to fetch departures for. Discover a city's stop IDs with get_city_resource(slug, resource='transit') first (each stop carries its id). Format: DELFI 'de:<AGS>:<id>' or a numeric gtfs. |
List all covered cities (slug, federal state, population, coverage). Takes no arguments. Call this first to discover valid city slugs before invoking any city-scoped tool. Read-only.
No parameter schema on file.
List all data sources with license, attribution and availability. Takes no arguments. Shows which upstream sources InfraNode bundles and whether each is currently active. Read-only.
No parameter schema on file.
Compare ONE resource across MULTIPLE cities in a single response. Fans the resource out over the listed cities and returns a per-city `source_status` (ok/disabled/no_data/error/not_found), so a missing or failing city source does not spoil the whole answer. Read-only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| resource | string | yes | Resource to compare. Supported: 'weather' (DWD), 'air' (UBA air quality), 'indicators' (INKAR socioeconomic indicators incl. unemployment rate and EV charging coverage), 'demographics', 'unemployment' |
| cities | string | yes | Comma-separated list of city slugs, e.g. 'berlin,koeln,hamburg' (max. 28 cities). |
Free
$0 forever
- 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 InfraNode or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.1.1 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest25001763a60b0bb6407fa7f0f843c1b56941a6c2763333bc4c2092ce9f1ed45f
Score vectorthreat 100 → client 96
| 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 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
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 |
|---|---|---|
| get_city | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_city_overview | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_city_resource | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| air_quality | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| weather | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| pois | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| station_board_departures | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| station_board_arrivals | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| transit_departures | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| list_cities | no tags | |
| sources | no tags | |
| compare | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
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
Integrityfirst-seen
Surface digest25001763a60b0bb6
Scanned2026-10-20
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.1.
1.1.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish InfraNode can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.