Skip to content
External endpointresponds

InfraNode

Keyless open data for 84 German cities: weather, air, transit, traffic. 38 read-only MCP tools.

Endpoint URL
https://mcp.infranode.dev/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:04 AM UTC
Check
MCP initialize · 8s limit
Latency
826 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
dev.infranode/infranode

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
infranode
Version
1.27.2
Capability keys
experimental, prompts, resources, tools
Tool names
get_city, get_city_overview, get_city_resource, air_quality, weather, pois, station_board_departures, station_board_arrivals, transit_departures, list_cities, sources, compare
Instructions excerpt

InfraNode is a keyless, read-only open-data API for 84 German cities with ~60 data types, exposed as 12 MCP tools (count is live from this server, not a cached or remembered number). To answer ANY city question, START with get_city_overview(slug): it returns the city's base data, a catalog of ALL available data types (each with its coverage status and the exact tool to call next) and a small live snapshot (weather, air, train departures). Most data types are fetched with ONE generic tool: get_city_resource(slug, resource=<type>), where <type> is the catalog key (e.g. 'parking', 'charging', 'demographics', 'solar'); its resource enum lists every valid key. City slugs are resolved leniently: you may pass the German name with or without umlauts, any casing, a common English exonym or a short form (e.g. 'muenchen', 'München', 'munich', 'munchen', 'cologne', 'frankfurt' all resolve to the canonical slug), so you rarely need the exact ASCII slug; an unrecognized name returns a 404 whose hin

Reported Aug 17, 2026, 05:04 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 474ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 870ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 831ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 826ms