# InfraNode (remote · mcp.infranode.dev)

Keyless open data for 84 German cities: 12 lean read-only MCP tools covering 67 data types.

- Trust score: 77/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.infranode.dev`: 77/100 (this document), [markdown](https://verifymcp.io/servers/dev-infranode-infranode/mcp.md), [page](https://verifymcp.io/servers/dev-infranode-infranode/mcp)

## Channel facts

- Endpoint: `https://mcp.infranode.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2815 tokens (~187/item across 15 items; 12 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http dev-infranode-infranode https://mcp.infranode.dev/mcp
```

### Codex

```toml
[mcp_servers.dev-infranode-infranode]
url = "https://mcp.infranode.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-infranode-infranode": {
      "type": "remote",
      "url": "https://mcp.infranode.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-infranode-infranode --url https://mcp.infranode.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-infranode-infranode:
    url: "https://mcp.infranode.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "dev-infranode-infranode": {
      "type": "http",
      "url": "https://mcp.infranode.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 77, +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.

### 2026-08-01 (score 76, 0)

- [security] Tool “get_city_resource” rewrote its description, which is the text the model reads
- [security] Tool “get_city_overview” rewrote its description, which is the text the model reads

### 2026-07-31 (score 76, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 73, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 72, +1)

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

### 2026-07-28 (score 71, +1)

- [security] Tool “get_city_resource” rewrote its description, which is the text the model reads
- [security] Tool “get_city_overview” rewrote its description, which is the text the model reads

### 2026-07-27 (score 70, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 70)

First indexed and scored.

## MCP tools (12)

### `get_city` (~177 tokens)

City Base Data

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.

Input parameters:

- `slug` (string, required): 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 -> muenc…

Output parameters:

- `data`
- `meta`

### `get_city_overview` (~290 tokens)

City Overview

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 82 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 its coverage status and the exact tool to call next (for most
data types that is ``get_city_resource(slug, resource=<type>)``), plus a small
live highlights snapshot (current weather, air quality and train departures).
Data types not yet covered for this city show where they ARE available so you
can pivot. InfraNode keeps adding data and cities, so the catalog grows over
time. Read-only.

Input parameters:

- `slug` (string, required): 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 -> muenc…

Output parameters:

- `data`
- `meta`

### `get_city_resource` (~423 tokens)

City Data by Type

Fetch ANY per-city data type by its key (generic accessor, 82 data types).

One tool for the whole breadth of InfraNode: live data (air, traffic, transit
stops, parking, charging, water-level, flood, sharing, fuel-prices, icu-live,
webcams, station-departures/-arrivals/stations, ...), statistics
(demographics, unemployment, tourism, accidents, crime-stats, indicators,
land-values, tax-rates, insolvencies, ...), multi-year TIME SERIES
(``sustainability``: SDG indicators per municipality, one value per year from
2006 to 2023, so trends can be answered without stitching snapshots),
infrastructure and environment
(solar, solar-roofs, district-heating, energy, heritage, tree-cadastre,
playgrounds, public-toilets, markets, education, ...) and more. Discover the
valid keys and per-city coverage with ``get_city_overview(slug)`` or the
\``infranode://catalog`` resource; the ``resource`` enum lists every key.
Uncovered types return ``source_status="not_covered"`` (plus where they ARE
available), never an error. Read-only.

Input parameters:

- `resource` (string, required): 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'.
- `slug` (string, required): 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 -> muenc…

Output parameters:

- `data`
- `meta`

### `air_quality` (~167 tokens)

Air Quality

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.

Input parameters:

- `slug` (string, required): 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 -> muenc…

Output parameters:

- `data`
- `meta`

### `weather` (~204 tokens)

Weather

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
live weather highlight.

Input parameters:

- `slug` (string, required): 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 -> muenc…

Output parameters:

- `data`
- `meta`

### `pois` (~164 tokens)

Points of Interest

Get points of interest in a German city, filtered by type.

Sourced from OpenStreetMap. Read-only.

Input parameters:

- `slug` (string, required): 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 -> muenc…
- `type` (string, required): POI type from the API allowlist, one of: hospital, school, pharmacy, restaurant, police, kindergarten.

Output parameters:

- `data`
- `meta`

### `station_board_departures` (~111 tokens)

Station Board: Departures

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.

Input parameters:

- `eva` (string, required): Station EVA number (digits only) from get_city_resource(slug, resource='stations'), e.g. '8011160' (Berlin Hbf).

Output parameters:

- `data`
- `meta`

### `station_board_arrivals` (~103 tokens)

Station Board: Arrivals

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.

Input parameters:

- `eva` (string, required): Station EVA number (digits only) from get_city_resource(slug, resource='stations'), e.g. '8000105' (Frankfurt Hbf).

Output parameters:

- `data`
- `meta`

### `transit_departures` (~331 tokens)

Transit Departures

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.

Input parameters:

- `slug` (string, required): 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 -> muenc…
- `stop_id`: 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…

Output parameters:

- `data`
- `meta`

### `list_cities` (~50 tokens)

List Cities

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.

Output parameters:

- `data`
- `meta`

### `sources` (~41 tokens)

Data Sources

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.

Output parameters:

- `data`
- `meta`

### `compare` (~186 tokens)

Compare Cities

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.

Input parameters:

- `cities` (string, required): Comma-separated list of city slugs, e.g. 'berlin,koeln,hamburg' (max. 28 cities).
- `resource` (string, required): Resource to compare. Supported: 'weather' (DWD), 'air' (UBA air quality), 'indicators' (INKAR socioeconomic indicators incl. unemployment rate and EV charging coverage), 'demographics', 'unemployment…

Output parameters:

- `data`
- `meta`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-infranode-infranode/mcp#diagnostics

## Score history

- 2026-08-03: 77
- 2026-08-02: 76
- 2026-08-01: 76
- 2026-07-31: 76
- 2026-07-30: 73
- 2026-07-29: 72
- 2026-07-28: 71
- 2026-07-27: 70
- 2026-07-26: 70

## Links

- Remote endpoint: https://mcp.infranode.dev/mcp
- Repository: https://github.com/street1983nk/infranode
- Changelog RSS feed: https://verifymcp.io/servers/dev-infranode-infranode/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-infranode-infranode/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/dev-infranode-infranode/mcp