ViaFrei
ViaFrei is a free, hosted German real-time mobility MCP server: 24 read-only tools for live traffic, transit, charging, parking, fuel, weather and place lookups, each answering in German or English with source attribution.
Motorway traffic (
check_autobahn_traffic): traffic light, jams, closures, roadworks and delays for up to 5 motorways, or all motorways of one Bundesland.Road status and closures (
check_road_status): whether a motorway, Bundes-/Landesstraße or town is open, closed or restricted now or in the next 14 days; also lorry height/weight limits and the long-lorry network.Planned roadworks (
find_roadworks_ahead): dated construction sites on a road or by place within a chosen window.Parking (
find_parking): car parks, P+R, lorry parks and disabled-badge bays with spaces, stated amenities (WC, shower) and published free counts.EV charging (
find_charging_station): filter by plug (incl. MCS), power band, operator, 24/7, card payment, free and live availability.Fuel and hydrogen: cheapest grade nearby (
find_cheapest_fuel), filtered station search (find_fuel_station), H2 stations for cars or lorries (find_hydrogen_station).Speed cameras (
find_speed_cameras): published enforcement locations for planning only, with the StVO notice.Transit: train boards (
get_train_departures), any bus/tram/U-Bahn/ferry stop or the stops around a place (get_departures), and regional or per-line punctuality (check_transit_disruption).Stations: lift and escalator states (
check_station_facilities) or a whole station briefing (describe_station) with platforms, departures and access.Places: name lookup (
find_place), businesses and landmarks (find_poi), street addresses (find_address), coordinate-to-words (describe_location), what is nearby (find_nearby).Shared bikes (
find_sharing): bike-sharing stations with bikes and free docks, plus free-floating bikes.Weather and rules: official DWD warnings with road-surface forecast (
check_weather_warnings), and German driving rules such as low-emission zones, tolls, winter tyres and the lorry ban (get_driving_rules).Watches (
watch_situation/stop_watch): get told inside the conversation when a closure, jam, delay, warning or free charger changes state, for up to 24 hours.Every tool takes a place name or lat/lon plus
language(de/en), and returns missing data honestly ("unknown, not free") with the licence/attribution line to show.
Provides access to Deutsche Bahn train timetable and station data, enabling queries about departures, arrivals, and station information.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ViaFrei Find available EV charging stations near Cologne Cathedral"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ViaFrei
The German Real-Time Mobility Context Platform for AI
ViaFrei gives AI assistants real-time awareness of Germany. Trains and buses, traffic and roadworks, fuel, charging, parking and weather. One MCP. No API key. No sign-up.
Ask in plain words. Get the live answer, with its source.
viafrei.de · Connect your assistant · For developers · For businesses · All tools · API reference · REST API (in development, preview planned)
claude mcp add --transport http viafrei https://mcp.viafrei.de/mcpFree. No account, no API key, no sign-up. One line and your assistant knows whether the A8 is jammed, whether your train, bus or tram is late, where the nearest fast charger is (and whether it is free, where the operator publishes that), which hydrogen station takes a lorry, whether the lift at your station works and whether the road ahead is forecast to freeze — from official German open data, live, with the source named in every answer. And every German motorway has a live page of its own on viafrei.de, with a map and a traffic light, and so does every railway station and every Autobahnkreuz, all of them one search away from the box in the site's header.
Beta. ViaFrei is being stabilised: sources are still being added, and answers and coverage can change. The answers are written by an AI assistant from our data, and AI can make mistakes, so check anything important (a closure, a departure, a price) against the source each answer names.
New in server 2.6.16: FlixBus and FlixTrain departures. No tool was added, renamed or removed and no input changed; there are still twenty-four tools, and one source joins the 276.
Long-distance coaches and trains on the departure board.
get_departuresnow adds a FlixBus and FlixTrain block after the local departures, at a stop and around a place, with the realtime delay where Flix publishes one. Asked for buses at "München, ZOB" withlimit: 5andlanguage: "en"at 06:19 on 2026-11-14, it listed the Lufthansa Express Bus to the airport from the DELFI timetable and, beside it, eight FlixBus departures from Munich central bus station 730 m away between 05:50 and 07:00, the night line N422 running 69 minutes late. A FlixBus or FlixTrain departure DELFI's board already lists is not shown twice.One new source, share-alike. The departures come from the timetable and realtime Flixbus France publishes on transport.data.gouv.fr under ODbL 1.0, kept as a database of its own; only an answer that lists one carries its line (SOURCES.md).
On viafrei.de: the transit card of the place pages shows the same block, in every language of the site, and the News page announces it.
Before that, server 2.6.15: fuel prices fetched when you ask, and a steadier viafrei.de. No tool, input or answer shape changed; there are still twenty-four tools, and the sources are the same 276.
Fuel prices are read for the question that needs them. The server no longer refreshes the large cities' and the motorway corridors' prices on a schedule of its own, because Tankerkönig's terms ask for requests that a person starts. Asked for the cheapest Super E5 in Leipzig with
limit: 3at 21:30 on 2026-11-13,find_cheapest_fuellisted two STAR stations at 1.819 €/l and a Greenline at 1.848 €/l, each "as of 21:30": read for that question. Prices already read are kept, and every price still carries the time it was read.A question you ask always gets its turn. Background updates can no longer use up a source's request allowance and leave a person's question waiting.
On viafrei.de: pages no longer stall for several seconds after each motorway update, pages answer more reliably while the site is busy, and the fuel and charging station lists are built several times faster.
Before that, server 2.6.13 and 2.6.14: speed-camera lists from three more cities and from OpenStreetMap, punctuality for a line asked without a place, and DB's own departure board at the large stations. No tool was added, renamed or removed; there are still twenty-four. Three of them changed:
find_speed_camerasanswers from more sources,check_transit_disruptiontakes one new optional input,line, anddescribe_stationnow reads DB's own board at the large stations.
Speed-camera locations from Bottrop, Konstanz and Essen, and from OpenStreetMap.
find_speed_camerasand the place pages' card now also list Bottrop's current speed-check sites, Konstanz's stationary radar units (from the city's yearly statistics, 2023 the newest year it publishes) and Essen's weekly plan of announced mobile checks, a row for each street on each day, kept in the answer until the day is over. Where no official source we hold publishes fixed or section-control cameras for a municipality, the fixed cameras OpenStreetMap contributors have mapped follow in a block of their own, with their own count (osmTotal) and their own ODbL credit;limitapplies to each block. Asked about Essen withlimit: 3at 20:28 on 2026-11-13, the answer listed three announced checks (Alfredstraße, Alte Hauptstraße, Altendorfer Straße "and 85 more") and then "Fixed cameras (OpenStreetMap)", six of them. Every answer still opens with the § 23 Abs. 1c StVO notice, and the tool's description now says what that rule covers: a driver's use of such a device, not the publication of the locations. SOURCES.md has all seven towns and the OpenStreetMap terms."Is the RB33 on time?"
check_transit_disruptiontakesline. Without a region it answers for the districts the line runs through, or, when lines of that name run in several regions, lists them and asks which. Asked about the RB33 withregion: "Duisburg"at 20:25 on 2026-11-13, it answered for the eight districts and cities that line stops in: 15% of observed trips more than 5 minutes late (187 of 1,212 in the last hour, better than the 25% of the hour before), 3 trips skipping a stop and 6 cancelled (example); asked without a region two minutes later, it named the seven regions where a line called RB33 runs. The figures stay region-wide, and the answer says so.DB's own board at the large stations. For the category 1 and 2 stations the station page and
describe_stationtake the platform and destination of the trains they list from DB's own departure board; a row DB answered says so ("by": "db_timetables"), and the page says when DB last answered.describe_stationis now annotated as reaching an outside source (openWorldHint: true).Sharper answers. "Homburg" finds Bad Homburg v.d.Höhe as well as Homburg in the Saarland; a road with only a weight limit is no longer called closed, and a closure is over when the dates in its own text say so;
get_train_departuresnow says whether a time lies beyond what DB has published yet or the station is one DB does not cover, and names the window it looked at; "+N more" counts only rows the result really holds, andfind_parkingtells you when the limit hid some matching sites; each lift of a station appears once, and an inventory entry with no live reading can no longer override a lift that reports its state.On viafrei.de: a home tile that cannot load says so after 1.5 seconds and tries again, instead of showing "loading" for a quarter of a minute; a place page the site has not read yet answers "busy" rather than "not found"; and every charging page in the site's sitemap now opens directly, without a redirect.
Before that, server 2.6.9 to 2.6.12: a steadier viafrei.de when it is busy. The connector itself was unchanged: no tool, input, answer shape or source was added, changed or removed.
The tools answer as before. Asked about the A7 at 19:41 on 2026-11-12,
check_autobahn_trafficanswered with data as of 19:37: a red traffic light, 7 jams, 21 closures and 100 roadworks sites, and +27 min both from Hannover towards Kassel and from Würzburg towards Fulda.describe_stationfor Hamburg Hbf in the same minute gave the rail lamp amber, with 1 of 72 departures cancelled, and named platform 13/14 as not step-free right now because its lift was out of service.A busy place page no longer turns a person away. While the site is under load, someone waiting for a place page gets a reduced version of it instead of an error.
Before that, server 2.6.0 to 2.6.8: the same address and the same tools. No tool was added, renamed or removed, and no input or answer changed shape; there are still twenty-four.
Nothing to change on your side. The endpoint is still
https://mcp.viafrei.de/mcp, over Streamable HTTP, with no key and no sign-up, and this package still relays to it. Asked about the A8 at 17:40 on 2026-11-11,check_autobahn_trafficanswered as before: a red traffic light, 3 jams, 3 closures and 55 roadworks sites, the worst jam Stuttgart → Karlsruhe at +27 min.describe_stationfor Köln Hbf four minutes later gave the station's rail lamp red, with 21 of its 71 trips in the window more than 5 min late.Before that, server 2.5.21 to 2.5.28: distances in metres, train boards that know DB's horizon, lifts and entrances at Berlin and Brandenburg stops, and on viafrei.de a live map and road messages in every page language. No tool was added, renamed or removed; there are still twenty-four.
Distances in metres. Every site in
find_charging_stationand every car park infind_parkingcarriesdistanceMbesidedistanceKm, and a main facility infind_parkingcarriesexternalId, the publisher's own id where it has one. Asked for 150 kW chargers near Leipzig Hbf on 2026-11-09, the nearest answered with"distanceKm": 0.9, "distanceM": 920.A train board past DB's horizon says so.
get_train_departuresasked about a window DB has not published yet answers"dbTimetables": {"answered": false, "reason": "not_published"}and lists the planned departures from the DELFI timetable instead, never "unreachable". A board for a later time names its own window.Lifts and entrances in Berlin and Brandenburg.
check_station_facilitiesreads VBB's register of stop entrances: for U Hermannplatz on 2026-11-09,"lifts": 3, "entrances": {"total": 11, "withLift": 2}. The register says where a lift is, not whether it works, and the answer never calls a stop step-free because of it.Sharper answers.
find_parkingreads occupancy and the lorry-parking terms against the time of the request; the winter-tyre line follows the forecast, so ice on the road is no longer lost under a frost warning; a speed-camera search that finds none names the register it searched; and a point outside Germany is given no Bundesland.On viafrei.de: a live map with switchable layers for the motorways, roadworks, the railway network, weather warnings and delays, with a time slider; police, Land and city road messages machine-translated into every language the pages are offered in, the German original linked beside each; Land pages with questions to put to your AI; a station index that opens near you; a railway traffic light on station pages; "nearby" on every object page; and pages that open the same way everywhere, with the state, one sentence and its time first.
Before that, server 2.5.9 to 2.5.20: lorry chargers, free charging from the operator's own tariff, refusals that show the call to make instead, and on viafrei.de a desktop dashboard, U-Bahn and Stadtbahn station pages and pages for developers and businesses. No tool was added, renamed or removed; one of the twenty-four,
find_charging_station, accepts one more plug.
Chargers for electric lorries.
find_charging_stationtakesconnector: "mcs", the Megawatt Charging System that heavy electric lorries charge with (example). The plug and MCS filters are decided point by point, so an answer lists only the plugs a site's points actually carry."Free of charge" from the operator's own price list too. The
conditionsfilter'sfreenow also counts a site whose operator publishes an ad-hoc tariff of 0 that is at most 90 days old, beside what the Bundesnetzagentur's register states. A site that states nothing is still left out and counted, never assumed.A refusal says what to ask instead. A call that cannot be answered says why and what would work: a missing or invalid input ends with an example call, a point outside Germany asks for a German place, and
_meta.errorCode(with_meta.errorReasonwhere there is one) says which kind of refusal it is (example).Discovery on both hosts.
viafrei.de/.well-known/mcp.jsonandmcp.viafrei.de/.well-known/mcp/server-card.jsonserve the same server card, andviafrei.de/.well-known/security.txt(RFC 9116) names the contact.On viafrei.de: a developers page with a quickstart per client, a recorded try-it call and every tool with an example question, and a business page with a table of what a business may do with each kind of source; at 1024 px and wider a dashboard layout (the items in one column, beside a map whose marks link back to them, and on the home a strip of the most affected motorways and stations); every page opening on a phone with what it is about, a card's credits folded with the figures they credit; station pages for U-Bahn and Stadtbahn stations, found through OpenStreetMap, each naming the nearby tram and bus stops with their live departures; departure boards that refresh every minute in place; "use my location" at a station, a fuel or charging station or a rest area opening that place's page; and shorter addresses for the fuel and charging pages, with every older address redirected.
Fixed: a single misread date in a city's traffic message no longer stops that city's whole feed; the motorway messages of the national access point no longer wait behind the large feeds; central Köln is called Köln again; and the home's "most affected stations" block reads every regional realtime feed, not one.
Before that, server 2.5.8: a whole railway station in one answer, one Bundesland's motorways at a glance, and on viafrei.de a page for every Land, every fuel station and every charging site. One tool was added then,
describe_station.
A whole station in one answer. The new tool
describe_stationanswers one railway station as its page on viafrei.de shows it: the address, which platforms are step-free now, the lifts and escalators (out of service first), the platforms with their heights, the next departures with live delays, the service alerts, and parking and charging at the station, with a link to the station page (example). One lift, one train's delay or a bus stop are stillcheck_station_facilities,get_train_departuresandget_departures.One Bundesland's motorways.
check_autobahn_traffictakeslandinstead ofroads: "Stau in Bayern?" is answered with the Land's counts of closures, warnings and roadworks, its longest jams and each motorway with something in force, as the Land's page shows it (example).Lift states agree with the station page.
check_station_facilitiesreads the lift and escalator states by the same rule as the station page, so the two no longer count a station's lifts differently.On viafrei.de: a page for each of the sixteen Länder and an index of them, with the motorways now, facts and the largest towns; a page for every fuel station and every charging site, linked from the cards and from the fuel and charging answers, each kind in its own sitemap; maps that draw closures, roadworks and jams along the road, mark a station's lifts and say how fresh they are, refreshing in place with the traffic light every two minutes; a site search that also finds Bundes- and Landesstraßen ("B 51", "L 249") and suggests without waiting on a slow read; and recent places in the header's place bar that each open their own place, and a station chosen from the search remembered as that station, reopening its page.
Earlier, server 2.5.4 and 2.5.5: published speed-camera locations for planning, everyday needs near a place, departures around a place, charging by terms of use, Trier's car parks, and bus and train cards that read like a departure board. One tool was added then,
find_speed_cameras. Server 2.5.6 and 2.5.7 added no tool.
Published speed-enforcement locations, for planning only. The new tool
find_speed_camerasand a card on the place pages list what four towns publish: the fixed and red-light cameras of Düsseldorf and of Karlsruhe (with Rheinstetten), Köln's table of measuring sites (a published measuring site, never called a fixed camera), and Aachen's log of this year's mobile checks, for the town as a whole. They are listed by kind and street, never by distance. Every answer, every empty answer and every refusal opens with the § 23 Abs. 1c StVO notice: a driver may not use such a function while driving, so the list is for before the trip or a stop, andwatch_situationrefuses to watch for speed cameras (example).Everyday needs near a place.
find_nearbyanswers, when they are named incategories,groceries,health(pharmacy, doctor, hospital),money(cash machine, bank, post office),food,lodging,garage(repair, tyres, car wash),policeandtoilets, up to five each, from OpenStreetMap, each in its own radius of 1 to 2 km, widened up to 5 km where fewer than three are near. The place pages show the same places as cards. Server 2.5.4 had onesafetyneed for police and public toilets together; 2.5.5 made them two,needs.policeandneeds.toilets, and still answerssafetyas both.Departures around a place.
get_departurestakes aplaceorlat/lonas well as a stop, and then answers with the nearest stops within 5 km and their next departures in the coming hour, the same stops, departures and credits as the place page's card.Charging by terms of use.
find_charging_stationand the charging card filter forconditions: open around the clock, card payment at the charger, free of charge, open to the public. Only the Bundesnetzagentur's charging register states these terms, so a site that states nothing is left out and counted, never assumed to qualify.Trier's car parks with their free spaces: 29 car parks and lots of the Stadtwerke Trier, 28 of them placed, in
find_parkingand on the parking card, the first parking source for Trier (SOURCES.md).The bus and train card, stop by stop. Each stop is a small departure board (the countdown over the clock, the line as a badge, the destination, the platform, the state as a word and a symbol), its facilities folded underneath with what is out of service, and chips over the stops to show one kind of service. The station pages' board is drawn as a platform display, with departures and arrivals on two tabs, and its columns keep one line each on a phone (fixed in 2.5.5).
One card format everywhere. The motorway pages' fuel, charging, weather warning and road-weather cards, and the station page's departure rows, are drawn like the place pages' cards, and the fuel card can be sorted by your grade.
Fixed: a 22 kW AC charger (and a Type 2-only site up to 43.5 kW) is no longer labelled DC; one departure published twice under two spellings of its line or stop ("RE5" and "RE 5 (RRX)") is listed once, in every departure tool and on every board.
Earlier: server 2.5.1 to 2.5.3 brought a search box in every page's header, one page for every Autobahnkreuz and Autobahndreieck, a place box that finds motorways and junctions, redesigned cards, and a place that may come with a coordinate (refused with the distance and
_meta.errorReasonwhen the two are too far apart). Server 2.5.0 fixed bugs only (a sectioned track such as Hamburg Hbf's "7A-D" is read as that track). Server 2.4.4 to 2.4.9 brought live times for buses, trams and the U-Bahn from DELFI's fourteen regional SIRI ET feeds and VBN's Connect, the traffic strategies of Bayern and Lower Saxony, a traffic light and a street map for every place, station pages for every railway station, and police and Land traffic messages translated on the site. The 2.4.0 to 2.4.3 releases brought the five-questionentryon every road item, charging by operator and power band, truck-parking occupancy behind the user's acceptance, and the station and exit pages; the CHANGELOG has the whole list. Every source is listed, with what it feeds and what we hold back, in SOURCES.md.
🧳 What you can ask
You don't need to know any tool names. Ask the way you'd ask a friend who happens to have every German traffic feed open. German or English; the answer comes back in the language you asked in.
when you're… | ask |
🌅 about to commute | Wann fährt die nächste Bahn ab Köln Neumarkt? · What leaves from the stops near Köln-Ehrenfeld? · Does an ICE leave Tübingen Hbf in the next hour? · Fahren Busse und Bahnen in Bayern gerade pünktlich? · Is the RB33 around Duisburg on time? · When does the next train leave Hamburg Hbf? · Which U-Bahn and trams leave Berlin Alexanderplatz in the next minutes? · Wann fährt die nächste Stadtbahn ab Hannover Kröpcke? · Tell me about Leipzig Hbf |
🚗 about to drive | Is the A7 clear right now? · Stau in Bayern? · How are the motorways in Hessen right now? · Gibt es Stau auf der A8? · Are there roadworks on the A7 next week? · Is the A1 closed anywhere? · Welche Vollsperrungen sind auf der A7 in den nächsten sieben Tagen geplant? · Welche Baustellen gibt es in München? · How is the traffic on the A3 around Köln? · Ist die Fehmarnsundbrücke wegen Wind gesperrt? · Which detours are signed near Hamburg Hbf? |
🗺️ planning a trip | Ich plane eine Fahrt nach Düsseldorf: Wo stehen dort feste Blitzer? · Which speed-camera locations does Karlsruhe publish? · Welche Blitzer plant Essen diese Woche? — for planning only: the answer opens with the § 23 Abs. 1c StVO notice, and a driver may not use it while driving |
🚚 driving a lorry | Darf der Lang-Lkw auf die A7? · Which height limits are there for lorries in Bremen? · Gibt es Lkw-Durchfahrtsverbote bei Bielefeld? · Wann ist der nächste Lkw-Fahrverbotstag? · Gilt am 31. Oktober in Niedersachsen Lkw-Fahrverbot? · Welche Durchfahrtshöhen gibt es am Kölner Dom? · Where are the lorry bans in Dresden? |
🚧 stuck in traffic | How much time is the jam on the A3 between Frankfurt and Würzburg costing right now? · Is traffic backed up on the Cologne motorway ring — A1, A3 or A4? · Ist der Elbtunnel auf der A7 heute Nacht gesperrt? |
⚡ driving electric or on hydrogen | Where can I charge with Type 2 near Leipzig? · Which fast chargers near Leipzig are open around the clock and take a card? · Wo gibt es einen Schnelllader mit 150 kW bei Nürnberg? · Is there an EnBW charger with 150 kW or more in Stuttgart? · Where can I fill up a hydrogen lorry near Hamburg? · Where can my electric lorry charge near Munich? · Gibt es in Stuttgart kostenlose Ladesäulen? |
🅿️ parking | Is the P+R at Fröttmaning usually full in the morning? · Wie viele Plätze sind in den Kasseler Parkhäusern frei? · Which car parks in Trier have spaces? · Which car parks in Konstanz still have spaces? · How full are the lorry parks along the A9? · Is there a free disabled parking bay near Dortmund's Hansastraße? · Find a rest area with lorry parking on the A9 · Rastplatz mit Dusche an der A7? · Where can I park on the street near Hamburg Rathaus? |
⛽ filling up | Where is diesel cheapest near Kassel? · Welche Tankstellen gibt es in Weimar? |
♿ travelling step-free | Funktioniert der Aufzug am Bahnhof Köln Messe/Deutz? · Is Tübingen Hbf step-free? · Ist die Bushaltestelle Ludgeriplatz in Münster barrierefrei? · Which platforms at Leipzig Hbf are step-free? |
🌦️ watching the weather | Gibt es eine Unwetterwarnung für Freiburg? · Is the road near Garmisch going to be icy this morning? |
📍 looking for a place | What is the address of the Elbphilharmonie in Hamburg? · Welche Apotheken gibt es in Fulda? · Where is the nearest police station and public toilet in Fulda? · My satnav shows 50.1109, 8.6821 — what address is that? |
🇩🇪 new to German roads | Do I need an emission sticker for Stuttgart? · Is Marienplatz in Munich inside the low-emission zone? · Liegt Essen Hbf in der Umweltzone? · Is there a speed limit on the Autobahn? |
⏳ waiting for news | Tell me as soon as the closure on the A7 is lifted. · Tell me when a jam builds up on the A7. · Sag mir Bescheid, wenn in Köln ein Viertel oder mehr der Bus- und Bahnfahrten verspätet ist. · Warn me when a DWD severe-weather warning comes into force for Cologne. |
What the answers cover, honestly. Live traffic is the motorways, plus the measured traffic state of Hamburg's and Bonn's streets and the quarter-hour counts of Hamburg's counting sites (a count is a volume, never a jam). Closures and roadworks also cover Land roads in Niedersachsen, Nordrhein-Westfalen, Hessen, Baden-Württemberg, Mecklenburg-Vorpommern, Sachsen and Thüringen, federal roads there and in Schleswig-Holstein, Bayern and Berlin, the Autobahn GmbH's planned short-duration works on the motorways (a plan with its own window, never a closure before it begins), the city streets of Hamburg and Bremen, the works the city and Land portals publish (Kiel, Schleswig-Holstein, Brandenburg, Freiburg, Karlsruhe, Frankfurt, Berlin, Duisburg, Aachen, Ingolstadt, Köln, Münster, Dortmund, Stuttgart, München), the traffic reports some Länder and cities publish (Baden-Württemberg, Schleswig-Holstein, Berlin, Hamburg, Köln, Hannover, Kassel, Leipzig, Rüsselsheim am Main), and the state of Schleswig-Holstein's large bridges, and the traffic strategies the Autobahn GmbH (nationally and in Bayern) and Lower Saxony's NLStBV switch on, as their recommendation and only while switched; other city streets are not covered. Street detail around a place (signed detours, signal installations, on-street bays, loading bays, border crossings, winter service, pedestrian-zone entrances) exists only where a city or Land publishes it, and the answer names which. Lorry restrictions by place cover North Rhine-Westphalia's towns (SEVAS), Köln, Dresden, the Frankfurt RheinMain region (ivm) and Bremen; elsewhere the answer says it holds no data, which is never a clearance, and the long-lorry network covers the whole country. Departures cover every German stop from the timetable; a live delay appears where a realtime feed carries that trip (DELFI's national rail feed and, since 2.4.5, its fourteen regional feeds for every mode, its GTFS-RT, and VBB, VRN and VBN, with VBN's Connect in Niedersachsen and Bremen), and otherwise the answer says the time is the plan; a railway station's board also lists its U-Bahn and trams from the timetable. Live parking and charging occupancy exist only where the operator publishes them, and an answer never reads "no data" as free. A parking figure is shown as published, with the operator's status beside it; a reading the publisher stopped updating says when it was last reported, and one that cannot be right is called implausible. Truck-parking occupancy at the motorway rest areas (Toll Collect's SID) is shown only after the user accepts ViaFrei's terms of use, section 2, in the question the client asks; a client that cannot ask gets the lorry parks without it. A parking site's amenities (WC, shower, restaurant and more) are the ones its own publisher states; many state none, and an amenity nobody stated is unknown, not absent. A motorway's traffic light is green only when every source it reads is current and reports nothing, and even then it is no guarantee of a clear road. Fuel prices cover the stations we watch, not all of Germany. A charger's live status counts as current only while it is younger than its feed's own window; older, it is shown with its time as possibly out of date. Hydrogen stations are H2 Mobility's published list: pumps and opening hours, but no availability, price or working state, so check before you drive. Speed-camera locations are what seven towns publish (Düsseldorf, Karlsruhe with Rheinstetten, Köln, Aachen, Bottrop, Konstanz and Essen) and, where no official source covers a municipality, the fixed cameras mapped in OpenStreetMap, for planning only; a town none of them covers answers that nothing is published there, which never means that nobody checks. Places and addresses, and the everyday needs near a place (shops, pharmacies, police, toilets and the rest), come from OpenStreetMap, so what is not mapped there cannot be found, and ratings are not part of it. A watch lives in the conversation that opened it: the server keeps every change there, and your assistant shows it when you ask, or on its own if your client supports MCP notifications. Nothing is sent by e-mail or SMS. Up to 10 watches per conversation, each for up to 24 hours (3 by default), and a road is watched as a whole, not one section of it. On a motorway a watch can also report jams; on other roads and around a place it watches closures and restrictions only, and says so.
Related MCP server: db-mcp
💬 Real answers
These came back from the production server at https://mcp.viafrei.de/mcp. They
are not mock-ups. The first two were asked of server 2.6.14 on 2026-11-13 at 20:27
and 20:25 Berlin time, the evening it went live. The next two were asked of server
2.5.20 on 2026-11-08 at 11:34 and 11:35 Berlin time, and the two after them of
server 2.5.8 on 2026-11-04 at 01:13 Berlin time, in the night after it went live. The next five were asked of server
2.5.5 on 2026-11-03 at 03:20 Berlin time, a few hours after that release reached
production. The next three were asked of server 2.5.2 on 2026-11-02 between 03:56
and 04:10 Berlin time, in the night before 2.5.3 went live. The next was asked of
server 2.5.0 on 2026-10-29 at 17:48 Berlin time, the day it went live. The next was
asked of server 2.4.9 that
morning at 06:55. The next five were asked of server
2.4.3 on 2026-10-27 between 16:00 and 16:02 Berlin time, the day it went live, and
were asked again of server 2.4.9 on 2026-10-29 at 06:54: they answer in the same
shape, and their figures belong to the moment they were first captured. An "As of"
time earlier than a capture is the time the source was last read. The next four were asked of server
2.3.23 on 2026-10-25 between 15:04 and 15:06 Berlin time, the day it went live.
The next three were asked of server
2.3.18 on 2026-10-24 at 00:20 Berlin time. The next five were asked of server 2.3.12 on 2026-10-22
between 08:50 and 09:20 Berlin time; an "As of" time earlier than that is the
time the source was last read. The next nine were asked of server 2.2.14 on
2026-10-20 between 06:00 and 06:16 Berlin time. The next seven were asked of server 2.2.6 on
2026-10-19 between 07:34 and 07:45 Berlin time, the day it went live. The next two were asked of
server 2.1.25 on 2026-10-17 at 18:38 Berlin time, an hour after it went live. The next three were asked of
server 2.1.17 on 2026-10-14, around 22:40 Berlin time, minutes after it went live. The next three were asked
of server 2.1.8 on 2026-10-13 around 22:40, three more of server 2.1.5 that
afternoon, between about 14:50 and 16:20, and the others of server 2.0.10 that morning around
06:41. Those were asked again of server 2.1.17 on 2026-10-14 around 22:43 and
answer in the same shape; their figures, and the frost warning, belong to the
moment they were captured.
Each one shows the first lines of what the tool returned, and the source line as
it was sent, shortened where marked.
Note on use (§ 23 Abs. 1c StVO): a person driving a vehicle may not, while driving, operate or use any technical device or app function that shows or disrupts traffic enforcement. This also applies to a passenger's smartphone if the driver benefits from it (OLG Karlsruhe). A violation costs €75 and one point in Flensburg. This information is meant only for planning before setting off or during a stop. The locations come from official and open sources and may be incomplete or out of date; mobile checks are possible at any time and anywhere. Always keep to the speed limit in force. Not legal advice.
The notice in its original wording (German):
Hinweis zur Nutzung (§ 23 Abs. …
Speed enforcement — published locations for Bottrop (radius 5 km), by kind and street:
Measuring sites from the city's site table:
- Aegidistraße, Bottrop — speed · 30 km/h · direction Gladbecker Straße
- Aegidistraße, Bottrop — speed · 30 km/h · direction Horster Straße
- Aegidistraße, Bottrop — speed · 40 km/h · direction Gladbecker Straße
… and 7 more locations in this area.
Fixed cameras (OpenStreetMap):
- 51.52070, 6.93117 — speed · 50 km/h
- 51.52073, 6.93140 — speed · 50 km/h
- 51.52752, 6.99025 — speed · 70 km/h · direction 190
… and 6 more cameras mapped in OpenStreetMap in this area.
Stand Blitzerstandorte Bottrop: read 2026-11-13
Stand Blitzer (OpenStreetMap): read 2026-11-13, data as of 2026-10-27
Source: Blitzerstandorte Bottrop: Stadt Bottrop, Datenlizenz Deutschland – Zero – Version 2.0 (…) · Blitzer (OpenStreetMap): © OpenStreetMap-Mitwirkende, ODbL 1.0 (…) · Ortsdaten: © GeoNames (CC BY 4.0), bearbeitet (…) · As of 13:32New in 2.6.14: Bottrop's current speed-check sites, and the fixed cameras mapped in
OpenStreetMap as a block of their own. Bottrop lists its sites for mobile checks, so
they are measuring sites, never called cameras; because no official source we hold
publishes fixed cameras for Bottrop, OpenStreetMap's follow, with their own count and
their own credit, and limit applies to each block. The notice comes first, as in
every answer of this tool.
Edited: the German notice cut after its first sentence, and the URIs omitted.
Line RB33 (8 districts and cities combined): 15% of observed trips more than 5 minutes late (187 of 1,212 trips in the last 60 minutes, from 16,396 delay reports on these trips; reports in the window from 4,831 stops in all); in addition, 3 trips skip at least one stop (a detour, a closed stop or a trip ending early); 6 trips are cancelled here (none of the stops reported in the region served).
Line RB33 stops, per the timetable, in: Duisburg, Essen, Krefeld, Mönchengladbach, Mülheim an der Ruhr, Viersen, Städteregion Aachen, Heinsberg. The figures cover every trip in these districts; the service alerts are only those naming the line.
Trips are counted, not reports: a trip counts as late if it was reported more than 5 minutes late at least once during the window, even if it caught up afterwards.
Trend: better than the 60 minutes before (25%).
The source reports changes only: these figures cover the trips whose delay moved during the window, not every trip. Few reports therefore does not by itself mean "everything on time".
Trips the source cancels as a whole are reported without a stop, cannot be placed in a region and are not in this figure. Counted as cancelled are only trips all of whose reported stops here are skipped.
Individual lines, trips or stops cannot be judged from these delay figures — the realtime data arrives with no line reference, and its licence permits region-wide totals only.
Service alerts for Line RB33 (8 districts and cities combined): none of the alert sources I read has published an alert for this area in the last 14 days — none for this area has reached me since I began reading these sources, so "none in force" means nothing here — diversions or closures may still exist.
Source: Echtzeitdaten: DELFI e.V. via Mobilithek, CC BY-SA, bearbeitet (…) · Fahrplandaten: DELFI e.V., CC BY 4.0, bearbeitet (…) · Verwaltungseinheiten: © BKG (2026) dl-de/by-2-0, Datenquellen: https://sgx.geodatenzentrum.de/web_public/gdz/datenquellen/datenquellen_gn250.pdf (Daten verändert) (…) · As of 20:25
These figures are licensed CC BY-SA (share-alike) by their source; we release our adaptation under CC BY-SA 4.0 (https://creativecommons.org/licenses/by-sa/4.0/): anyone who passes them on, or builds something on them, must release the result under the same licence and with this attribution.New in 2.6.13: line. The figures cover the districts and cities the line stops in,
per the timetable; the realtime data carries no line reference, so they stay
region-wide, and only the service alerts are the line's own. Asked without a region,
the same question listed the seven regions where a line called RB33 runs and asked
which one was meant.
Not edited, except the URIs.
Charging around München (within 25 km, MCS), nearest first, sites wholly out of order last:
1. MAN, Dr.-Ernst-Zimmermann-Allee 5, 85757 München/Karlsfeld, 85757 Karlsfeld (München) — 11.5 km, MCS, up to 500 kW, 0.79 €/kWh, out of order (as of 11:21)
Every listed site reports all its matching points out of order.
Site id for watch_situation (kind "charger"): 1 = 2720
Source: Ladepunkte: Ampeco Ltd. (EDRI) via Mobilithek, CC0 1.0 (…) · Ladepunkt-Verfügbarkeit: Ampeco Ltd. (EDRI) via Mobilithek, Open Data (freie Nutzung) (…) · Verwaltungseinheiten: © BKG (2026) dl-de/by-2-0, Datenquellen: https://sgx.geodatenzentrum.de/web_public/gdz/datenquellen/datenquellen_gn250.pdf (Daten verändert) (…) · As of 11:21New in 2.5.13: connector: "mcs", the Megawatt Charging System. Within 25 km of
Munich one site had an MCS point, and its operator's live feed reported it out of
order at that moment, which the answer says rather than hiding the site; the site id
lets watch_situation report when it turns free. Asked the same of Hamburg and Kassel,
the server answered that none of the 2838 and 643 sites within 25 km has one, and
suggested widening the radius or dropping the filter.
Not edited, except the URIs.
No place given. Ask the person where: a town, a postcode or their position. Then pass the town (or postcode and town, "36037 Fulda") as place, or their position as lat+lon — for example {"place": "Fulda"} or {"lat": 50.55, "lon": 9.68}.New in 2.5.13: a refusal ends with a call that would work. The result is marked
isError, and _meta says "errorCode": "invalid_input" and
"errorReason": "place_missing", so a client can tell a question it must ask the
person from a fault of the server.
Not edited.
Leipzig Hbf — Station page: https://viafrei.de/en/station/leipzig-hbf
Willy-Brandt-Platz 5, 04109 Leipzig · Saxony · station category 1 (Bahnhofskategorie) · EVA 8010205
Step-free now (As of 01:03):
- step-free: Platform 1/2, Platform 6/7, Platform 8/8a/9, Platform 10/11, Platform 12/13, Platform 14/15, Platform 16/17, Platform 18/18a/19, Platform 20/21, Platform 22/23
Lifts and escalators (As of 01:03):
- Lift: state unknown
- Escalator (Platform 1/2): state unknown
…
- Lift (Platform 1/2): working
Platforms (As of 2026-11-03 03:39):
- Platform 1/2: step-free, platform height 55 cm
- Platform 6/7: step-free, platform height 76 cm
…
Departures (As of 01:13):
- 01:14 16 → Dölitz: on time
- 01:15 S3 → Halle (Saale) Hbf, Platform 2B-C: on time
- 01:43 11 → Angerbrücke: on time
Parking and charging:
- per DB: car park, bicycle parking, car rental, taxi rank
- Car parks and charging points nearby: find_parking or find_charging_station with lat 51.34547, lon 12.38206.
Source: Bahnhofsdaten: Deutsche Bahn AG, DB API Marketplace, CC BY 4.0, bearbeitet (…) · Aufzüge, Fahrtreppen und Bahnsteige (Bestand): Deutsche Bahn AG / DB InfraGO AG (OpenStation) via Mobilithek, CC0 1.0 (…) · Aufzüge und Fahrtreppen (Status): Deutsche Bahn AG / DB InfraGO AG (OpenStation) via Mobilithek, CC0 1.0 (…) · Aufzüge und Fahrtreppen: Deutsche Bahn AG, DB API Marketplace, CC BY 4.0, bearbeitet (…) · Fahrplandaten: DELFI e.V., CC BY 4.0, bearbeitet (…) · Echtzeitdaten: DELFI e.V. via Mobilithek, CC BY-SA, bearbeitet (…) · Echtzeitdaten: DELFI e.V. via Mobilithek, Datensätze „DELFI-Realtime SIRI ET“ (Bahndaten und 14 Regionen), CC BY-SA, bearbeitet (…) · As of 01:13
The DELFI SIRI ET and DELFI GTFS-RT realtime entries are licensed CC BY-SA (share-alike) by their source; we release our adaptation under CC BY-SA 4.0 (https://creativecommons.org/licenses/by-sa/4.0/): anyone who passes them on, or builds something on them, must release the result under the same licence and with this attribution.New in 2.5.8. One call answers what the station page shows, each block with its own "As of" time, and links the page. A lift whose state no source vouches for is said to be "state unknown", never "working". At 01:13 the next departures were the night's trams and one S-Bahn, because the board lists every mode the station serves. The parking and charging block names the two tools and the coordinates to ask with, rather than guessing a list. Edited: six of the ten lifts and escalators and eight of the ten platforms omitted, and the URIs omitted.
Hesse, motorways now: 10 closures, 3 warnings, 150 roadworks sites — on A3, A4, A5, A7, A44, A45, A49, A60, A66, A67, A480, A485, A659, A661, A671.
- A49 Brückenneubau (AS Edermünde (aus Richtung Felsberg) nach A49) — closure, 0.4 km, since 2026-10-19 00:00
- A49 Brückenneubau (Gießen -> Kassel) — closure, 0.1 km, since 2026-10-19 00:00
- A66 | Neuhof-Nord - Flieden (Fulda -> Frankfurt) — closure, 3.6 km, since 2026-11-03 22:00
- A66 | Flieden - Fulda-Süd (Frankfurt -> Fulda) — closure, 3.6 km, since 2026-11-03 22:00
- A661 Sperrung Richtungsfahrbahn (AS Frankfurt am Main-Eckenheim (aus Richtung Preungesheimer Dreieck)) — closure, 0.4 km, since 2025-09-01 00:00
…
153 more (next page: cursor).
How an item is placed: in the Land of the nearest Gemeinde centre (BKG, within 20 km); near a Land border that can be the neighbouring Land.
Page: https://viafrei.de/en/state/hessen
Source: Verkehrsdaten: Autobahn GmbH des Bundes (https://verkehr.autobahn.de) · Verwaltungseinheiten: © BKG (2026) dl-de/by-2-0, Datenquellen: https://sgx.geodatenzentrum.de/web_public/gdz/datenquellen/datenquellen_gn250.pdf (Daten verändert) (…) · As of 01:09New in 2.5.8: land instead of roads. The answer is the Land's motorways as its
page on viafrei.de shows them: the counts first, then what is in force, the rest one
cursor away. It says how an event is placed in a Land, because near a border the
nearest town can lie in the neighbouring one.
Edited: five of the ten closures shown, and the URIs after the BKG line omitted.
Note on use (§ 23 Abs. 1c StVO): a person driving a vehicle may not, while driving, operate or use any technical device or app function that shows or disrupts traffic enforcement. This also applies to a passenger's smartphone if the driver benefits from it (OLG Karlsruhe). A violation costs €75 and one point in Flensburg. This information is meant only for planning before setting off or during a stop. The locations come from official and open sources and may be incomplete or out of date; mobile checks are possible at any time and anywhere. Always keep to the speed limit in force. Not legal advice.
The notice in its original wording (German):
Hinweis zur Nutzung (§ 23 Abs. 1c StVO): Wer ein Fahrzeug führt, darf während der Fahrt kein technisches Gerät und keine App-Funktion betreiben oder nutzen, die Verkehrsüberwachungsmaßnahmen anzeigt oder stört. …
Speed enforcement — published locations for Düsseldorf (radius 5 km), by kind and street:
Fixed cameras:
- Auf´m Hennekamp, Düsseldorf — speed · 50 km/h
- Brehmplatz, Düsseldorf — red light
- Dreherstraße 225, Düsseldorf — speed · 50 km/h
- Kö-Bogen Tunnel, Düsseldorf — speed · 50 km/h
- Mörsenbroicher Ei, Düsseldorf — speed and red light · 50 km/h
- Rheinufertunnel Nord, Düsseldorf — speed · 60 km/h
… and 6 more locations in this area.
Stand Stationäre Verkehrsüberwachung Düsseldorf: read 2026-11-02, data as of 2024-03-13
Source: Stationäre Verkehrsüberwachung Düsseldorf: Landeshauptstadt Düsseldorf – Ordnungsamt, Datenlizenz Deutschland – Zero – Version 2.0 (…) · Verwaltungseinheiten: © BKG (2026) dl-de/by-2-0 (…) · As of 2026-11-02 18:45New in 2.5.4. The notice comes first, in the answer's language with the German
original beside it, and again as _meta.conditionNote, which an assistant is asked to
show verbatim; the structured result says "planningOnly": true. The list is in the
order of kind and street, never of distance, and says when the source was last read
and the date the publisher gives its data. Düsseldorf's file is the city's own list of
its stationary speed and red-light enforcement; Köln's tables are measuring sites and
are said as such, and Aachen's is a log of this year's mobile checks for the town as a
whole.
Edited: the German notice cut after its first sentence, and the URIs omitted.
Charging around Leipzig (within 10 km, ≥ 150 kW, open 24/7, card at the charger), nearest first, sites wholly out of order last:
1. Friedrich-Ebert-Str. 51, 04109 Leipzig (Stadtwerke Leipzig GmbH) — 1.1 km, CCS2, up to 170 kW, no status data, per charging point register
2. Hauptmannstr. 6, 04109 Leipzig (Stadtwerke Leipzig GmbH) — 1.3 km, CCS2, up to 150 kW, no status data, per charging point register
3. Am Sportforum 2, 04105 Leipzig (Stadtwerke Leipzig GmbH) — 1.8 km, CCS2, up to 180 kW, no status data, per charging point register
Only a few operators publish live occupancy; "no status data" means unknown, not free.
Price per kWh: not published for any of these sites (in the data we hold).
Charging point register as of 2026-09-01 — chargers as reported by their operators to the Bundesnetzagentur, with no live occupancy and no warranty of accuracy or completeness.
Only the Bundesnetzagentur charging register states these terms; sites that state nothing are left out, not ruled out.
Source: Ladesäulenregister: Bundesnetzagentur.de, CC BY 4.0, bearbeitet (…) · Verwaltungseinheiten: © BKG (2026) dl-de/by-2-0 (…) · As of 03:20New in 2.5.4: the conditions argument. Of 657 sites within 10 km, 14 met both terms
and the power ("sitesMatching": 14), and the three nearest are listed. Every one of
them comes from the Bundesnetzagentur's register, because no other source states
these terms; a site that states nothing is not offered as matching.
Not edited, except the URIs.
Near Fulda (within 5 km):
- police (within 2.0 km): Stadtwache Fulda - Polizei, police (0.2 km); Stadtwache Fulda - Ordnungspolizei, police (0.2 km); Bundespolizeirevier Fulda, police (0.6 km); Polizeistation Fulda, police (1.8 km); Polizeipräsidium Osthessen, police (1.8 km)
- public toilets (within 2.0 km): öffentliches BWC, toilets (0.1 km); öffentliches BWC, toilets (0.2 km); Rail & Fresh, toilets (0.6 km); Öffentliche Toilette, toilets (0.7 km)
Source: OSM-Standortdaten: © OpenStreetMap-Mitwirkende, ODbL 1.0 (…) · Verwaltungseinheiten: © BKG (2026) dl-de/by-2-0 (…)New in 2.5.4, split in 2.5.5: police and public toilets are two needs, each in its own
radius (2 km here, wider in a village, and the answer says so), up to five each. The
structured result carries them as needs.police and needs.toilets. The call asked
for a third need, health, whose doctors' practices are left out here.
Edited: the health line omitted, the URIs omitted.
The nearest stops around Köln-Ehrenfeld (within 5 km) with their next departures until 04:20:
Köln Ehrenfeld Bf Ehrenfeld (11 m) — stop_id de:05315:14201:2:21:
03:34 S19 → Hennef Bf, platform 1, +6 min (expected 03:40)
03:46 S19 → Düren, Bf, platform 2, on time
03:54 S19 → Troisdorf Bf, platform 1, no forecast
Köln Ehrenfeld Venloer Str./Gürtel (0.1 km) — stop_id de:05315:14211:1:11:
no departure until 04:20
…
Köln Müngersdorf Technologiepark S-Bahn (2.1 km) — stop_id de:05315:13501:7:71:
03:18 S19 → Kerpen Horrem Bf, platform 2, +3 min (expected 03:21)
03:31 S19 → Hennef Bf, platform 1, +7 min (expected 03:38)
…
More departures of one stop: get_departures with its stop_id.
Source: Fahrplandaten: DELFI e.V., CC BY 4.0, bearbeitet (…) · Echtzeitdaten: DELFI e.V. via Mobilithek, Datensätze „DELFI-Realtime SIRI ET“ (Bahndaten und 14 Regionen), CC BY-SA, bearbeitet (…) · …
The realtime figures from DELFI GTFS-RT and DELFI SIRI ET are licensed CC BY-SA (share-alike) by their source; we release our adaptation under CC BY-SA 4.0 (…): anyone who passes them on, or builds something on them, must release the result under the same licence and with this attribution.New in 2.5.4: a place (or lat/lon) instead of a stop. The answer is the place
page's card in words: the nearest stops of each kind, three departures for the nearest
stop that has any and two for each other, in the next hour, each with the stop_id
to ask about one stop in full. It was asked at 03:20 Berlin time, so most of the city's
stops had nothing before 04:20. Asked this way, limit, which applies to one named
stop, is refused with a sentence saying so.
Edited: three of the eight stops shown, the line naming what "timetable" means and
the URIs omitted.
Parking around Trier (within 10 km), nearest first:
1. DE - SWT TR PlazaCarree (8471) — Car park (Parkhaus), 0.2 km, 205 spaces, last reported 112 free, 45.37 % occupied, operator's status: spaces available (as of 2026-11-02 12:58, 14 h 22 min ago), Facilities: not reported
Nearby per OpenStreetMap (straight line): restaurant 10 m · snack bar 100 m · café 110 m · shop 120 m
Nearby (straight line): EV charger 22.1 kW, 140 m (Ladenetz)
…
3. DE - SWT TR Hauptmarkt (1257) — Car park (Parkhaus), 0.2 km, 328 spaces, last reported 109 free, 66.77 % occupied, operator's status: spaces available (as of 2026-11-02 12:58, 14 h 22 min ago), Facilities: not reported
…
Source: Parkhäuser und Parkplätze Trier: SWT Anstalt des öffentlichen Rechts der Stadt Trier via Mobilithek, Datensatz „Parkdatenerfassung Stadt Trier statisch (SWT)“, Datenlizenz Deutschland – Namensnennung – Version 2.0 (www.govdata.de/dl-de/by-2-0), Daten verändert (…) · Parkhaus-Belegung Trier: SWT Anstalt des öffentlichen Rechts der Stadt Trier … · …
Where no "free" count is shown the operator publishes no occupancy — it does not mean the site is full.New in 2.5.4: the Stadtwerke Trier's car parks, Trier's first parking source. At 03:20 the newest reading was from the afternoon before, so every count says "last reported" with its age instead of passing as current. The charger named beside each site is credited to ladenetz.de, one of smartlab's four charging publications that ended on 2026-10-19: at server 2.5.5 a site no other feed carried still answered with its place, plugs and power, dated, and never with a status; since server 2.5.6 such a site no longer answers (SOURCES.md). Edited: two of the four sites shown, OpenStreetMap's own car-park list and its notice omitted, the source line shortened.
"roads": ["A7"]
"counts": {"jams":0,"warnings":0,"closures":12,"roadworks":88,"announcedClosures":18,"announcedRoadworks":115,"announcedWarnings":0,"announcedFrom":"2026-11-02T05:00:00.000Z"}
"ampel": {"lamp":"red","scope":"road","reasonsTotal":122} — full closure · full closure · police/Land message: animals on the road · 10 × a junction ramp closed · 20 × DWD warning Level 1 of 4 — Wetterwarnung (the DWD's own name; our translation: weather warning) (FROST), placement on the road by ViaFrei · slippery road forecast (road-weather station Hittistetten Bruecke) · …
{"kind":"closure","title":"A7, AS Bispingen bis AS Garlstorf, km 44,5-37,0, Grundinstandsetzung","gist":"Closure on the A7; since 2026-10-13, until 19:00, whole measure until 2028-10-29.","entry":{"where":{"kind":"at","junction":{"name":"Egestorf","number":"41","type":"AS"},"land":{"name":"Lower Saxony"}},"impact":[{"code":"ramp_closed"}]}}
…
Source: Verkehrsdaten: Autobahn GmbH des Bundes (https://verkehr.autobahn.de) · Datenbasis: Deutscher Wetterdienst, zusammengefasst (…) · … · Verkehrsmeldungen Schleswig-Holstein: Landesmeldestelle Polizei Schleswig-Holstein via Mobilithek, Open Data (freie Nutzung) (…) · Arbeitsstellen kürzerer Dauer auf Autobahnen (geplant): Die Autobahn GmbH des Bundes | MIA via Mobilithek, eingeschränkte Nutzung, kostenfrei (…) · …
The road-weather station data are unverified point measurements and do not reflect conditions on a road section; … Planned short-duration roadworks are planned at short notice and often changed; …New in 2.5.2: "A07" is read as the A7 ("roads": ["A7"]), by the same rule the
site search uses for "A 7", "BAB 7" or "Autobahn 7". The schema of this tool takes
A and a number, with or without a space; the site search also takes the longer
spellings. At four in the morning the A7 had no jam, but its light was red for two
full closures and an animal on the road, and 18 closures were announced from 06:00
Berlin time (announcedFrom is UTC). Times in the structured result are UTC unless
they carry their own offset, as gist and entry do.
Edited: the three events cut to the first one, its entry shortened to where and
impact, the reason list, the police/Land messages and the planned short-duration
works shortened, the event identifiers and most of the source line omitted.
{"name":"VOLLERT STATION HYC","operator":"ChargePoint","address":"Stadtseestraße 12, 74189 Weinsberg","distanceKm":0.7,"connectors":["CCS2"],"maxPowerKw":150,"powerClass":"hpc","pricePerKwh":0.595,"availability":{"unknown":2,"total":2}}
{"operator":"ENBW","address":"Am Autobahnkreuz 9-13, 74189 Weinsberg","distanceKm":1.7,"connectors":["CCS2"],"maxPowerKw":300,"powerClass":"hpc","pricePerKwh":0.79,"availability":{"unknown":4,"total":4}}
{"operator":"ENBW","address":"Am Autobahnkreuz 2, 74248 Ellhofen","distanceKm":1.8,"connectors":["CCS2"],"maxPowerKw":300,"powerClass":"hpc","pricePerKwh":0.79,"availability":{"stale":24,"total":24},"staleStatusAsOf":"2026-11-01T07:39:10Z"}
…
Source: Ladepunkte: Eco-Movement via Mobilithek, CC BY 4.0, bearbeitet (…) · Ladepunkte: EnBW AG via Mobilithek, CC BY 4.0, bearbeitet (…) · Ladepunkt-Verfügbarkeit: EnBW AG via Mobilithek, CC BY 4.0, bearbeitet (…) · Verwaltungseinheiten: © BKG (2026) dl-de/by-2-0 (…)The two EnBW sites stand on the street named after the Weinsberger Kreuz, beside
the interchange. powerClass is the class the charging card prints beside each site
since 2.5.2: ac up to 22 kW, dc above that, hpc from 150 kW. No operator here published a live status that
night: the first two sites say unknown, which is never free, and the third
reports 24 points whose last status, from the morning before (08:39 Berlin time),
is older than its feed's window, so it is shown as possibly out of date.
Edited: one line per site with the address object written as one line, the
per-point list, the site identifiers and the source feed fields omitted, and the
source line shortened.
"isError": true
"_meta": {"errorCode":"invalid_input","errorReason":"place_and_coords"}
The place "Weinsberg" is 492 km from lat/lon — further than the 15 km searched here. Ask the person which one they mean, and pass only the place OR lat+lon.New in 2.5.2: a place and a coordinate may come together. Within the tool's search
reach of each other the coordinate answers and the place is its label; 492 km apart,
as here, the call is refused with the distance, and _meta.errorReason names the
rule. The same tool given lat without lon answers "errorReason":"half_coordinate"
and "lat and lon go together: give both, or give place instead."
Not edited.
{"line":"ICE 200","destination":"Hamburg-Altona","plannedAt":"…T16:22:00Z","delayMin":30,"platform":"13","place":"track"}
{"line":"S3","destination":"Hamburg-Neugraben","plannedAt":"…T16:46:00Z","delayMin":4,"platform":"3","place":"track"}
{"line":"ICE 1275","destination":"Berlin Gesundbrunnen","plannedAt":"…T16:51:00Z","delayMin":0,"platform":"8","place":"track"}
{"line":"RE1","destination":"Büchen","plannedAt":"…T16:55:00Z","delayMin":0,"platform":"7A-D","place":"track"}
"capped": {"shown":10,"more":13}, "interchange": U1, U2, U3, U4 and the buses, with their own departures
…
Source: Fahrplandaten: Deutsche Bahn AG, DB API Marketplace, CC BY 4.0, bearbeitet (…) · Bahnhofsdaten: Deutsche Bahn AG, DB API Marketplace, CC BY 4.0, bearbeitet (…) · … · Echtzeitdaten: DELFI e.V. via Mobilithek, CC BY-SA, bearbeitet (…)
The DELFI GTFS-RT realtime entries are licensed CC BY-SA (share-alike) by their source; we release our adaptation under CC BY-SA 4.0 (…): anyone who passes them on, or builds something on them, must release the result under the same licence and with this attribution.New in 2.5.0: the RE1's platform "7A-D" — track 7, sections A to D, written without
a space — is read as a track ("place": "track"), so the English answer says "platform
7A-D" and the German one "Gleis 7A-D". Before 2.5.0 such a row fell through as
plain text. Times are UTC in the structured result: the ICE 200, planned at 17:22
Berlin, was expected at 17:52, 30 minutes late. The U-Bahn departures of the
interchange come in a list of their own, and because the realtime is DELFI's, the
answer carries the share-alike sentence.
Edited: four of the ten departures shown, one line each, the station's other
fields and the full attribution omitted.
Departures from Hannover Kröpcke — timetable with realtime, 06:55 to 07:55:
06:56 metro 1 → Laatzen, platform #3/SB, on time
06:56 metro 4 → Hannover Roderbruch, platform #5/SB, on time
06:56 metro 7 → Hannover Wettbergen, platform #1/SB, on time
06:57 metro 1 → Langenhagen, platform #4/SB, +2 min (expected 06:59)
06:57 bus 100 → Hannover August-Holweg-Platz, stand Bus18, on time
06:57 bus 120 → Hannover Ahlem, stand Bus17, on time
06:57 metro 4 → Garbsen, platform SB6, on time
06:57 metro 7 → Hannover Misburg, platform #2/SB, +1 min (expected 06:58)
… and 148 more in the window.
…
Source: Fahrplandaten: DELFI e.V., CC BY 4.0, bearbeitet (…) · … · Echtzeitdaten: DELFI e.V. via Mobilithek, CC BY-SA, bearbeitet (…) · Echtzeitdaten: DELFI e.V. via Mobilithek, Datensätze „DELFI-Realtime SIRI ET“ (Bahndaten und 14 Regionen), CC BY-SA, bearbeitet (…) · As of 06:55
The realtime figures from DELFI GTFS-RT and DELFI SIRI ET are licensed CC BY-SA (share-alike) by their source; we release our adaptation under CC BY-SA 4.0 (…): anyone who passes them on, or builds something on them, must release the result under the same licence and with this attribution.New in 2.4.5: the Stadtbahn and the buses carry a live figure. In the structured
result seven of these eight departures have "source": "delfi_siri_et", DELFI's SIRI ET,
which since 2.4.5 includes fourteen regional feeds that carry buses, trams and the
Stadtbahn as well as trains, and one has
"source": "delfi_rt_tu", the GTFS-RT Trip Updates. Each departure gets one figure,
from the feed whose call agrees with where it is going; a departure no live feed
covers says "timetable". The same question about Bremen Hauptbahnhof also credits
VBN's Connect timetable and realtime, which answer for Niedersachsen and Bremen since
2.4.5. Live figures from DELFI are share-alike, and the answer says so in a sentence
of its own.
Edited: the stop id for watch_situation and the stops read with it, the
administrative-units credit, the line on where the realtime comes from and how far
the timetable reaches, and the URIs omitted.
A3 — traffic light red: full closure (and 109 more reasons).
A3, road-wide: 11 jams, 4 closures, 104 roadworks sites; plus police/Land messages: 3 jams, 6 restrictions, 8 roadworks sites, 6 reports; announced from 18:00: 49 closures, 110 roadworks sites — As of 16:01. Traffic state at 127 measuring sites (NRW, as of 15:58): 29 standstill, 5 slow, 29 heavy, 64 free-flowing; standstill or slow near Bonn/Siegburg, Duisburg-Wedau, Köln-Dellbrück; …
• Traffic jam (Stau): A3, end of the jam 2.7 km past AS Leverkusen-Zentrum, about 10.0 km long, growing (about 8.9 km 17 min ago), since 15:39, +57 min — between junction Leverkusen-Zentrum and junction Königsforst, towards Frankfurt — Provider text (German): "A3 | Leverkusen-Zentrum - Königsforst · Oberhausen -> Frankfurt — […] Angespannte Verkehrslage […] …"
• Traffic jam (Stau): A3, end of the jam 0.8 km past AS Iggensbach, about 6.6 km long, since 15:25, +18 min — between junction Iggensbach and junction Hengersberg, towards Nürnberg — …
…
Source: Verkehrsdaten: Autobahn GmbH des Bundes (https://verkehr.autobahn.de) · Verkehrslage Nordrhein-Westfalen: © Die Autobahn GmbH des Bundes 2026 — GeoNutzV, Daten verändert (…) · TMC Location Code List (LCL 22.0): Bundesanstalt für Straßenwesen (BASt), CC BY 4.0 (…), bearbeitet (…) · …And the first jam's entry in the structured result, new in 2.4.1 (the map links
shortened):
"entry": {
"where": { "kind": "pair",
"from": { "name": "Köln-Mülheim", "number": "25", "type": "AS" },
"to": { "name": "Leverkusen-Zentrum", "number": "24", "type": "AS" },
"town": { "name": "Leverkusen", "ags": "05316000" },
"land": { "ags": "05", "name": "North Rhine-Westphalia" },
"placedBy": "ViaFrei" },
"direction": { "kind": "toward", "toward": "Frankfurt" },
"when": { "from": "2026-10-27T15:39+01:00", "to": null, "running": true, "moreWindows": 0 },
"impact": [ { "code": "jam" } ],
"what": { "kind": "Traffic jam (Stau)", "measure": null, "terms": [] },
"at": { "lat": 51.00005, "lon": 7.01323 },
"maps": { "osm": "https://www.openstreetmap.org/?mlat=51.00005&mlon=7.01323…", "google": "…" }
}Every jam, closure and works site of the three road tools carries the same five
answers: where (the junction pair, the town and the Land), which way, when, what it
means for a driver and what the work is. where places the entry's own point (at,
here the end of the jam, 2.7 km past Leverkusen-Zentrum) between the two junctions
around it, while the publisher's title above names the whole stretch the jam covers.
An assistant can say where, which way and since when without parsing the publisher's
text, and link the map.
Edited: the condition notes that open the answer, the rest of the first jam's
provider text, the third jam, the short-duration works listed after it, and most of
the source line omitted.
Charging around Stuttgart (within 10 km, ≥ 150 kW, operator EnBW), nearest first, sites wholly out of order last:
1. Rotebühlstr. 30, 70178 Stuttgart (ENBW) — 0.7 km, CCS2, up to 300 kW, 0.79 €/kWh, status from 2026-10-24 02:22 — possibly out of date
2. Keplerstraße 7, 70174 Stuttgart (ENBW) — 0.7 km, CCS2, up to 300 kW, 0.79 €/kWh, status from 2026-10-24 04:47 — possibly out of date
3. Am Neckartor 2, 70190 Stuttgart (ENBW) — 1.5 km, CCS2, up to 300 kW, 0.79 €/kWh, no status data
…
Only a few operators publish live occupancy; "no status data" means unknown, not free.
Source: Ladepunkte: EnBW AG via Mobilithek, CC BY 4.0, bearbeitet (…) · Ladepunkt-Verfügbarkeit: EnBW AG via Mobilithek, CC BY 4.0, bearbeitet (…) · …New in 2.4.3: operator and max_power_kw. Spellings of one brand match together
(the register's "ENBW" above), and the structured result says how many of the radius's
sites the filter kept (sitesMatching 10 of sitesInRadius 1,580 here). Where no
site matches, the answer says how many it looked at and suggests widening the radius
or dropping the filter. A status older than its feed's own window is shown with its
time, never as free.
Edited: two more sites, the site ids for watch_situation and most of the source
line omitted.
Departures from Berlin Alexanderplatz (next 60 minutes):
16:02 S9 → Flughafen BER (S-Bahn), platform 3, on time
16:03 S9 → Berlin-Spandau (S), platform 4, on time
16:05 S3 → Berlin Charlottenburg (S), platform 4, on time
…
U-Bahn, Stadtbahn and tram at this station (DELFI timetable; realtime where DELFI GTFS-RT reports it):
16:01 tram M4 → S Hackescher Markt (Berlin) (per timetable, platform Pos. 11)
16:01 U5 → U Hönow (Berlin) (per timetable, platform 2 (U5))
16:02 U2 → S+U Pankow (Berlin) (per timetable, platform 2 (U2))
…
Lines here: metro: U2, U5, U8 · tram: M4, M5, M6 · bus: 025, 060, 065, 070, 100, 157, 170, 200, …
Source: Fahrplandaten: Deutsche Bahn AG, DB API Marketplace, CC BY 4.0, bearbeitet (…) · Bahnhofsdaten: Deutsche Bahn AG, DB API Marketplace, CC BY 4.0, bearbeitet (…) · Fahrplandaten: DELFI e.V., CC BY 4.0, bearbeitet (…) · Haltestellendaten: DELFI e.V. (zentrales Haltestellenverzeichnis), CC BY 4.0, bearbeitet (…) · As of 16:00New in 2.4.3: a railway station that is also an interchange lists its U-Bahn, Stadtbahn and trams below the trains, from the timetable with realtime where the feed reports it, and names every line that calls there. One question about the station answers for all of it. Edited: seven more trains, seven more U-Bahn and tram departures and most of the bus lines omitted.
Parking around Konstanz (within 10 km), nearest first:
1. Fischmarkt — Car park (Parkhaus), 0.2 km, 161 spaces, 15 free, 90.68 % occupied, operator's status: almost full (as of 15:52), Facilities: not reported
Nearby per OpenStreetMap (straight line): restaurant 30 m · shop 30 m · café 40 m · snack bar 120 m · toilet 210 m
2. Altstadt — Car park (Parkhaus), 0.3 km, 359 spaces, 15 free, 95.82 % occupied, operator's status: almost full (as of 15:52), Facilities: not reported
3. Marktstätte — Car park (Parkhaus), 0.4 km, 277 spaces, 93 free, 66.43 % occupied, operator's status: spaces available (as of 15:52), Facilities: not reported
4. Augustiner / Karstadt — Car park (Parkhaus), 0.4 km, reported closed (as of 2026-10-22 14:12, 122 h 48 min ago), Facilities: not reported
5. Benediktinerplatz — Car park (Parkhaus), 0.7 km, 40 spaces, last reported 16 free, 60 % occupied, operator's status: spaces available (as of 2026-10-22 14:12, 122 h 48 min ago), Facilities: not reported
…
Source: Parkhäuser Konstanz: Stadt Konstanz via Mobilithek, Datensatz „Parkdaten Stadt Konstanz statisch“, CC BY 4.0, bearbeitet (…) · Parkhaus-Belegung Konstanz: Stadt Konstanz via Mobilithek, Datensatz „Parkdaten Stadt Konstanz dynamisch“, CC BY 4.0, bearbeitet (…) · OSM-Standortdaten: © OpenStreetMap-Mitwirkende, ODbL 1.0 (…) · …
Where no "free" count is shown the operator publishes no occupancy — it does not mean the site is full.New in 2.4.2 and 2.4.3: the city of Konstanz's own car-park feed (Wiesbaden's joined in the same release), and every figure as the operator publishes it, with the operator's status beside it. Rows 4 and 5 show the honest part: their last reading is five days old, so they say "reported closed" and "last reported" with the time, and are never presented as current. MobiData BW's bundle carries some of the same lots; a lot both publish is listed once. Edited: the nearby lines of rows 2 to 5, the chargers near each site, the OpenStreetMap notice and car-park list, and most of the source line omitted.
Parking along the A9:
…
2. 24-TOTAL Autohof Leipzig Flughafen — Lorry parking (Lkw-Parkplatz), 151 spaces, 151 of them for lorries, no occupancy published, Facilities: not reported
3. Aral Autohof Bad Berneck — Lorry parking (Lkw-Parkplatz), 220 spaces, 120 of them for lorries, no occupancy published, Facilities: not reported
…
Truck-parking occupancy (Toll Collect, SID) is given only after accepting ViaFrei's terms of use, section 2 (https://viafrei.de/en/terms#sid); this client cannot ask for acceptance (MCP elicitation); it is available in a client that can, or on viafrei.de with "Show occupancy". The lorry parks above are therefore listed without it.
Source: Verkehrsdaten: Autobahn GmbH des Bundes (https://verkehr.autobahn.de) · LKW-Parken: © Lkw-Parken BAB Deutschland / Bundesministerium für Verkehr (BMV) 2026 — GeoNutzV, Daten verändert (…) · …New in 2.4.3. The Toll Collect Stellplatz-Informationsdienst publishes the occupancy of the motorway rest areas, and its terms require that everyone who receives the figures is bound by them. So the server asks first: a client that supports MCP elicitation shows the user the question, and the figures follow only on an explicit yes. This capture came from a client that cannot ask, so the answer lists the lorry parks without the figures and says where to get them. An assistant must never accept for the user. Edited: three more lorry parks, the nearby lines, the OpenStreetMap notice, the line saying the list is in name order, most of the source line and the closing sentence on missing free counts omitted.
A7 — traffic light red: full closure (and 146 more reasons).
A7, road-wide: 6 jams, 12 closures, 101 roadworks sites; plus police/Land messages: 18 restrictions, 3 roadworks sites, 2 reports; announced from 2026-10-26 07:00: 28 closures, 132 roadworks sites — As of 15:04. Delay per direction: Fulda → Würzburg +23 min (1 jam); Hamburg → Hannover +32 min (2 jams); Hannover → Hamburg +21 min (2 jams); Würzburg → Fulda +7 min (1 jam). +1 more in the structured result.
• Traffic jam (Stau): A7, end of the jam 0.6 km past Am Forsthaus, about 3.6 km long, growing (about 3.1 km 27 min ago), since 13:01, +23 min — between Am Forsthaus and Speicherz, towards Würzburg — Provider text (German): "A7 | Am Forsthaus - Speicherz · Fulda -> Würzburg — […] Angespannte Verkehrslage […]"
• Traffic jam (Stau): A7, end of the jam 0.9 km past Maschener Kreuz/A39, about 2.6 km long, steady (about 2.4 km 27 min ago), since 13:40, +10 min — between Maschener Kreuz/A39 and Harburger Berge, towards Hamburg — …
…
Source: Verkehrsdaten: Autobahn GmbH des Bundes (https://verkehr.autobahn.de) · Verkehrsmeldungen der Polizei: Landesbetrieb Straßenbau NRW (VIZ.NRW) via Mobilithek, … · Arbeitsstellen kürzerer Dauer auf Autobahnen (geplant): Die Autobahn GmbH des Bundes | MIA via Mobilithek, eingeschränkte Nutzung, kostenfrei (…) · Datenbasis: Deutscher Wetterdienst, zusammengefasst (…) · As of 15:04The traffic light (since 2.3.9) is one national rule: red for a closure of the carriageway, a jam of 30 minutes or more, a safety message or a DWD warning of level 3 or above; green only when every source it reads is current and reports nothing. A jam says where it ends, how long it is, since when and whether it is growing. The short-notice works of the Autobahn GmbH are listed beside the live situation only while their planned window holds, and never count towards the light. Edited: the condition notes that open the answer (road-weather stations, the Baden-Württemberg traffic-warning service, the short-duration works), four more jams, the closures and planned works, and most of the source line omitted.
Planned short-duration roadworks are planned at short notice and often changed; they replace neither a permit for oversize and heavy transports nor the route check before setting off (our translation of the publisher's note).
A3: 28 planned roadworks sites between 2026-10-25 and 2026-11-01. 10 of them are in this answer — raise limit to 20 for the rest. Not current and therefore not used: BASt (roadworks), Autobahn GmbH (roadworks, next 14 days).
• Construction works (Baustelle): A3 — nearest junction: Oberhausen-Lirich (placed by ViaFrei) — 2 of 3 lanes closed, hard shoulder closed — planned 2026-10-24 20:00–2026-10-25 05:00; 2026-10-25 20:00–2026-10-26 05:00; 2026-10-26 20:00–2026-10-27 05:00 (+3 more dates) — Provider text (German): "A3 DB BW Längsfugenabdichtung - A3 DB BW Längsfugenabdichtung; Bauwerksarbeiten"
• Maintenance works (Instandsetzung): A3 — nearest junction: Frankfurt am Main-Flughafen (placed by ViaFrei) — 1 of 3 lanes closed, others restricted — per the plan now 2026-10-25 08:00–18:00 — Provider text (German): "A3 von Kelsterbach (AS) nach Frankfurter Kreuz (AK) Fahrbahninstandsetzung - …"
…
Source: Arbeitsstellen kürzerer Dauer auf Autobahnen (geplant): Die Autobahn GmbH des Bundes | MIA via Mobilithek, eingeschränkte Nutzung, kostenfrei (…) · TMC Location Code List (LCL 22.0): Bundesanstalt für Straßenwesen (BASt), CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/), bearbeitet (…) · As of 14:53, unchanged since 14:37New in 2.3.21: the Autobahn GmbH's short-duration works (AkD), the night and day closures it plans at short notice. Each is listed with the windows the publisher states, a series of nights as separate windows, "planned" until a window opens and "per the plan now" inside it, and never as a closure that has begun. The publisher's note goes with every answer that carries one. This answer also shows the honest gap: two other roadworks sources were not current at that moment, so the answer names them and does not use them. Edited: eight more sites and the planning-data note at the end omitted.
B49: 14 roadworks sites between 2026-10-25 and 2026-11-01, 5 of them already begun. None in Niedersachsen, Sachsen, Thüringen, Baden-Württemberg, Bayern, Mecklenburg-Vorpommern or Nordrhein-Westfalen — all 14 in Hessen. 10 of them are in this answer — raise limit to 20 for the rest.
• Construction works (Baustelle) (Hessen): B49 — 1 of 2 lanes closed, phase 2026-08-24 until 2026-11-27 — 2026-08-21 until 2026-11-27 — Provider text (German): "Limburg a.d. Lahn-Linden; Bauwerksarbeiten"
• Lane management (Verkehrsführung) (Hessen): B49 — 1 of 1 lanes restricted, all open, phase 2026-10-13 until 2026-11-09 — 2026-10-12 until 2026-11-10 — Provider text (German): "Limburg-Gießen; Auf-/Abbau Verkehrsführung"
• Maintenance works (Instandsetzung) (Hessen): B49 — planned 2026-10-26 08:00–17:00 — Provider text (German): "Limburg a.d. Lahn-Leun; Arbeiten an Schutzeinrichtungen"
…
Source: Arbeitsstellen Hessen: Hessen Mobil (Daten verändert) via Mobilithek, GeoNutzV (https://mobilithek.info/) · As of 14:35New in 2.3.21: Hessen Mobil's works on Bundes-, Landes- and Kreisstraßen, and the Landesbetrieb Straßenbau NRW's works off the motorways. The credit is the source note GeoNutzV prescribes, "Hessen Mobil (Daten verändert)", with its link. Edited: seven more sites and the closing note naming the covered Länder omitted.
Charging around Krautheim (within 10 km), nearest first, sites wholly out of order last:
1. Krautheim - Ladesäule Krautheim, Götzstraße 47, 74238 Krautheim (Regioladen+ GmbH & Co. KG) — 0.6 km, Type 2, up to 22 kW, 0.62 €/kWh net, 2 of 2 free (as of 15:04)
2. Uferweg 12, 74238 Krautheim (Rüdinger Spedition GmbH) — 0.8 km, CCS2, up to 400 kW, no status data, per charging point register (4 charging units)
3. Krautheim — 0.8 km, CCS2/Type 2, up to 400 kW, 0.48 €/kWh, occupied, 18 without status (as of 14:39)
…
Only a few operators publish live occupancy; "no status data" means unknown, not free.
…
Source: Ladepunkte: chargecloud GmbH via Mobilithek, CC0 1.0 (…) · … · Ladepunkte: ELU Mobility via Mobilithek, Open Data (freie Nutzung) (…) · Ladepunkt-Verfügbarkeit: ELU Mobility via Mobilithek, Open Data (freie Nutzung) (…) · …New in 2.3.23: ELU Mobility's charging park at Krautheim, up to 400 kW, answers with its
live status: row 3, the park's 26 points, with the status the operator publishes. Row 2
is the Bundesnetzagentur's register at the same spot, which never carries a status. eliso, TC-Backend and Chargepool joined in the same release.
A "Krautheim" alone asks which one: there are three.
Edited: two more sites, the site ids for watch_situation, the price and register
notes and most of the source line omitted.
2 official notices for Kiel, highest level 1 of 4:
1. Level 1 of 4 — Wetterwarnung (the DWD's own name; our translation: weather warning) — Wind gusts (WINDBÖEN)
Area: Stadt Kiel (warn cell 801002000)
Valid: from 2026-10-24 04:00 until 2026-10-24 12:00
Official DWD wording in English (the DWD's own text), reproduced unaltered:
„Official WARNING of WIND GUSTS“
„There is a risk of wind gusts (level 1 of 4).
Max. gusts: < 60 km/h; Wind direction: south then south-west“
For the drive: Gusts can push vehicles sideways; take particular care on bridges, in woodland and when overtaking lorries.
…
Quelle: Deutscher Wetterdienst (https://www.dwd.de/copyright; Lizenz: CC BY 4.0, …) · …New in 2.3.17 and 2.3.18. The warning text is the DWD's own English, unaltered, so it keeps the DWD's Quellenvermerk. The level name stays German ("Wetterwarnung") with our gloss beside it, because a German official level has no official English name. The driving sentence is ours. On viafrei.de, where the DWD has no English text and in the other twenty languages, the card shows the German original as the binding text beside our labelled translation. Edited: the road-weather condition note that opens the answer, two DWD lines on the level and its CAP fields, the hazard text, the second warning, the road-surface forecast and most of the source line omitted.
Charging around Hamburg Hbf (within 10 km), nearest first, sites wholly out of order last:
1. Heidi-Kabel-Platz, 20099 Hamburg — 0.2 km, Type 2, up to 22 kW, 0.50 €/kWh, 3 of 4 free (as of 00:19) (2 charging units)
2. Mönckebergstr. 1, 20095 Hamburg (E.ON Drive Infrastructure) — 0.3 km, CCS2, up to 150 kW, no status data, per charging point register
3. Borgesch 1, 20099 Hamburg (Hamburger Energiewerke) — 0.3 km, Type 2, up to 22 kW, no status data, per charging point register; CCS2/Type 2, up to 50 kW, no status data, per charging point register (2 charging units)
4. Hühnerposten 14, 20097 Hamburg — 0.4 km, Type 2, up to 22 kW, 0.50 €/kWh, status from 2026-10-23 20:01 (4 h 19 min ago) — possibly out of date
…New in 2.3.15: the charge points of one site that differ only in their momentary status
are one line ("3 of 4 free"), and a site that its operator names only by a code is named
by its address. A status older than its feed's own window is shown with its time and
"possibly out of date", never as free.
Edited: two more sites, the site ids for watch_situation and the source line
omitted.
Low-emission zone and plaque — Hannover:
Hannover: the Umweltzone Hannover was lifted on 22.02.2024 according to the Umweltbundesamt; no plaque is needed there any more — the signs on the spot still decide.
…
Source: Verkehrsregeln: ViaFrei, eigene Zusammenstellung aus amtlichen Quellen (…) · Umweltzonen in Deutschland: Umweltbundesamt, Datenlizenz Deutschland – Namensnennung – Version 2.0, bearbeitet (…)
Reviewed 2026-09-19 · Informational, not legal advice.New in 2.3.14: the zone list follows the Umweltbundesamt's list of 2026-10-22, with 35 zones in force and 23 lifted. A lifted zone is said as lifted, with its date, instead of "no zone". Edited: the general rules on plaques and fines and the links in the source line omitted.
A7 — traffic light red: full closure (and 156 more reasons).
A7, road-wide: 3 jams, 1 warning (accident, hazard etc.), 13 closures, 128 roadworks sites; announced from 09:00: 26 closures, 125 roadworks sites — As of 08:47. Delay per direction: Flensburg → Hamburg +72 min (2 jams); Hannover → Hamburg +11 min (1 jam). +1 more in the structured result.
• Traffic jam (Stau): A7, end of the jam 2.0 km past AS Bad Bramstedt, about 3.9 km long, steady (about 3.9 km 13 min ago), since 07:03, +47 min — between junction Bad Bramstedt and junction Kaltenkirchen, towards Hamburg — Provider text (German): "A7 | Bad Bramstedt - Kaltenkirchen · Flensburg -> Hamburg — […] Angespannte Verkehrslage […]"
…New in 2.3.9 (the traffic light) and 2.3.5 (the jam's end, length, trend and the delay per direction). The light follows one national rule: red for a closure of the carriageway, a jam of 30 minutes or more, a safety message, a DWD warning of level 3 or above or a closed bridge; yellow for a shorter jam, roadworks, a closed ramp, a lower warning or a source we cannot see right now; green only when every source is current and reports nothing, and even then the answer says it is no guarantee of a clear road. The structured result lists each reason with its source, and groups roadworks and closed ramps ("11 × a junction ramp closed"). Edited: the end of the provider text, the other entries and the source line omitted.
Parken an der A7:
1. Aalbek — Lkw-Parkplatz, 207 Plätze, davon 89 für Lkw, keine Belegungsdaten veröffentlicht, Ausstattung laut Herausgeber: WC · Dusche · Tankstelle · Picknickplatz · Spielplatz
In der Nähe laut OpenStreetMap (Luftlinie, Erreichbarkeit nicht geprüft): Imbiss 110 m · Restaurant 120 m · Café 130 m
In der Nähe (Luftlinie, Erreichbarkeit nicht geprüft): Ladesäule 350 kW, 50 m (IONITY)
2. Allgäuer Tor Ost — Lkw-Parkplatz, 95 Plätze, davon 28 für Lkw, keine Belegungsdaten veröffentlicht, Ausstattung laut Herausgeber: WC · Dusche · Trinkwasser · Picknickplatz
In der Nähe laut OpenStreetMap (Luftlinie, Erreichbarkeit nicht geprüft): Restaurant 30 m · Café 40 m
…
Nur Anlagen, deren Herausgeber Dusche angibt. 194 von 447 Anlagen hier nennen überhaupt eine Ausstattung — bei den übrigen ist sie unbekannt, nicht ausgeschlossen.New in 2.3.10. "Ausstattung laut Herausgeber" is what the site's own publisher states, and only that answers the filter. The two "In der Nähe" lines are what OpenStreetMap and the charging register show close by, in a straight line and with access not checked: they are listed for the driver and never counted as the site's own. The last line says how many sites state any amenity at all, so a short list is not mistaken for "no showers on the A7". An OpenStreetMap row carries the ODbL offer (see SOURCES.md). Edited: three of five sites, the ODbL lines, a note on the order of the list and the source line omitted.
No ICE train leaves Tübingen Hbf in the next 60 minutes.
12 other trains of another type leave in the window and are not listed.
The DELFI timetable names no product for long-distance trains, so it cannot tell whether any ICE train runs.
Station asked: Tübingen Hbf (station number 8000141).New in 2.3.11 and 2.3.12. An empty board now says what it checked: how many trains of other types leave, whether the DELFI timetable lists a train either, and here that the timetable cannot tell an ICE from another train, so it is not asked to. Where the timetable files a rail replacement bus near the station, the answer names it. When DB's board cannot be read at all, the next planned train answers instead of an error, marked as planned. Edited: the source line omitted.
Parking around Berlin-Wannsee (within 10 km), nearest first:
1. Wannsee P1 — Park and ride (P+R), 0.2 km, 33 spaces, free of charge, no occupancy published, Facilities: not reported
Nearby per OpenStreetMap (straight line): shop 190 m · restaurant 210 m · snack bar 230 m
Nearby (straight line): EV charger 3.7 kW, 10 m (Ubitricity)
2. Potsdam Hauptbahnhof - Parkhaus Bahnhofspassagen — Park and ride (P+R), 8.2 km, 1392 spaces, no occupancy published, Facilities: not reported
…Berlin's park-and-ride register (Land Berlin, with the surrounding area from VBB) answers now. It had had no successful read when SOURCES.md was last compared, at server 2.2.14. "Facilities: not reported" is said as unknown. Edited: the remaining sites, the ODbL lines and the source line omitted.
I do not find "Heisfeldr Straße 10, Leer" in the OpenStreetMap address data: addresses are mapped in Leer (Ostfriesland), Lower Saxony, but none on a street of this name.
Streets there with a similar name: Heisfelder Straße (26789 Leer (Ostfriesland)) — 114 mapped addresses.New in 2.3.2. A near miss says whether the town or only the street is missing from the map, and suggests the similar streets nearby with how many addresses each holds. Edited: the source line omitted.
Hamburg Hbf: 1 jam report, 176 closures, 291 restrictions, 2 planned roadworks sites, 13 current roadworks sites per BASt — window until 2026-10-21.
I do not hold federal and Land roads (Bundes-, Landes-/Staatsstraßen) for Hamburg: for those, this answer is no all-clear.
Measured traffic state (Hamburg, BVM (traffic state), as of 06:00) within 10 km: 952 segments: jammed traffic: 3, slow traffic: 35, dense traffic: 914 — nearest segment (jammed traffic or slow traffic) 1.1 km away, main road; the source does not list free-flowing segments — a segment it does not list is flowing or not measured.
Counted traffic within 1.0 km (BVM counting sites (Hamburg)): counting site 0330, cross-section 4 (0.1 km), 05:30–05:45: no cross-section total (not every direction counted); by direction: west to east 37 · counting site 0331, cross-section 3 (0.2 km), 05:30–05:45: 53 motor vehicles; by direction: northeast to southwest 34, southwest to northeast 19. Further cross-sections in reach: 2. A count is a volume per quarter hour, not a statement about congestion or free flow.
• Traffic jam (Stau) A1: Provider text (German): "A1 | Tunnel Moorfleet - Norderelbbrücke · Lübeck -> Hamburg" (since 05:26; +10 min; 7.6 km away)
…
Signed motorway detours nearby (signs 460/455): U 26 (nearest section: Bürgerweide; 1.3 km); U 85 (nearest section: Heidenkampsweg; 1.3 km) — signage context, not a route recommendation
Signal installations nearby (16 within 500 m): 11 at junctions, 5 at pedestrian crossings; nearest: Mönckebergstraße/Steintorwall (0.1 km)New in 2.2.12 (the counts) and 2.2.13 (the detours and the signal installations). A detour is named by its number and its nearest street, and always as the signs you will see, never as a route we recommend. A bus registration at a signal is counted only where the city records one, and a zero is never said. Edited: the first line (a note that one roadworks source is 13 days old), two of three entries, the sources that answered and the source line omitted.
Parking around Hamburg, Rathaus (within 10 km), nearest first:
1. Europa-Passage — Car park (Parkhaus), 0.2 km, 690 spaces, no occupancy published
2. Alter Wall / BUCERIUS-Passage — Car park (Parkhaus), 0.3 km, 210 spaces, 95 free (as of 06:00)
3. Große Reichenstraße — Car park (Parkhaus), 0.3 km, 850 spaces, 488 free (as of 06:06)
…
On-street parking bays nearby (the city's register) (168 bays within 300 m): Rathausstraße (for disabled badge holders; 1 bay; 0.1 km); Rathausstraße (electric vehicles charging only Mon–Sat 09:00–20:00; at most 180 min; 1 bay; 0.1 km); Rathausstraße (pay and display; 2 bays; 0.1 km) — the city publishes no occupancy — whether a bay is free is not known; the signs on site applyNew in 2.2.13. The bays come from the Landesbetrieb Verkehr's register of public parking space: a street's bays under one rule set are one line, with the rule, the hours and the maximum stay. Stopping bans and personal disabled bays are never counted or offered. The same answer also lists the city's coach places, with the city's own remark quoted, and the OpenStreetMap car parks in a block of their own. Edited: two car parks, the OpenStreetMap and coach blocks and the source line omitted.
Lorry restrictions within 5 km of Dom, Köln (NRW.Mobidrom (SEVAS)): 387 — No lorries 177, Height limit 121, Cycle street 46, Weight limit 38, No hazardous goods 2, Length limit 2, No vehicles 1. Nearest:
- No lorries — Marzellenstraße, Köln (0 km)
- Cycle street — Trankgasse, Köln (0.1 km)
- Height limit 4 m — Tunisstraße, Köln (0.2 km)
Lorry priority routes: 4 in range, the nearest 0.2 km away.
Lorry restrictions within 5 km of Dom, Köln (Stadt Köln): 26 — Height limit 21, Weight limit 3, No lorries 2. Nearest:
- Height limit 4 m — Tunisstraße, Unterführung Komödienstraße, direction “Norden” (0.2 km)
- Height limit 3.8 m — Nord-Süd-Fahrt, Unterführung Schildergasse, direction “Süden” (0.7 km)
- Height limit 4 m — Nord-Süd-Fahrt, Unterführung Cäcilienstraße, direction “Norden” (0.8 km)
Lorry route network (Stadt Köln, as of 2014-01-01), nearest section: secondary lorry connection for deliveries 0.2 km (Tunisstr., Ursulastr., Victoriastr.); primary lorry connection 1.3 km (Holzmarkt, Zu-/Abfahrt Severinsbrücke, Severinsbrücke); …
These lorry entries come from our database derived from “SEVAS (NRW.Mobidrom)” (ODbL 1.0; its geometry comes from OpenStreetMap). We send a complete machine-readable copy (CSV) under the ODbL 1.0 free of charge on request – contact details in the Impressum on viafrei.de.New in 2.2.9 and 2.2.10. Each publisher gets its own nearest lines, so the city's per-direction heights are no longer crowded out by SEVAS's. A SEVAS restriction drawn on several road segments is counted and named once. Edited: the end of the network line, the closing line and the source line omitted.
Lorry restrictions within 5 km of Dresden Altmarkt (Landeshauptstadt Dresden): 1 — No lorries 1. Nearest:
- No lorries over 3.5 t (sign 253) (0 km); additional sign „Dienstleister, Anlieferer und Wohnmobile frei“
Lorry route network (Landeshauptstadt Dresden), nearest section: lorry priority route 1.6 km. This is the network the city routes lorry traffic over; later rules, such as through-traffic bans, are not shown in it — not an all-clear: the signs on site apply.
Current closures and roadworks: the same question without vehicle.
As of 03:41 · Source: Lkw-Verbotszonen: Landeshauptstadt Dresden (Quelle: Geodaten Sachsen), Datenlizenz Deutschland – Namensnennung – Version 2.0 (…), bearbeitet (…) · Lkw-Vorrangroutennetz: Landeshauptstadt Dresden (Quelle: Geodaten Sachsen), … · …
Lorry bans are shown here as information, not legal advice: only the signs on site say whom and when a ban binds.New in 2.2.10. The city's ban zone is one ban, stated as the city's record states
it; the additional sign is quoted in German, as it is signed. The last line is the
condition note that travels with every such answer as _meta.conditionNote.
Edited: the source URIs shortened to (…).
Lorry restrictions around Hamburg Hbf: no data. We hold them only where a publisher publishes them (so far NRW.Mobidrom for North Rhine-Westphalia, ivm for the Frankfurt RheinMain region, VMZ Bremen for Bremen and Stadt Köln and Landeshauptstadt Dresden, each for its own city area) — this is not an all-clear.
Oversize and heavy transport network (Landesbetrieb Verkehr Hamburg), nearest section 0.4 km (Kreuzweg, Steindamm, Deichtorplatz) — an aid for the application in VEMAGS, no permit.
Current closures and roadworks: the same question without vehicle.
…
The oversize and heavy transport network helps with an application in VEMAGS and is no permit: an oversize or heavy transport needs its own permit or authorisation (§ 29(3), § 46(1) StVO), and the signs on site apply. The network is the LBV's compilation of the routes most often needed; it names no permitted dimensions, weights or axle loads, and the route a transport may take is the one its permit sets.New in 2.2.10. "No data" for the restrictions is said as what it is, and the network is never presented as a permission. Edited: the source line omitted.
2 of 14 reported facilities at Frankfurt (Main) Konstablerwache are out of service. Counted are the facilities DB reports for this station. The platform details are from DB's station data, as of 2026-10-19. …
…
Platforms at Frankfurt (Main) Konstablerwache per DB's station data: 2 of 2 step-free. The station as a whole: step-free, wheelchair accessible.
Platform 2 (Bahnsteig Gleis 2): step-free · wheelchair accessible · platform height 96 cm · tactile guidance · level boarding into the train: unknown
Platform 3 (Bahnsteig Gleis 3): step-free · wheelchair accessible · platform height 96 cm · tactile guidance · level boarding into the train: unknown
Traffic signals within 300 m: 6, 3 of them with an acoustic signal for blind pedestrians: Konstabler Wache/Kurt-Schumacher-Straße (60 m); Berliner Straße/Battonstraße/Kurt-Schumacher-Straße (240 m); Battonstr./Klingerstr./Stoltzestr. (270 m)New in 2.2.9 (the platforms, from DB InfraGO's station inventory) and 2.2.10 (the acoustic signals, from Stadt Frankfurt am Main). "Unknown" is said as unknown, never as no. A tram or U-Bahn stop named with its city, such as "Stuttgart Charlottenplatz", is answered as that stop, with the sentence that we hold no lift status and no survey for it where that is so. Edited: the rest of the first line, the fourteen escalator lines and the source line omitted.
Low-emission zone and plaque — Essen Hbf:
Essen Hbf lies inside the Umweltzone Essen (Umweltzone).
Required: the green plaque (emission group 4). You can buy it at vehicle registration offices, TÜV/DEKRA/GTÜ/KÜS and approved garages on presentation of the vehicle registration document (part I). (Umweltbundesamt, Umweltzonen in Deutschland; not confirmed: exactly which cities belong to the Ruhr zone today — check the source)
Zone boundary last read on 2026-10-19.
…New in 2.2.10, for Essen and Bochum. The point is checked against the city's own polygon, credited "Umweltzone: Datenquelle: Stadt Essen – opendata.essen.de, Datenlizenz Deutschland – Namensnennung – Version 2.0, bearbeitet", with the Umweltbundesamt's agreeing zone credited beside it. Edited: the general rules that follow and the source line omitted.
A59, road-wide: 0 jams, 12 closures, 22 roadworks sites; announced from 10:00: 3 closures, 17 roadworks sites — As of 06:09. Traffic state at 53 measuring sites (NRW, as of 06:08): 4 slow, 5 heavy, 44 free-flowing; standstill or slow near Düsseldorf-Garath, Monheim, Richrath.
• Closure (Sperrung): A59, since 2026-10-05 00:00, until 2026-10-23 12:00 (whole measure until 2031-12-23) — Provider text (German): "A59 6-streifiger Ausbau AK DU - AS DU-Marxloh · AK Duisburg (aus Richtung Duisburg-Häfen) — Zeitraum dieser Bauphase: […] Ende: 23.10.26 um 12:00 Uhr …"
…
structuredContent.events[0].gist:
Closure on the A59; since 2026-10-05, until 2026-10-23 12:00, whole measure until 2031-12-23.New in 2.2.8 and 2.2.9. The gist is built only from fields we already parse (kind, road, junctions, direction, length, limits, dates, distance), so it never translates the publisher's words. For a works in phases it ends with the current phase and names the whole measure's end as such. A German answer carries no gist. Edited: two entries and the source line omitted; the gist is quoted from the structured result.
find_parking {place: "Xyzzyqwertstadt"}
→ isError: true · _meta.errorCode: "not_found"
I do not know "Xyzzyqwertstadt". Name a town, a district or a stop — or pass lat/lon.
check_autobahn_traffic {road: "A59"} (the argument is "roads", a list)
→ isError: true · _meta.errorCode: "invalid_input"
MCP error -32602: Input validation error: Invalid arguments for tool check_autobahn_traffic: Invalid input: expected array, received undefined at roadsNew in 2.2.13. Every error result carries one code from a closed list of seven
(invalid_input, not_found, out_of_coverage, unavailable, limit_reached,
timeout, internal), so a client can tell "ask differently" from "try later"
without reading the sentence.
Edited: shown as the two results' fields, not as the raw JSON-RPC frames.
The A7 is listed in the long-lorry positive network:
- BASt extract, amending ordinance no. 13, network as of uebw. 2025q2: 180 sections, 965.8 km
- Hamburg's field-trial network, as of 2015: 29 sections, 39.5 km
What binds is the Annex to § 2(1) of the LKWÜberlStVAusnV, not this extract.
Current closures and roadworks: the same question without vehicle.
As of 06:43 · Source: Lang-Lkw-Netz: Bundesanstalt für Straßen- und Verkehrswesen (BASt), Positivnetz Lang-LKW (Auszug Bundesfernstraßen), CC BY 4.0 (…), bearbeitet (…) · Lang-Lkw-Netz Hamburg (Feldversuch 2015): Freie und Hansestadt Hamburg, Behörde für Verkehr und Mobilitätswende, (BVM), Datenlizenz Deutschland – Namensnennung – Version 2.0 (www.govdata.de/dl-de/by-2-0), Daten verändert (…)
The data make no claim to be complete or correct. They have no legal or official meaning either. The data are not suitable for navigation or similar purposes (our translation of the publisher's notice).New in 2.2.6. The "As of" time is when the files were last read: the network is
published as a release, not live. The last line is BASt's own notice. It travels
with every such answer as _meta.conditionNote, and your assistant should show it.
Edited: the source URIs shortened to (…).
Lorry restrictions within 5 km of Bremen (VMZ Bremen): 31 — Height limit 19, Weight limit 12. Nearest:
- Height limit “Tiefer 4,0m” (0.3 km)
- Weight limit “aktuell nicht für die Nutzung schwerer Lkw empfohlen” (no value stated, the signs on site apply) (0.3 km)
- Weight limit “Wilhelm-Kaisen-Brücke: >16t” (0.4 km)
- Weight limit “Bgm.-Smidt-Brücke-Brücke: >30t” (0.7 km)
- Height limit “Gustav-Deetjen-Tunnel: 3,1m” (0.9 km)
- Height limit “Parkallee (Remberti-Tunnel): 3,5m” (0.9 km)
…
VMZ Bremen's heights and weights are shown as published (read on 2026-10-19). Only the signs on site are binding; the data is not for route guidance. A missing entry does not mean there is no restriction.Every height and weight is quoted in the publisher's own words and never turned into a number of ours. Where the words give no figure, the answer says that no value is stated. Edited: the source line omitted.
Lkw-Beschränkungen im Umkreis von 5 km um Bielefeld (NRW.Mobidrom (SEVAS)): keine verzeichnet. Das ist keine Freigabe: es gilt die Beschilderung vor Ort.
Lkw-Vorrangrouten: 1 im Umkreis, die nächste in 0,1 km.
Diese Lkw-Einträge stammen aus unserer aus „SEVAS (NRW.Mobidrom)“ abgeleiteten Datenbank (ODbL 1.0; die Geometrie stammt aus OpenStreetMap). Eine vollständige, maschinenlesbare Kopie (CSV) unter der ODbL 1.0 senden wir auf Anfrage kostenlos – Kontakt im Impressum auf viafrei.de.
Aktuelle Sperrungen und Baustellen: dieselbe Frage ohne vehicle.
Stand 06:45 · Quelle: Lkw-Navigationsdaten NRW: NRW.Mobidrom GmbH (SEVAS), Datenlizenz Deutschland – Zero – Version 2.0; Geometrie: © OpenStreetMap-Mitwirkende, Open Database License 1.0 (opendatacommons.org/licenses/odbl/1-0/) (…) · Ortsdaten: © GeoNames (CC BY 4.0), bearbeitet (…)"None listed" is said as what it is: no restriction is recorded, which does not clear the road. The third line is the ODbL offer for the SEVAS rows (see SOURCES.md). Edited: the source URIs shortened to (…).
Low-emission zone and plaque — München Marienplatz:
München Marienplatz lies inside the Umweltzone München (Umweltzone).
Required: the green plaque (emission group 4). You can buy it at vehicle registration offices, TÜV/DEKRA/GTÜ/KÜS and approved garages on presentation of the vehicle registration document (part I). (Umweltbundesamt, Umweltzonen in Deutschland; not confirmed: whether an additional diesel ban applies and to which Euro classes — check the source)
Zone boundary last read on 2026-10-19.
…The point is checked against the city's own zone polygon. München's line, "Datenquelle: dl-de/by-2-0: Landeshauptstadt München – opendata.muenchen.de (bearbeitet)", is credited beside our rules text. Edited: the general rules that follow and the source line omitted.
Note: the source "Arbeitsstellen auf deutschen Autobahnen (BASt)" has not republished since 2026-10-06 (12 days) — information from it may be out of date.
Bonn: 5 jam reports, 46 closures, 844 restrictions, 0 planned roadworks sites, 14 current roadworks sites per BASt — window: right now.
I do not hold federal and Land roads (Bundes-, Landes-/Staatsstraßen) for North Rhine-Westphalia: for those, this answer is no all-clear.
Measured traffic state (City of Bonn, Amt 66 (traffic state), as of 07:25) within 10 km: 111 segments: risk of congestion: 2, increased traffic load: 10, normal traffic volume: 68, not measured: 31 — nearest segment (risk of congestion) 1.3 km away.
• Traffic jam (Stau): Provider text (German): "A555 Bonn Richtung Köln, zwischen Rodenkirchen und Kreuz Köln-Süd, 1 km Stau" (since 06:26; 18.5 km away)
…The fourth line is the city's own measurement, new in 2.2.6, in the city's own class names. "Not measured" is never counted as free. The first line comes from 2.2.4: a source that has stopped republishing is named in the answer instead of being passed off as current. Edited: the remaining entries and the source line omitted.
Disabled-badge bays on the street around Dortmund (within 10 km), nearest first:
1. Hansastraße 9, 44137 Dortmund — 0.2 km, free (sensor, 06:45)
2. Hansastraße 20-22, 44137 Dortmund — 0.2 km, free (sensor, 06:54)
3. Gerberstraße 5, 44135 Dortmund — 0.2 km, no current sensor reading (last 2026-10-18 19:12)
…
Within the radius: 175 disabled-badge bays with a sensor, 62 reported free and 19 occupied; the rest have no current reading.
For holders of a disabled parking permit only. "No current sensor reading" means unknown, not free.
As of 06:54 · Source: Parksensoren Dortmund: Stadt Dortmund (Dortmunder Systemhaus – Smart City), Open Data Dortmund, Datenlizenz Deutschland – Zero – Version 2.0 (…) · …New in 2.2.4. A sensor's state counts for three hours after the city's newest message. After that it is unknown, and unknown is never free. Edited: two of five lines and most of the source line omitted.
2 of 2 reported facilities at Tübingen Hbf are out of service. Counted are the facilities DB reports for this station. Lifts at stops of the city's transport operator (tram, light rail, underground) are not included — I hold no live data on them for this station.
Lift zu Gleis 1/13: out of service — under construction
Lift zu Gleis 2/3/12: out of service — under construction
Step-free access, from the Baden-Württemberg survey (BFRK, Tübingen Hbf): 7 platforms, 1 with a tactile guidance strip; 3 lifts, narrowest door 99 cm, cabins at least 94 cm wide and 220 cm deep; 5 ramps, steepest 6.1 %; 11 staircases. Unchecked raw survey data, file dated 2026-09-18. It says nothing about whether a lift is working now.
…DB's live lift states come first. The survey block is new in 2.2.5, and it says what is built, not what works. Edited: the source line omitted.
Alsdorf (05334004): no jams reported, 1 closure, 12 restrictions, 0 planned roadworks sites — window until 2026-10-20.
I do not hold federal and Land roads (Bundes-, Landes-/Staatsstraßen) for North Rhine-Westphalia: for those, this answer is no all-clear.
• Roadworks (Baustelle) A4: Provider text (German): "Instandsetzung Grenze NL_D - AK Aachen · AK Aachen (aus Richtung Aachener Land) nach A4 — Zeitraum dieser Bauphase: Beginn: 25.08.26 um 09:00 Uhr, Ende: 01.12.26 um 15:00 Uhr, (Ende der Gesamtmaßnahme: 01.12.2…" (2026-08-25)
• Roadworks (Baustelle) A544: Provider text (German): "A544 | Aachen - Würselen · Autobahnkreuz Aachen -> Aachen (Europaplatz) — Zeitraum dieser Bauphase: Beginn: 17.10.26 um 05:00 Uhr, Ende: 16.10.27 um 05:00 Uhr, (Ende der Gesamtmaßnahme: 16.10.2…" (2026-10-17)
…The second line is new in 2.1.23: where no source covers a road class in that Land, the answer says so instead of letting "no jams" read as an all-clear. The same line is on the place's road card on viafrei.de. Edited: the remaining entries and the source line omitted.
Charging around Würselen (05334036) (within 10 km), nearest first:
1. Würselen - Lehnstraße, Lehnstraße 27, 52146 Würselen (Ladenetz) — 0.1 km, Type 2, up to 22.1 kW, 0.50 €/kWh net, status from 2026-10-15 17:37 — possibly out of date (2 charging units)
2. Würselen Rathaus, Rathausstraße 2, 52146 Würselen (Ladenetz) — 0.2 km, Type 2, up to 22.1 kW, 0.41 €/kWh net, status from 13:19 — possibly out of date (2 charging units)
…
Only a few operators publish live occupancy; "no status data" means unknown, not free.
As of 18:38 · Source: Ladepunkte: e-clearing.net (smartlab Innovationsgesellschaft mbH) via Mobilithek, CC0 1.0 (…) · Ladepunkt-Verfügbarkeit: e-clearing.net (smartlab Innovationsgesellschaft mbH) via Mobilithek, CC0 1.0 (…) · …One line per place, each saying how many charging units it holds; since 2.1.23 a publisher's many records of one car park are one place. A status too old to vouch for is said with its time, never as free. Edited: three of five lines, the site ids and most of the source line omitted.
A7: 27 closures, 188 restrictions, 1 planned roadworks site, 44 current roadworks sites per BASt — window until 2026-10-21.
• Closure (Sperrung): Provider text (German): "A7 | Langenau - Lonetal · Ulm -> Würzburg — Die Baustelle ist zu folgenden Zeiträumen gültig: 20.10.26 21:00 bis zum 21.10.26 05:30 Uhr., (Ende der Gesamtmaßnahme:…"
• Closure (Sperrung): Provider text (German): "A7 | Aalen/Westhausen - Aalen/Oberkochen · Würzburg -> Ulm — Die Baustelle ist zu folgenden Zeiträumen gültig: 14.10.26 22:00 bis zum 15.10.26 05:30 Uhr., 15.10.26 22:00 bis zum 16…" — signed detour (U 12) for AS Aalen/Westhausen – AS Aalen/Oberkochen, route as published by the Verkehrsministerium BW (German): "AS Aalen/Westhausen - B 29 - B 19 - L 1084 - AS Aalen/Oberkochen" — signage context, not a route recommendation
• Closure (Sperrung): Provider text (German): "A7 Hamburg-Marmstorf (AS) Sperrung wg. erforderlicher Gehölzarbeiten · Hamburg -> Hannover — Die Baustelle ist zu folgenden Zeiträumen gültig: 19.10.26 von 09:00 bis 15:00 Uhr, (Ende der Gesamtmaßnahme: 21.10.26)"
…
Sources that answered: Autobahn GmbH, BASt (roadworks), BAB traffic messages, Landesmeldestelle Schleswig-Holstein (police traffic messages), Verkehrsministerium BW (signed detours).
As of 22:38 · Source: Verkehrsdaten: Autobahn GmbH des Bundes (…) · Arbeitsstellen: Bundesanstalt für Straßen- und Verkehrswesen (BASt) via Mobilithek, CC BY 4.0, bearbeitet (…) · …Each closure in its publisher's words with its night-time windows, and the signed detour where Baden-Württemberg publishes one. The planned full closures on the A7 page are the same question asked by the page itself, so the two cannot disagree. Edited: seven of ten entries, the count of further entries, two notes and most of the source line omitted.
Regeln in Deutschland — Sonntags- und Feiertagsfahrverbot für Lkw:
• Nächster Fahrverbotstag: Sonntag, 18. Oktober, 0–22 Uhr, bundesweit. (Kalender nach § 30 Abs. 3 und 4 StVO, Feiertage geprüft am 2026-10-08)
• Sonntags und an Feiertagen dürfen Lkw über 7,5 t sowie Lkw mit Anhänger von 0 bis 22 Uhr nicht fahren. (§ 30 Abs. 3 StVO)
• Für Pkw, Wohnmobile und Transporter unter 7,5 t gilt das Verbot nicht — der Sonntag ist für sie ein normaler Fahrtag. (§ 30 Abs. 3 StVO)
…
• Ein Feiertag nur einzelner Länder ist nur dort ein Fahrverbotstag: Am 31. Oktober gilt das Lkw-Verbot von 0 bis 22 Uhr in den neun genannten Ländern; in Baden-Württemberg, Bayern, Berlin, Hessen, Nordrhein-Westfalen, Rheinland-Pfalz und im Saarland ist der Tag kein Feiertag nach § 30 Abs. 4 — außer er fällt auf einen Sonntag. (§ 30 Abs. 3 und 4 StVO)
…
Stand 19.09.2026 · Quelle: Verkehrsregeln: ViaFrei, eigene Zusammenstellung aus amtlichen Quellen (StVO, StVZO, 35. BImSchV, StVG, EmoG, AFIR); jede Aussage mit Quelle und Prüfdatum — informativ, keine Rechtsberatung / … (…)The answer now opens with the next ban day, dated, before the rule itself, and a holiday kept only in some Länder names them. The motorway pages print the same calendar for the Länder each motorway crosses. Edited: the list of holidays and four further rules omitted, and the English half of the source line cut.
Charging around Kassel (within 10 km, ≥ 150 kW), nearest first:
2. Kassel, Germany - Zentrum, Neue Fahrt 9, 34117 Kassel (Tesla, Inc.) — 0.2 km, CCS2, up to 250 kW, 0.48 €/kWh net, status from 10:01 — possibly out of date, 10 without status
4. Circle K I Kassel Leipziger Strasse 22, 34125 Kassel (Spirii) — 1.2 km, CCS2, up to 400 kW, 0.83 €/kWh, status from 09:30 — possibly out of date
…
Only a few operators publish live occupancy; "no status data" means unknown, not free.
Price per kWh: published for 3 of 5 only; for the others we hold no price.
As of 22:43 · Source: Ladesäulenregister: Bundesnetzagentur.de, CC BY 4.0, bearbeitet (…) · Ladepunkte: Tesla Germany GmbH via Mobilithek, CC0 1.0 (…) · …A status is judged by its feed's own window: one read this morning is shown with its time as possibly out of date, never as free now. The charging card and the motorway pages use the same rule. Edited: a place key, three of five sites, the watch ids, the register note and most of the source line omitted.
"SAP" in Walldorf:
1. SAP SE — company, Hasso-Plattner-Ring 7, 69190 Walldorf, Baden-Württemberg, 49.29442, 8.63995
2. SAP WDF01 — commercial building, Dietmar-Hopp-Allee 16, 69190 Walldorf, Baden-Württemberg, 49.29368, 8.64166
3. SAP WDF02 — office building, Dietmar-Hopp-Allee 14, 69190 Walldorf, Baden-Württemberg, 49.29461, 8.64274
4. SAP WDF03 — office building, Robert-Bosch-Straße 34, 69190 Walldorf, Baden-Württemberg, 49.29296, 8.64373
5. SAP WDF04 — office building, Dietmar-Hopp-Allee 15a, 69190 Walldorf, Baden-Württemberg, 49.29421, 8.64443
…
23 matches, 1–10 shown — the next with cursor="10".
OpenStreetMap data as of 2026-10-06
As of 22:44 · Source: OSM-Standortdaten: © OpenStreetMap-Mitwirkende, ODbL 1.0 (…)A company's buildings, each with its address and point, from OpenStreetMap,
which is also why the answer carries the ODbL line.
The answer says how many matched and how to fetch the next page.
Edited: five of ten entries and the source URIs cut to ….
"Hasso-Plattner-Ring 7, Walldorf" — 2 mapped objects at this address:
1. Hasso-Plattner-Ring 7, 69190 Walldorf, Baden-Württemberg — 49.29448, 8.63670
(2 OpenStreetMap objects of this address, up to 145 m apart, shown as one point: outline, usually the building (OSM way; point = its centre))
2. Hasso-Plattner-Ring 7, 69190 Walldorf, Baden-Württemberg — 49.29438, 8.63978 — outline, usually the building (OSM way; point = its centre) — 224 m from point 1
The 2 points lie up to 224 m apart — further than 150 m, so not one door mapped twice; probably several buildings under this house number.
Mapped at this address in OpenStreetMap:
- SAP WDF21 — office building
- SAP WDF19 — office building
- SAP SE — company
As of 22:44 · Source: OSM-Standortdaten: © OpenStreetMap-Mitwirkende, ODbL 1.0 (…)The address, the buildings mapped under it (and how far apart they are, so "two buildings" is not mistaken for "one door mapped twice"), and the companies and buildings OpenStreetMap places there. Edited: the note on another Walldorf, the data date and the source URIs cut.
Berlin (11000000): 1 jam report, 247 closures, 267 restrictions, 10 planned roadworks sites — window until 2026-10-16.
• Slow traffic (Stockender Verkehr): Provider text (German): "A100 Stadtring Berlin, Wilmersdorf Richtung Neukölln, zwischen Gradestraße und Tunnel Ortsteil Britz, 0,8 km stockender Verkehr" (since 12:35; 6.6 km away)
• Roadworks (Baustelle): Provider text (German): "Karl-Liebknecht-Straße (Mitte) — Richtung Brandenburger Tor in Höhe Spandauer Straße Baustellenfläche für eine Hochbaustelle, Fahrbahn auf einen verschwenkten…" (2026-03-26–2027-09-30)
• Roadworks (Baustelle): Provider text (German): "Gertraudenstraße (Mitte) — in beiden Richtungen zwischen Spittelmarkt und Fischerinsel Brückenprüfung, Fahrbahn auf zwei Fahrstreifen verengt, Gewichtsbeschrän…" (2023-04-27–2028-03-31)
• Closure (Sperrung): Provider text (German): "Rosenthaler Straße (Mitte) — in beiden Richtungen zwischen Hackescher Markt und Sophienstraße Gleisbauarbeiten, Vollsperrung für Kfz-Verkehr" (2026-09-18–2026-10-20)
…
Sources that answered: Autobahn GmbH, BASt (roadworks), VIZ.NRW / NMS, Senatsverwaltung Berlin (traffic messages).
As of 22:34 · Source: Verkehrsdaten: Autobahn GmbH des Bundes (…) · … · Verkehrsmeldungen Berlin: Senatsverwaltung für Mobilität, Verkehr, Klimaschutz und Umwelt Berlin via Mobilithek, Datenlizenz Deutschland – Namensnennung – Version 2.0 (www.govdata.de/dl-de/by-2-0), Daten verändert (…) · …One jam, not dozens: a lane narrowed for a building site is roadworks, however the police message is filed, and the one queue on the A100 is the jam. Edited: six of ten entries, the radius notes, the other sources of the source line and its URIs omitted.
Hydrogen stations for trucks/buses near Hamburg (within 50 km), nearest first:
1. Hamburg - Schnackenburgallee — 5.5 km · Schnackenburgallee 12, 22525 Hamburg · 350 bar truck/bus, 700 bar car · opening hours: not published (unknown) · record last changed 2026-10-13 (today)
2. Hamburg - Flughafen — 7.9 km · Weg beim Jäger 193, 22335 Hamburg · 700 bar car, 350 bar truck/bus · opening hours: not published (unknown) · record last changed 2026-10-13 (today)
3. Hamburg - Großmoorbogen — 10.0 km · Großmoorbogen 1, 21079 Hamburg · 350 bar truck/bus, 700 bar car · opening hours: not published (unknown) · record last changed 2026-10-13 (today)
No live availability, price or operating status is published — check that the station is working before you drive.
As of 14:50 · Source: Wasserstofftankstellen: H2 Mobility Deutschland GmbH & Co. KG via Mobilithek, CC BY 4.0, bearbeitet (…) · Ortsdaten: © GeoNames (CC BY 4.0), bearbeitet (…)Only the stations with a 350 bar pump for lorries and buses, because the question
was about a lorry. It names what the publisher does not say, opening hours
included, and never guesses that a station is working.
Edited: the two source URIs cut to ….
Bremen: 4 jam reports, 151 closures, 119 restrictions, 8 planned roadworks sites — window until 2026-10-16.
• Slow traffic (Stockender Verkehr): Provider text (German): "A1 Osnabrück Richtung Bremen, zwischen Dreieck Stuhr und Bremen-Arsten, 4 km stockender Verkehr im Baustellenbereich" (since 12:46; +16 min per Autobahn GmbH; 6.2 km away)
• Traffic restriction (Verkehrseinschränkung) (Bremen): Provider text (German): "Einengung der Fahrbahn; Einengung des Geh-/Radweges; Halteverbot;" (2026-06-01–2026-10-31)
• Closure (Sperrung) (Bremen): Provider text (German): "Vollsperrung; Einengung des Geh-/Radweges; Halteverbot;" (2026-08-17–2026-10-16)
…
Sources that answered: Autobahn GmbH, BASt (roadworks), VIZ.NRW / NMS, Bremen traffic management centre (roadworks).
As of 16:14, unchanged since 13:15 · Source: Verkehrsdaten: Autobahn GmbH des Bundes (…) · … · Baustellen Bremen: Verkehrsmanagementzentrale Bremen via Mobilithek, Datenlizenz Deutschland – Namensnennung – Version 2.0 (www.govdata.de/dl-de/by-2-0), Daten verändert (…) · …The motorway jam and the city's own building sites in one answer, each in its publisher's words and with its dates, and a line naming every source that answered. Edited: asked in English; a place key, seven of ten entries, the radius notes and three of five sources omitted.
Parking around Kassel (within 10 km), nearest first:
1. Galeria — Car park (Parkhaus), 0.2 km, 210 spaces, 102 free (as of 16:06)
2. Friedrichsplatz — Car park (Parkhaus), 0.2 km, 980 spaces, 579 free (as of 16:06)
3. Kurfürsten Galerie — Car park (Parkhaus), 0.3 km, 560 spaces, 456 free (as of 16:06)
…
As of 16:06 · Source: Parkhäuser Kassel: Stadt Kassel, Straßenverkehrs- und Tiefbauamt via Mobilithek, Datenlizenz Deutschland – Namensnennung – Version 2.0 (www.govdata.de/dl-de/by-2-0), Daten verändert (…) · Parkhaus-Belegung Kassel: Stadt Kassel, Straßenverkehrs- und Tiefbauamt via Mobilithek, … (…) · …
Where no "free" count is shown the operator publishes no occupancy — it does not mean the site is full.The city's live counts, each with the time of its reading. Edited: asked in English; a place key, two car parks, the separate OpenStreetMap list and two of four sources omitted.
Abfahrten ab Köln Neumarkt — Fahrplan mit Echtzeit, 06:41 bis 07:01:
06:42 Tram 3 → Köln Dellbrück Thielenbruch, Gleis 14, pünktlich
06:43 Tram 7 → Benzelrath Frechen-Benzelrath, Gleis 12, Plan
06:44 Tram 16 → Bonn Bad Godesberg Stadthalle, Gleis 14, +1 Min. (voraussichtlich 06:45)
06:45 Bus 146 → Köln Lindenthal Deckstein, Steig 25, pünktlich
06:47 Tram 18 → Köln Buchheim Herler Str., Gleis 16, +1 Min. (voraussichtlich 06:48)
… und 23 weitere im Fenster.
Stand 06:41 · Quelle: Fahrplandaten: DELFI e.V., CC BY 4.0, bearbeitet (…) · … · Echtzeitdaten: DELFI e.V. via Mobilithek, CC BY-SA, bearbeitet (…)
Die Echtzeitangaben aus DELFI GTFS-RT und DELFI SIRI ET stehen unter CC BY-SA (Share-alike), …
Verspätungen und Ausfälle aus den DELFI-Echtzeitdaten, wo sie vorliegen; mit „Plan“ markierte Zeiten sind Fahrplanzeiten ohne Echtzeitangabe. …Trams and buses with their live delay, from the same national realtime feeds as the trains. Where no live figure exists the row says Plan, never "on time". Edited: five of ten rows, the stop id line and two of three sources omitted.
7 of 62 reported facilities at Berlin Hauptbahnhof are out of service. Counted are the facilities DB reports for this station.
Escalator 1.UG - Tram Haltestelle 4: out of service
Lift Gleis 3/4 (C/D) - Gleis 11/12: out of service
Lift Gleis 5/6 (C/D) - Gleis 11/12: out of service
Lift Gleis 1/2 (C/D) - 1.UG - EG: in service
… and 54 more.
As of 06:41 · Source: Aufzüge und Fahrtreppen: Deutsche Bahn AG, DB API Marketplace, CC BY 4.0, bearbeitet (…) · …Each lift and escalator, where it is and whether it works. For anyone with a
wheelchair, a pram or a heavy suitcase, this decides whether a station is usable.
Edited: four escalator rows omitted, and one source cut to ….
A7: 45 roadworks sites per BASt between 2026-10-13 and 2026-10-20: 44 current, 1 planned. 5 of them are in this answer — raise limit to 20 for the rest.
• Construction works (Baustelle): A7 (+15 more sections) — 1 of 2 lanes closed, hard shoulder closed, 80 km/h limit, phase 2026-06-23 until 2026-10-25 — 2023-03-23 until 2028-04-14 — Provider text (German): "A7 zw. Bad Brückenau-Volkers → Bad Brückenau/Wildflecken 1,602 km; Brückenneubau"
• Construction works (Baustelle): A7 (+3 more sections) — 1 of 3 lanes closed, 80 km/h limit — 2023-10-28 until 2026-12-31 — Provider text (German): "A7 zw. Hammelburg → Bad Kissingen/Oberthulba 1,007 km; Brückenneubau"
…
As of 06:17 · Source: Arbeitsstellen: Bundesanstalt für Straßen- und Verkehrswesen (BASt) via Mobilithek, CC BY 4.0, bearbeitet (…)
Planning data from BASt: road sections only, no coordinates and no live delay. For the situation right now, call check_autobahn_traffic.Which junctions each site lies between, what is closed, and until when — and it says plainly that this is planning data, pointing to the live tool for now. Edited: the first and the last two of five sites omitted, and the "unchanged since" note cut from the stand line.
I know no filling station from our price data within 5 km of Weimar, … The nearest station with a diesel price is about 19.3 km away — radius_km 20 reaches it. … find_cheapest_fuel can ask the provider which ones are here — new areas one at a time and only a limited number per hour; its answer carries their prices, within about a minute.
More filling stations mapped by OpenStreetMap — we don't have a price for these stations yet:
1. Jet — 1.2 km
2. Star, Rießnerstraße 37, 99427 Weimar — 1.5 km
4. Shell, Rießnerstraße 14, 99427 Weimar — 1.5 km
…
As of 06:41 · Source: Tankstellenpreise: Tankerkönig.de — MTS-K, CC BY 4.0, bearbeitet (…) · OSM-Standortdaten: © OpenStreetMap-Mitwirkende, ODbL 1.0 (…) · …
Hinweis zu den Kraftstoffpreisdaten (MTS-K): Diese Daten dürfen ausschließlich zum Zweck der Verbraucherinformation verwendet werden; …Where we hold no price, the answer says so, offers the next step, and lists the OpenStreetMap stations nearby — never with an invented price. Where we do hold prices, each priced station is listed with its price per litre and its open state; this page shows none, because of the MTS-K condition. Edited: place keys and a second Weimar removed from the first line, two stations and one source omitted.
Parking around Fröttmaning (within 10 km), nearest first:
1. P+R Fröttmaning — Park and ride (P+R), 0.3 km, 1259 spaces, no live occupancy — forecast for now (weekdays 06–07): usually free (more than 75 % free) – forecast from past experience, as of 12/2024
2. P+R Kieferngarten — Park and ride (P+R), 1.1 km, 235 spaces, no live occupancy — forecast for now (weekdays 06–07): usually free (more than 75 % free) – forecast from past experience, as of 12/2024
Munich's P+R sites are, per the dataset, as a rule only for public-transport passengers („grundsätzlich nur den ÖPNV-Fahrgästen“).
…
As of 06:41 · Source: Datenquelle: dl-de/by-2-0: Landeshauptstadt München – opendata.muenchen.de (bearbeitet) (…) · …
Where no "free" count is shown the operator publishes no occupancy — it does not mean the site is full.No live count exists here, so it says so and gives the city's own forecast for this weekday and hour, labelled as a forecast and dated. Edited: a place key, one P+R site, the separate OpenStreetMap list and four of five sources omitted.
Charging around Leipzig (within 10 km, Type 2), nearest first:
1. Parkhaus Neumarkt, Neumarkt 30, 04109 Leipzig (Parkhaus Neumarkt) — 0.2 km, Type 2, up to 22 kW, no status data, per charging point register
2. Motel One Leipzig Nikolaikirche, Schuhmachergäßchen 5, 04109 Leipzig (Wirelane GmbH) — 0.3 km, Type 2, up to 11 kW, no status data, per charging point register
…
Only a few operators publish live occupancy; "no status data" means unknown, not free.
Price per kWh: not published for any of these sites (in the data we hold).
Charging point register as of 2026-09-01 — chargers as reported by their operators to the Bundesnetzagentur, with no live occupancy and no warranty of accuracy or completeness.
…It says what it does not know: "no status data" is unknown, never free, and where an operator publishes a price per kWh the answer shows it. Edited: a place key and the third site omitted, and the stand and source lines cut.
Description of 52.5163, 13.3777:
- Nearest address: Pariser Platz 1, 10117 Berlin (3 m)
- Settlement: Unter den Linden (0.7 km)
- Municipality: Berlin
- State (Land): Berlin
- Junction: Seestraße (4.2 km)
Address data as of 2026-10-06
As of 06:56 · Source: Ortsdaten: © GeoNames (CC BY 4.0), bearbeitet (…) · … · OSM-Standortdaten: © OpenStreetMap-Mitwirkende, ODbL 1.0 (…)That's the Brandenburg Gate. Edited: one of three sources cut to ….
One official notice for Garmisch-Partenkirchen, highest level 1 of 4:
1. Level 1 of 4 — Wetterwarnung (the DWD's own name; our translation: weather warning) — FROST
Valid: until 2026-10-13 08:00 (since 2026-10-13 00:00)
Official DWD wording, reproduced unaltered (German):
„Amtliche WARNUNG vor FROST“
For the drive: Expect ice and much longer braking distances; winter tyres are mandatory in these conditions (§ 2 (3a) StVO).
DWD road-surface forecast for the nearest road-weather stations (SWSMOS/METRo model forecast, run 05:00 — not a measurement and not an official warning):
- Station Farchant-Tunnel (open road, 5.3 km) — forecast 06:00: dry (Trocken), road surface 4.6 °C; no slippery class forecast until 2026-10-14 06:42.
…
Quelle: Deutscher Wetterdienst (…) · Quelle: Deutscher Wetterdienst. Datenquelle: BMVBS und Straßenbauverwaltungen der Länder (…) · …
The road-weather station data are unverified point measurements and do not reflect conditions on a road section; …The official warning word for word, and beside it the forecast for the road surface itself, with what that forecast is not. Edited: the area line, the CAP fields, part of the DWD text, two stations and one source omitted.
On viafrei.de the same data is on the page: the home shows cards for one place, public transport first, then fuel, parking, roads, the motorways nearby, charging, weather and what is nearby, and German towns and cities have place pages under their full names, where each card row with its own point links to OpenStreetMap's map. Since 2.1.9 the cards answer by the tools' own rules, so a card and an assistant asked about the same place say the same thing:
charging: one charger published by two feeds is one row, a site whose every point is closed is not listed, and each row says "1 of 2 free (as of 22:21)", "occupied", "out of service", "possibly out of date" or "no status data", which is unknown and never free. Since 2.5.2 the card shows one block per site under a summary line: the operator, the power with its class (AC up to 22 kW, DC above, HPC from 150 kW, the
powerClassoffind_charging_station), the plugs and the live status in the tool's own words. Since 2.5.4 it filters by terms of use (open 24/7, card at the charger, free of charge, public), as the tool'sconditionsdo;fuel: since 2.5.2 a small price table per station, the cheapest price marked in its cell and the brand as a text badge, and since 2.5.4 one button per grade sorts it by yours (kept on your device only after you click);
transit: Berlin and Brandenburg take their punctuality from VBB's own live feed, a railway station's realtime calls are matched through the national stop directory, and shared bikes within 1 km are listed with their stations. Since 2.5.2 every stop is listed in full, up to eight, the railway station first, and since 2.5.4 each stop is a small departure board (the countdown over the clock, the line as a badge, the destination, the platform, the state as a word and a symbol) with its facilities folded underneath and chips that show one kind of service;
get_departureswith aplaceanswers with the same stops and rows;roads: the Land traffic feeds and roadworks registers answer a place as they do in
check_road_status, every row says where it is, a city's own street messages are not crowded out by the motorways, Hamburg places name up to two traffic cameras (as links, never an image), and every source behind a row or a count is credited;parking: Trucklounge's lorry parks and the P+R NRW sites appear in blocks of their own, each with its licence's own sentence, and since 2.5.4 Trier's car parks carry their free spaces;
everyday needs (since 2.5.4): groceries, health, money, food, lodging, garage, and since 2.5.5 police and public toilets as two cards, each in its own radius, the same places
find_nearbylists when the need is named;speed cameras (since 2.5.4): the published locations of Düsseldorf, Karlsruhe, Köln and Aachen, since 2.6.14 also of Bottrop, Konstanz and Essen, and OpenStreetMap's fixed cameras where no official list covers the town, for planning, under the § 23 Abs. 1c StVO notice;
the place page adds the low-emission-zone sentence
get_driving_rulesstates for that Gemeinde, and lines suggesting what to ask your assistant to watch.
Since 2.4.2 every card refreshes in place (the ↻ on its heading, and the live cards on their own at the pace of their data) without reloading the page, long cards page through to their end, and a topic filter with All and None chooses which cards the home shows; it works without JavaScript and never hides a warning silently. A visitor outside Germany is shown the nearest German town near the border, or Germany as a whole when too far away.
The first screen says which place it shows, and since 2.5.2 the place bar is part of the page rather than a dialog: a search box, your recent places as chips that change the page in place, and "Use my location" on a row of its own above the search (2.5.3). "All of Germany" is one choice, in the headline; going back restores the place you had chosen. The place search finds districts, postcodes and streets, since 2.4.8 points of interest by name, since 2.4.9 a street with a house number typed without a town, and since 2.5.3 motorways and junctions: "A4", "Autobahn 4" or "Dreieck Heumar" list the motorway and the junctions first, each opening its page, then the places. Every card ends with one short sources line naming the providers in view, keeps the notes that must be seen in view, and puts the full credits behind a fold (2.5.2). A place page carries a traffic light for the place: the motorway pages' rule applied to the place's own cards, with each reason linked to its row and drawn on a map of the place. The map marks parking, charging, stations and the DWD warning ring by kind, each mark a link to its row, and since 2.4.7 it draws OpenStreetMap's streets under the marks. When the topic filter hides a card, its marks leave the map and the light says it took a reason from a hidden card. On 2026-10-29 the page for Kassel read "Traffic light: Yellow", with a DWD level-1 fog warning and roadworks narrowing the road as its reasons, and a 5 km map with 17 marks. The light is one per place: the Autobahn card on a place page no longer shows one of its own.
Each station on the transit card has a line of its own, linking its station page: how many of its lifts and escalators run, each one out of service by name, the platforms the timetable marks step-free, and the car parks and P+R sites within 300 m. The weather card shows the nearest road-weather station's next six hours, and the fuel card names the two nearest hydrogen stations within 25 km.
Why the source line matters. Every answer ends with one, and it is the licence speaking: show it to whoever reads the answer. Copy the line the server sends you, not the ones on this page, which are shortened. See Using the data you get back.
🛣️ Motorway pages
Every motorway in Germany has a page of its own, 122 of them, in 22 languages: the
index is at viafrei.de/en/autobahn (German:
viafrei.de/de/autobahn), and a motorway is its
number in lower case — the A7 is
viafrei.de/en/autobahn/a7, and
viafrei.de/fr/autobahn/a7 in French. The route
words are the same in every language and only the language token changes;
"autobahn" is used everywhere, and the older /en/motorway/… addresses redirect. A
spelling such as A 7, a07 or BAB7 takes you to the same page.
What the A7's page holds, from top to bottom:
What is reported now, in one line, since 2.5.2: the counts of the road's closures, jams and roadworks with their time, the junctions where something is reported named and linked, and a Next row: the roads the page's cards name, and one link that opens the connect page with a question about this page ready for your assistant. Place, exit and interchange pages end their first answer with the same row.
A traffic light for the whole road, by the same rule
check_autobahn_trafficuses, with its reasons listed and linked to their rows ("Jam, 47 min delay · Bad Bramstedt - Kaltenkirchen · Flensburg → Hamburg"), and a short "how the traffic light is set" that names what it reads and what gives no colour (detours, border crossings, lorry networks, parking and charging).Around you, when you share your position (rounded to about 500 m on your device), choose a place or one is guessed from the network: what lies within a radius you choose (1 to 100 km), nearest first, the nearest junction with its number, distance and a map link, "you are here" between two junctions with ahead/behind badges, and the traffic light for that stretch. The radius is kept in the address, never on the device.
Cards you choose: one card per kind — closures, jams, other warnings, roadworks, planned closures, police and Land messages, bridges, detours, border crossings, DWD warnings, the road-surface forecast, parking, charging, cameras and fuel — with checkboxes. The cards, their counts and the map follow without a reload, and the choice can stand in the address (
?show=). The traffic light still judges everything and says when the choice hides some of its reasons. The panels stand in order of usefulness, each with an icon, and the empty ones fold into one line.How fresh each panel is, as a shape and a word, never colour alone: live, delayed, stale (the panel keeps its data and says it may be out of date) or reference data with its date, beside the Berlin time of the source's last good read. A panel whose read failed says so, never "nothing reported".
Search, as you type: junctions, Länder and every panel row by row, with umlauts, case and the usual abbreviations (AS, AK, AD, Kreuz, Dreieck) folded, each hit linking to its row. Without JavaScript the same search is a plain form. The index search also takes a town or a junction: "Kassel" lists the A7, the A44 and the A49 with the matching junctions. Since 2.5.2 the box in every page's header searches the whole site.
The towns along the route: every town within reach of an exit, in road order, at its nearest exit, the large ones first, each linking to its exit and to its place page on viafrei.de, and to its official website where Wikidata states one.
The crossing motorways: each interchange and triangle names the motorways it meets, each linked to that motorway's page centred on the same junction, with the traffic light that page shows there. Since 2.4.3 the page also names the related motorways it does not cross, such as a spur or the road that bridges a gap in it.
One sentence about the road, built from its own data: from Füssen to Flensburg/Harrislee, about 928 km on the schematic line, the Länder it crosses in road order and how many junctions and interchanges it has, followed by what is reported now, with its time. Every figure in it links to its panel. On 2026-10-14 the English page read: "The A7 runs from Füssen junction to Flensburg/Harrislee junction, about 928 km long (schematic), through Bavaria, Baden-Württemberg, Hesse, Lower Saxony, Hamburg and Schleswig-Holstein, with 141 junctions and interchanges (24 of them interchanges). Reported on the A7 now: 21 closures, 0 jams, 118 roadworks (as of 22:37)."
A map, drawn on the server: Germany's outline and the Länder from the BKG's VG2500, the motorway as a schematic line through the junctions of BASt's Location Code List, closures solid, roadworks hatched, jams with their delay. A map zoomed below 25 km also draws the Land and Kreis borders from the BKG's VG250. Where the list has no course for a stretch the line breaks, and the page names the break rather than drawing across it. Since 2.4.7 the map also draws OpenStreetMap's streets as thin lines under its marks (never an OpenStreetMap motorway: the motorway is BASt's line), with the streets' own credit and our offer of the street database beside it; no mark is placed on or measured along a street.
What is reported now: closures, jams and roadworks under their own heading, then the full closures planned for the next seven days, soonest first, each with the signed detour where Baden-Württemberg publishes one. Since 2.4 every entry says where it is (the stretch between two junctions, the nearest town and Land, each a link), in which direction, when (with the weekday and "runs now" or "in 6 days"), what it means for a driver and what the work is in plain words, with a map link. Long cards show twelve entries and fetch the rest when you open the fold; without JavaScript the same fold is a link.
The junction strip: every junction, interchange and triangle in order, with its counts. A form filters the page by stretch (from, to), direction and layer, and works without JavaScript. Each interchange names and links the motorways it meets, and a chosen stretch gives its own length.
Parking and rest: truck stops, lorry parks and service areas with live free spaces where the operator publishes them, and car parks; the share-alike sources (Trucklounge, P+R NRW, and OpenStreetMap's car parks at the junctions) in blocks of their own. Each site shows the amenities its own publisher states ("Facilities per the publisher: toilet · shower · restaurant · fuel station"), and the card can be narrowed to sites with lorry spaces, free spaces now, or a stated amenity; it says how many sites state any ("34 of 50 sites state any facilities — for the rest they are unknown, not ruled out"). A second group of filters uses what OpenStreetMap shows near a site, with its licence line, and never counts it as the site's own. The occupancy of the rest areas from Toll Collect's Stellplatz-Informationsdienst appears only after you press "Show occupancy" and so accept the terms of use, section 2.
Along the road: the police and Land traffic messages for the Länder that publish them, Schleswig-Holstein's bridge states, the signed detours of North Rhine-Westphalia, Baden-Württemberg and Hamburg, Brandenburg's border crossings, and the lorry networks of SEVAS (NRW) and ivm (Frankfurt RheinMain) with their database licence offer, each with a line saying where it is covered. A message carried by several sources is shown once, with all of them.
Charging: the chargers along the road with their status, the sites by power class, and the longest stretch with no charger of 150 kW or more. It says where chargers are, never that one is free unless its operator says so. Since 2.4.3 a filter bar narrows the card by operator, plug, power band and "free now", with counts, the same rule
find_charging_stationuses.Weather: the DWD's official warnings along the road and the road-surface forecast of its road-weather stations.
Traffic cameras, as links to the publisher's images.
Fuel prices, loaded by your browser when the fuel card comes into view: the page's HTML carries none, a crawler never sees one, and the card shows at most ten stations, each price with its time and the MTS-K note.
On every motorway: the lorry ban, dated for the Länder this road crosses (whether it holds now, until when, and the next ban days), the advisory speed, the rescue lane and the emergency numbers, in the same words
get_driving_rulesuses.Ask your assistant: how to connect, the address to copy, and two or three questions this page can answer, each answered from the page's own rows with its time and source.
The index lists every motorway with its live counts, has a search that takes a number in any spelling, a "worst right now" order (closures and jams first, then the longest delay), and an overview map of Germany with the motorways that have a closure or a jam drawn apart. The home page lists the ten worst motorways right now as cards, and every place card set has an Autobahn card: the motorways near the place, nearest junction first, each linked to its page.
Found by search, classic and AI. Each motorway page has its own title and description in each of the 22 languages ("A7 Germany: traffic jams, roadworks, map"), the motorway sitemaps list every page in every language, and llms.txt and llms-full.txt describe the pages, since 2.5.2 every kind of page on the site with an English and a German example; llms-full.txt also lists every motorway page in English and German. robots.txt keeps the AI training and corpus crawlers off the fuel page, names them one by one, and leaves the motorway pages open to every crawler, the place pages since 2.4.0, and the station and exit pages from their first release. No fuel price is in any page's HTML: a reader's browser asks for the prices when the card comes into view, and that address is closed to every crawler.
One card format (2.5.4): a motorway page's fuel, charging, weather-warning and road-weather cards are drawn like the place pages' cards, with the same short sources line and the full credits behind a fold, so the same thing looks the same on a place, a motorway and a station page.
🚉 Station and exit pages
Every railway station has a page, 6,513 of them on 2026-10-29, in the same 22 languages: the stations in DB's station directory and, since 2.4.5, the ones it does not list, found in the timetable. The index is at viafrei.de/en/station, and a station is its name as an address, so Berlin Alexanderplatz is viafrei.de/en/station/berlin-alexanderplatz. A station page shows, from the same data the tools read:
the departure board and the arrivals, with platform, delay and cancellations, and since 2.4.5 filters for mode, departures or arrivals, platform or stand, destination, time, disruptions only and step-free only, which since 2.4.6 apply as you choose them. Only a real track number stands under "platform", a train that splits is one row, and every station a row names links to its page. The live part refreshes in place. Since 2.5.4 the board is drawn as a platform display (white on navy, delays in amber, the track in a white square), with departures and arrivals on two tabs that, without JavaScript, are two tables under their own headings; since 2.5.5 its columns keep one line each on a phone. One departure published twice under two spellings ("RE5" and "RE 5 (RRX)") is one row;
at an interchange, its U-Bahn, Stadtbahn and trams, and every line that calls there;
the lifts and escalators, every one of them, each joined to the platforms it serves, with the ones out of service named;
the service alerts that concern it;
parking and charging at its door, with the same filters as the charging card;
around the station: since 2.4.5 the place cards of the station's own position and the place traffic light with its map, the everyday needs nearby (since 2.5.5 police and public toilets as two cards), the motorways and the other stations near it.
Every block says how fresh it is, with the same sign as the motorway panels. A part that is slow to answer loads in place, and the page is never an error because of it. The home page has a block of the stations most affected right now, with a station search beside it. Each page's title names departures, platforms, lifts and disruptions in its language, and its heading names the station with its town.
Since 2.5.8 the tool describe_station
answers a station as its page shows it, by the page's own rules, and links the page.
The station map marks each lift at its own position, every map says how fresh it is,
and the traffic light and the map refresh in place every two minutes; a map that is
not ready in time is shown as its text instead, so the page never waits for it.
Since 2.5.10 a station's board updates itself once a minute, but only while you can see the tab. Since 2.5.14 U-Bahn and Stadtbahn stations have pages too: a tram stop of the German stop register gets one when OpenStreetMap maps an underground station within 300 m of it, and such a page carries the OpenStreetMap line and the share-alike offer described in SOURCES.md; its content (name, lines, departures, lifts) comes from the stop register, the timetable and the operators. Every station page also names the nearby tram and bus stops, each with its own live departures. "Use my location" at a station, a fuel or charging station or a rest area opens that place's own page; the position goes to the server inside the request, not in the address, and is not written to any log. Since 2.5.17, at 1024 px and wider, station, place and motorway pages are a dashboard: the items in one column and a map beside them that stays in view, each item linked to its mark.
Every Bundesland has a page since 2.5.8, in every language, with an index at
viafrei.de/en/states: Hessen is
viafrei.de/en/state/hessen. It shows the Land's
motorways as they are now (the counts, the longest jams and each motorway with
something in force, the same answer check_autobahn_traffic gives with land), its
facts, among them its area from the Statistisches Bundesamt, and its largest towns.
Every fuel station and every charging site has a page too since 2.5.8, under
/en/fuel/… and /en/charging/…, linked from the fuel and charging cards and from
the answers of find_fuel_station, find_cheapest_fuel and find_charging_station;
the Land pages and each kind of station page are listed in sitemaps of their own.
Since 2.5.19 such a page's address is its description alone
(/de/charging/<operator>-<town>-<street>), with a short key added only when two
pages share a description, and every older address answers with a permanent
redirect to the current one.
Every motorway exit has a page of its own since 2.4.1, under its motorway: the A3's junction Breitscheid is viafrei.de/en/autobahn/a3/exit-16-breitscheid. It is the motorway's page opened at that junction, with its title and a map above the fold: the traffic light, what is reported, the junction's surroundings, parking, charging, the towns along the route and the questions your assistant can answer there. The exits with enough to say are listed in their own sitemaps, about 1,700 per language. Since 2.5.2 an exit page's map frames the junction and its neighbouring junctions, at most 20 km across, instead of the whole motorway.
Every Autobahnkreuz and Autobahndreieck has one page since 2.5.2, named the way people search for it. An interchange used to be an exit page of each motorway it joins, named after the motorway ("A6 Weinsberg"), so a search for "Weinsberger Kreuz" found nothing and the same interchange stood at two unrelated addresses. Now its page is called "Kreuz Weinsberg (Weinsberger Kreuz)" in German and "Weinsberg interchange" in English, links the other motorways it meets, and one address is the canonical one, the one the sitemaps list: the Weinsberger Kreuz is viafrei.de/en/autobahn/a6/exit-38-weinsberg, and the A81's page for the same interchange points search engines there. On 2026-11-02 at about 04:00 it opened with "At Weinsberg interchange on the A6, reported now: 1 roadworks (as of 03:52)", followed by its Next row and the A6's traffic light, yellow for a DWD level-1 weather warning and roadworks narrowing the road.
The site search in every page's header (the fuel price page excepted) and at viafrei.de/en/search finds all of these: motorways in any spelling ("A 7", "BAB 7", "Autobahn 7", "A07"), places, stations, junctions ("Weinsberger Kreuz", and since 2.5.3 "AS Dresden-Neustadt" for an exit), areas, points of interest and the site's own pages, grouped by kind, best group first. Since 2.5.8 it also finds the Bundes- and Landesstraßen: "B 51" opens that road's page, and "L 249", a number several Länder use, offers one result per Land. The search and the MCP tools read the same words for junctions and stations, and the header's suggestions leave out a part that is slow to answer and say so, instead of waiting for it. A place picked from the header's recent places opens that place, and a station chosen from the search is remembered as that station, so its recent entry reopens the station's page.
🔌 Connect in one minute
The product is a hosted MCP server. Point your client at it and the tools appear. There is nothing to install, no key to request and no quota to negotiate. Step-by-step guides for each assistant: viafrei.de/en/connect.
Claude Code
claude mcp add --transport http viafrei https://mcp.viafrei.de/mcpclaude.ai and the Claude desktop app — Customize → Connectors → "+ Add" → Add custom connector, name it ViaFrei and paste this address as the server URL. The connector lives in your Claude account, so the desktop app has it too:
https://mcp.viafrei.de/mcpChatGPT — Plugins → "+" → Add custom MCP server, name it ViaFrei, paste the address under "Connection", authentication none, then Create as a plugin; in a new chat type @ and pick ViaFrei. Custom MCP servers work in ChatGPT on the web, for Pro users and in Business and Enterprise/Edu workspaces, not in the mobile apps and not on Free or Plus.
On a phone (Android, iPhone) — most assistant apps cannot add a connector inside the app. Set it up once in a browser (the phone's browser works too): for Claude, claude.ai → Customize → Connectors → "+ Add" → Add custom connector, the address above, Continue. Then sign in to the Claude app with the same account and switch ViaFrei on under "+" → Connectors in a chat. The connect page has these steps with pictures, and says for the other assistants what their official guides allow on a phone.
Cursor, and any client with an mcpServers file that takes a url, over HTTP:
{ "mcpServers": { "viafrei": { "url": "https://mcp.viafrei.de/mcp" } } }VS Code (.vscode/mcp.json, or MCP: Add Server from the command palette):
{ "servers": { "viafrei": { "type": "http", "url": "https://mcp.viafrei.de/mcp" } } }For GitHub Copilot in VS Code, MCP: Add Server → HTTP → the address → server
ID viafrei → Global → Copilot Global writes the same entry to Copilot's own
configuration.
Gemini CLI, OpenAI Codex, Windsurf and Mistral Le Chat:
gemini mcp add --scope user --transport http viafrei https://mcp.viafrei.de/mcp
codex mcp add viafrei --url https://mcp.viafrei.de/mcpWindsurf takes { "mcpServers": { "viafrei": { "serverUrl": "https://mcp.viafrei.de/mcp" } } }
in its mcp_config.json, and Le Chat a Custom MCP Connector with the address and
no authentication. The connect page has the steps
for each, a link to each client's official guide and how each was checked: on
2026-10-28 claude.ai, Claude Code, Gemini CLI, the MCP Inspector and this bridge were
connected for real, and the others were checked against their official guides.
Clients that speak only stdio — for example Claude Desktop's config file
(claude_desktop_config.json, opened from Settings → Developer → Edit Config).
That is what this package is for:
{ "mcpServers": { "viafrei": { "command": "npx", "args": ["-y", "viafrei"] } } }Node 22 or newer. npx fetches the bridge when your client starts it. If the
file already has an mcpServers block, add the "viafrei" entry inside it
rather than pasting a second block.
An older client on HTTP+SSE is answered too, at https://mcp.viafrei.de/sse.
The transport is deprecated in the specification, so prefer the address above
when you can:
claude mcp add --transport sse viafrei https://mcp.viafrei.de/sseRestart the client and ask one of the questions above.
Where to find ViaFrei
npm —
viafrei. This package: the stdio bridge, for the config line above. Its page shows the current version and this README.Smithery — smithery.ai/servers/viafrei/viafrei. Connect through Smithery's hosted connection, with no local install.
Glama — glama.ai/mcp/servers/mavrovde/viafrei-mcp. The directory listing for this repository, with the tool list.
Glama connector — glama.ai/mcp/connectors/de.viafrei.mcp/via-frei. The hosted endpoint as a Glama connector, ownership verified, with its health check.
mcpservers.org — mcpservers.org/servers/mavrovde/viafrei-mcp. The directory listing for this repository, in several languages.
Official MCP Registry —
de.viafrei/mcp. The hosted endpoint, as MCP clients and directories that read the registry find it;server.jsonis the entry. It is republished with every release of this package, after the npm publish, and only when the live server reports the same version.awesome-mcp-servers — punkpeye/awesome-mcp-servers. The largest curated list of MCP servers; ViaFrei is listed under Travel & Transportation.
awesome-remote-mcp-servers — punkpeye/awesome-remote-mcp-servers. The curated list of remote MCP servers; ViaFrei is listed with its hosted endpoint.
TensorBlock MCP Index — tensorblock.co/mcp/servers/…. TensorBlock's searchable index of MCP servers, with a profile page for this repository.
TensorBlock awesome-mcp-servers — TensorBlock/awesome-mcp-servers. TensorBlock's curated list on GitHub; ViaFrei is listed under Travel & Transportation.
For AI tools — viafrei.de/llms.txt and llms-full.txt: what ViaFrei is, how to connect, every tool in one line each, the example questions with the tool that answers each, and the live pages (the motorway index, an example motorway page, the place pages); llms-full.txt also lists every motorway page in English and German.
🧰 Everything it can do
24 tools, 9 prompts, 10 resources and 2 resource templates — server 2.6.18, snapshot of 2026-11-16. Each line is the server's own words; the full parameters are in API.md.
🚗 On the road
tool | what it answers |
| Per motorway (≤ 5), or one Bundesland's motorways with land: an Ampel, then jams, closures, roadworks in force, with place/delay/speed/map. |
| If a motorway/B/Land road (NI, NW, HE, BW, MV, SN, TH; B also SH, BY, BE; pass Land/town as place) is open/closed/restricted now/soon; by place, jams, city/Land messages, Hamburg traffic cameras; lorry limits, Lang-Lkw (vehicle). |
| Returns roadworks PLANNED on one motorway, one Bundes-/Landesstraße in NI, NW, HE, BW, MV, SN or TH (BY: B only), or city streets by place, in a date window: where, impact, dates, map links. |
| Parking near a place, a coordinate or along one motorway: lorry parks, car parks, P+R and disabled-badge bays, with total spaces, stated amenities (WC, shower) and published free spaces. |
| A town's published speed-enforcement locations (fixed, red-light, section control, announced mobile checks, measuring sites) by kind and street plus OpenStreetMap's fixed cameras. |
🚆 Public transport
tool | what it answers |
| Next trains at a German railway station: platform, delay, cancellations. |
| Scheduled departures from any German stop — bus, tram, U-/S-Bahn, train, ferry — or the nearest stops around a place ("Abfahrten in der Nähe"). |
| Public-transport punctuality now in a German region: share of trips >5 min late, skipped stops, cancellations, trend, alerts in force. |
| Whether the lifts and escalators of a railway station or Köln Stadtbahn stop work now: each with place, state, reason. |
| One German railway station as its viafrei.de page shows it: address, step-free platforms now, lifts and escalators (out of service first), platforms, the next departures with live delays, service alerts, parking and charging. |
⚡ Charging and fuel
tool | what it answers |
| Returns EV charging sites near a place or coordinate: operator, plugs, max power, price per kWh where published, and points free now where live status is published. |
| Returns the cheapest stations for one fuel grade near a place or coordinate: price per litre, brand, address, distance, open state. |
| Finds filling stations around a place or coordinate under any combination of filters — grade, brand, name, open now, open at a time you name, open 24 h — sorted by distance, price or name. |
| Returns hydrogen (H2) filling stations near a place or coordinate, nearest first, with operator, address, pumps (700 bar car, 350 bar truck/bus), opening hours where published and the age of the record. |
📍 Places and addresses
tool | what it answers |
| Looks up a place name and returns every match, each with its kind, population, English name and coordinate; the official key (AGS/RS) only in the structured result. |
| Finds a business or landmark by name or kind — company, shop, clinic, hotel, hostel — with address, category and coordinate. |
| Looks up a street address: its coordinate, and the named OpenStreetMap objects at it (company, shop, office) or that none are. |
| Turns a coordinate into words: the nearest address, settlement and motorway junction with their distances, and the Gemeinde, Kreis and Land the point lies in; also any low-emission zone. |
| Overview of what is around a place or coordinate: fuel, EV charging, parking, nearest railway station and motorway junction, with distances; everyday places (shop, pharmacy, cash, food, hotel, workshop, police) only when named in categories. |
🚲 Sharing
tool | what it answers |
| Returns rentable shared bikes near a place or coordinate: bike-sharing stations with bikes and free docks now, and free-floating bikes around, with distance and data age (nextbike incl. KVB Rad, MyRadl, VAG_Rad; Donkey Republic). |
🌦️ Weather and rules
tool | what it answers |
| Returns the official DWD weather warnings in force for a place — storm, snow, ice, heavy rain, thunderstorm, heat — with Warnstufe 1–4, area, validity and the official text unaltered. |
| Returns the German road rules a visitor needs: low-emission zones (Umweltzone) and the Feinstaubplakette, speed limits (advisory 130), winter tyres, alcohol, the Sunday lorry ban, tolls, Rettungsgasse, what must be in the car, electric cars. |
🔔 Watches
tool | what it answers |
| Opens a watch so THIS conversation is told when something changes: a road closed or restricted, a motorway jam, a stop running late, a weather warning, a charger freeing up. |
| Ends a watch this conversation opened with watch_situation, so no further notifications arrive for it. |
🧭 Prompts — ready-made briefings
Pick one in your client's prompt menu and fill in the blanks; it calls the right tools in the right order.
prompt | what it does |
| Briefs a drive that is about to start: the official weather warnings at both ends, whether each motorway is open, and the jams in force this minute, ending in one go/no-go sentence. |
| Weighs one trip by car against the same trip by rail: closures and live jams on the motorway side, the next departures and the region's punctuality on the rail side, as two paragraphs the traveller can compare. |
| Collects what a driver must carry and know before driving in Germany and into one particular city: the low-emission-zone badge, speed limits, winter tyres, the alcohol limit, tolls, mandatory equipment and the rules for an electric car. |
| Finds where this traveller fills up or charges on the way: the cheapest stations for one fuel grade around one place, or the charging points with the right connector and power, and the rest area beside them if they also need a break. |
| Plans one public-transport leg on the day itself: the next departures from the station with delays, platforms and cancellations, and whether the region's buses and trains are running normally at this hour. |
| Finds where to leave the car at the end of the drive: the car park in town, the park-and-ride at the edge with the onward departures, or the rest area if the traveller is early. |
| Resolves a bare name of unknown kind into a place, a named thing, or an address, trying each table in turn and stopping at the first that answers. |
| Answers "what is around here" for one place: the nearest fuel, EV charging, parking, railway station and motorway junction in one glance, then — only if the traveller wants more than the nearest one — the depth tool for that one category. |
| Turns a bare lat/lon into a sentence a traveller understands: the nearest address, settlement and motorway junction with their distances, and the Gemeinde, Kreis and Land the point lies in. |
📚 Resources — reference your assistant can read
resource | what it holds |
| Licence and attribution text for every data source ViaFrei uses. |
| Which feeds, places and vehicles ViaFrei can answer for right now — licence, cadence and freshness per feed, which large cities hold no fuel price yet, plus what is deliberately not covered. |
| Curated, sourced and dated: low-emission zones, speed, winter tyres, alcohol, tolls, the Sunday lorry ban, equipment, emergencies and electric driving. |
| Which German cities run a low-emission zone, which Feinstaubplakette they require and where to buy it. |
| What to dial, how to form the Rettungsgasse, what to do in a breakdown or after a crash, and what the law requires you to carry. |
| What an electric car needs in Germany: the E-Kennzeichen and why its privileges differ per city, the green plaque, the right to ad-hoc card payment, plug standards, how prices are shown, etiquette and what to do in an emergency. |
| Per feed: is it still arriving? |
| The watches THIS conversation has open, with what each one is watching and when it expires. |
| What the place index holds: rows and last load per source and kind, how many carry an English name, and the sixteen Länder it can name — the coverage behind find_place/find_poi/find_nearby's place answers. |
| What the OSM-derived address index holds per Bundesland — the Länder and each one's extract date read from the rows, the row counts estimated from the planner's statistics and labelled so — plus the ODbL § 4.6 offer owed to anyone who receives an address-derived result. |
| One watch of this conversation: what is being watched, what it has reported, and the attribution of the data behind each report. |
| One place, poi or address resolved the same way every tool resolves |
The running server is the source of truth. This list and API.md
are rendered from a dated snapshot of it, and CI fails if either drifts from that
snapshot. Ask any MCP client for tools/list to see what is live this minute.
Worked use cases
Walkthroughs that chain several tools, each naming what comes back:
🛣️ Driving Munich to Berlin: several motorways in one call, roadworks ahead, a fuel or charging stop, and parking at the far end.
🚉 The commute that broke: departures, regional disruption, and a station lift that is out.
🔋 An EV on a long weekend: charging by connector and power, low-emission-zone rules, and what is around a stop.
🚚 Fleet and logistics briefings: a dispatcher's morning brief, and watches that report a change instead of being polled.
🗺️ Building a local guide agent: a vague place to coordinates and back, and what OpenStreetMap's licence asks of you.
How well it answers, measured: test rounds of up to nearly 3,000 questions in German and English against production, with every finding published.
🛠️ For developers
Not building for an AI assistant? The same live data is coming as a keyed REST API, developed in the open at viafrei-api: in development, with a preview planned; feature-first endpoints, OpenAPI 3.1, attribution on every response. Follow it in its wiki.
It's plain MCP over HTTP. You can call it without an SDK:
# 1. open a session
curl -si https://mcp.viafrei.de/mcp \
-H 'content-type: application/json' -H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"me","version":"0"}}}' \
| grep -i mcp-session-id
# 1b. tell the server you are ready — the MCP lifecycle requires it before any request
curl -s https://mcp.viafrei.de/mcp \
-H 'content-type: application/json' -H 'accept: application/json, text/event-stream' \
-H 'mcp-session-id: <from step 1>' -H 'mcp-protocol-version: 2025-06-18' \
-d '{"jsonrpc":"2.0","method":"notifications/initialized"}'
# 2. ask a question (put the session id from step 1 in the header)
curl -s https://mcp.viafrei.de/mcp \
-H 'content-type: application/json' -H 'accept: application/json, text/event-stream' \
-H 'mcp-session-id: <from step 1>' -H 'mcp-protocol-version: 2025-06-18' \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"check_weather_warnings","arguments":{"place":"Freiburg im Breisgau","language":"en"}}}'One endpoint instead of a stack of integrations. SOURCES.md lists the more than 140 sources behind it, among them Autobahn GmbH, Deutsche Bahn, DWD, DELFI, VBB, the national access point Mobilithek, MobiData BW, the Bundesnetzagentur, dozens of charge-point operators, H2 Mobility, city open-data portals, BKG, GeoNames, OpenStreetMap and MTS-K. Each has its own format, release rhythm and licence, and they arrive here as one protocol.
Results are written to be read aloud. A tool answers in sentences an assistant can pass on, says what it does not know ("no status data means unknown, not free"), and ends with the source line.
Annotated honestly. Twenty-two of the twenty-four tools are read-only and idempotent (
readOnlyHint,idempotentHint), so a client can call them without a confirmation prompt. The two watch tools are not, because opening or stopping a watch changes what the server will tell you later, and their annotations say so.Prompts and resources, not only tools. Nine ready-made briefings, and a reference shelf (driving rules, emission zones, emergency numbers, attribution) your assistant can read directly.
Watches.
watch_situationturns polling into a notification for as long as the session lives: a road closure appearing or clearing, a stop's departures running late, a region's late share reaching a threshold (a quarter by default), a DWD warning coming into force, a charge point turning free. Three hours by default, 24 at most, and at most 10 per session. What a watch has reported is readable atviafrei://watchesandviafrei://watch/{id}, and a client that subscribes to that resource is told when it reports something new. It reaches no inbox and no phone.Machine-readable failures, in the bridge too: one line on stderr and a distinct exit code per cause (see below). On the server, a refusal carries
isErrorand_meta.errorCode(invalid_input,not_found,out_of_coverageand the rest of a closed list), and an input it cannot use is answered with an example call that would work.Discoverable. The server card is served at
https://mcp.viafrei.de/.well-known/mcp/server-card.jsonand, the same document, athttps://viafrei.de/.well-known/mcp.json;https://viafrei.de/.well-known/security.txtnames the contact for security reports. The developers page has a quickstart per client and every tool with an example question.
Bridge configuration
option | what it does |
| endpoint to relay to. Default |
| extra HTTP header on every request, repeatable. For an API key, when there is one |
| per-request timeout, default 30000. The event stream is never timed out |
| print and exit |
Many MCP clients can only pass an env block, not arguments, so every option
has an environment variable too:
variable | same as |
|
|
|
|
|
|
A flag wins over the variable, and the variable wins over the built-in default.
A --header of the same name replaces one from the variable; a --header of a
different name is added alongside it.
There is no self-hosted ViaFrei. The server is a hosted service. --url is
not a way to run your own: it exists for a proxy or gateway in front of the
service, and for the stub server this repository's test suite starts.
When something is wrong
The bridge prints one line to stderr and exits with a code that says what happened. No stack traces:
viafrei: cannot reach https://example.invalid/mcp: host not found (DNS) (ENOTFOUND) - check your network connection; --url only if you relay through a proxyThe same text also goes back to the client as a JSON-RPC error, so an assistant can say what went wrong instead of going quiet.
exit | meaning |
| clean shutdown (the client closed stdin, or sent SIGINT/SIGTERM) |
| something else went wrong; the line says what |
| bad usage: a flag or a value the bridge does not accept |
| the endpoint could not be reached, stopped answering, or never answered in time |
| the endpoint answered and the bridge cannot continue: it refused (the line names the HTTP status), forgot the session, answered with something that is not MCP, or redirected to another origin |
| protocol version mismatch; the line names the version the server speaks |
A slow call may be a retried call. A 429, 502, 503 or 504 is tried
again once, after the delay the server asked for in Retry-After, or 250 ms
when it asked for none. A connection that fails outright (reset, broken pipe,
socket or connect timeout) is tried once more after 250 ms. Two cases are not
retried, because waiting would be worse than answering: a 429 with no usable
Retry-After, and any requested delay longer than your timeout. An event stream
is never retried.
Your timeout bounds each request, not the whole call. Two attempts plus a delay can add up to about three times the timeout, and more if the endpoint redirects. If you need a hard ceiling, enforce it on your side.
An established session may wobble: a dropped event stream is a warning, and the bridge reconnects. It may not stay dead in silence. Several failures in a row with nothing succeeding in between end the process with the code above, so the client that started it finds out.
What the bridge does not do
No tracking. No telemetry, no analytics, no usage counter, no update check.
No stored files or credentials. It writes no file outside the OS temp directory.
--headeris passed through to the endpoint and is never persisted or logged.No cross-origin redirects. A redirect off the origin you pointed it at is refused with one line naming both ends, so a server cannot forward your API key somewhere you did not choose. Same-origin redirects are followed normally.
💼 For businesses
The licence work is done, and it travels with the answer. Each result carries the attribution its sources require. Where a source attaches a condition, the result states it: share-alike is flagged, and the MTS-K purpose limit arrives as a sentence you are meant to show.
Built for answering people. Live figures, sourced and dated, in the language of the question. Good for travel and mobility assistants, dispatchers' briefings, customer service and step-free station checks.
Read the business page: viafrei.de/en/business. It covers six use cases and how to work with us.
A REST API is on the way. For systems that do not speak MCP, viafrei-api is in development, in public, with a preview planned: API keys, rate limits and priority tiers, and the same licence rules on every response.
⚖️ Using the data you get back
Every result carries an attribution line. Show it to the person reading the
answer. The full register is at the resource viafrei://attribution, and
SOURCES.md is the readable version: every publisher, what it
covers, its licence, and the exact line to reproduce.
Two constraints matter more than the rest, because getting them wrong is a licence breach rather than a style problem:
MTS-K fuel prices are consumer information only. Any other use is unlawful in any form, raw, reformatted or aggregated, and never for the fuel industry or its IT providers. On top of that we ask for no redistribution at all: answer the person who asked; do not build a product out of it. (This is also why this page shows no fuel price.)
DELFI's realtime and disruption feeds are Creative Commons Attribution-ShareAlike (its static timetable and stop directory are CC BY 4.0, and so is VBB's Berlin-Brandenburg feed). Share-alike travels with anything you derive from it: recompute it, reshape it, rearrange it or build a delay table out of it, and that is Adapted Material you must license under BY-SA (art. 1(a) names material "translated, altered, arranged, transformed, or otherwise modified"). Merely showing it beside another source's data is an aggregation and puts no obligation on the other source. The realtime feeds' catalogue records name no licence version, so do not rely on one for a derivative; SOURCES.md has the detail, and also covers the share-alike databases under the ODbL (OpenStreetMap's and the others).
A third condition applies to one source only. Truck-parking occupancy from Toll Collect's Stellplatz-Informationsdienst (SID) comes with terms that bind everyone who receives the figures: they may be inaccurate, incomplete or out of date, there is no warranty, and nobody may use them to identify a vehicle or a person. ViaFrei passes them on only to a user who has accepted its terms of use, section 2, which carry those conditions. If you build on ViaFrei, let the user answer that question, never answer it for them, and show the condition sentence the result carries with every figure.
🗣️ Tell us when an answer is wrong
ViaFrei is live, free, and still growing. Some sources are thinner than they will be, and a tool can be slow or wrong. A tool that fails is something the server sees. A tool that answers confidently with the wrong thing is not. Use the A tool answered badly, or not at all issue template, saying what you asked and what came back. That report is the one thing we cannot get any other way.
The server itself
The MCP server is a hosted service, and its source is closed. It is not in
this repository and is not published. What is public is the part meant to be:
the tool names, descriptions, input schemas, result shapes and attribution
lines, which is everything a client reads from tools/list. We say this plainly
so nobody spends an evening looking for the server code.
Contributing · Security · Licence
Contributing: yes, please. See CONTRIBUTING.md and CODE_OF_CONDUCT.md. The bridge is small and self-contained, which makes it a good place for a first patch.
Security: never open a public issue for a key, a token or anything that looks like one. SECURITY.md has the private reporting path.
Licence: Apache-2.0 for this code. Data obtained through the server keeps its provider's licence; see NOTICE.
viafrei.de — Deutsch · English · Русский · Български · Українська · Română · Türkçe
Available Tools
24 toolscheck_autobahn_trafficARead-onlyIdempotent
Per motorway (≤ 5), or one Bundesland's motorways with land: an Ampel, then jams, closures, roadworks in force, with place/delay/speed/map. Use when asked about a named motorway now: frei/clear (Ampel), Stau, delay, how it looks, or a LIST of closures; name every motorway (Munich→Berlin: A9). Do NOT use for open/closed/gesperrt/passable, even now, a closure with no time word or a later one (tonight, weekend), or a town, no motorway — check_road_status; Baustellen dated or geplant — find_roadworks_ahead; a named city street: not held; trains (get_train_departures). ~5 min old. Show attribution.
Inputs: lat, lon, land, kinds, +6 more.
check_road_statusARead-onlyIdempotent
If a motorway/B/Land road (NI, NW, HE, BW, MV, SN, TH; B also SH, BY, BE; pass Land/town as place) is open/closed/restricted now/soon; by place, jams, city/Land messages, Hamburg traffic cameras; lorry limits, Lang-Lkw (vehicle). Use when asked if a road's open/closed/gesperrt/passable, even now — "A8 in diesem Moment gesperrt?" — closures tonight/weekend, or Stau in a town (Köln). Do NOT use for a named motorway frei/clear (Ampel) or its jams/delays — check_autobahn_traffic; dated roadworks — find_roadworks_ahead; a named city street: not held, no call. ≤14 days/11 entries. Show attribution.
Inputs: lat, lon, road, limit, +4 more.
check_station_facilitiesARead-onlyIdempotent
Whether the lifts and escalators of a railway station or Köln Stadtbahn stop work now: each with place, state, reason. Another tram, U-Bahn or bus stop (named with its city: "Stuttgart Charlottenplatz") gets its step-free survey where one exists. Use when asked about step-free access, broken lifts, wheelchair or pram: "Funktioniert der Aufzug am Kölner Hbf?", "is the lift at Hamburg Hbf working?". Do NOT use for departures, platforms or delays: get_train_departures (trains), get_departures (bus/tram/U-Bahn); whole station: describe_station. At most 50, broken first. Show the attribution line.
Inputs: limit, eva_no, station, facility, +1 more.
check_transit_disruptionARead-onlyIdempotent
Public-transport punctuality now in a German region: share of trips >5 min late, skipped stops, cancellations, trend, alerts in force. Use when asked if buses and trains run normally, a strike, storm or works disrupt them, or for a line with no place ("ist die RB33 pünktlich?" → line: answered where it runs, or asks which region). Do NOT use for a station's departures or a line from a named DEPARTURE station ("RE1 ab Köln Hbf?"; "nach …" is no station) — get_train_departures. Figures are region-wide. Window ≤ 120 min. CC BY-SA (DELFI) or CC BY 4.0 (VBB, Berlin/Brandenburg): show attribution.
Inputs: lat, lon, line, region, +2 more.
check_weather_warningsARead-onlyIdempotent
Returns the official DWD weather warnings in force for a place — storm, snow, ice, heavy rain, thunderstorm, heat — with Warnstufe 1–4, area, validity and the official text unaltered. At a town or coordinate it adds the DWD road-surface forecast (Straßenwetter-Prognose: dry to black ice, road temperature) for the nearest road-weather stations. Use when asked about weather on a trip, safe driving, storm or snow warnings, or icy roads (Glätte, Glatteis). Do NOT use for a general forecast (not offered) or jams (check_autobahn_traffic). Show the attribution line.
Inputs: lat, lon, place, language, +1 more.
describe_locationARead-onlyIdempotent
Turns a coordinate into words: the nearest address, settlement and motorway junction with their distances, and the Gemeinde, Kreis and Land the point lies in; also any low-emission zone. Use when you already HAVE a lat/lon and need to say where that is. Do NOT use to look up a place or address BY NAME — that is find_place, find_poi or find_address; this only goes coordinate to words. Those come from the municipality the point lies in (its key), not the nearest Kreis point; near the border the answer says so. OpenStreetMap ODbL 1.0 for the address; show the attribution line.
Inputs: lat (required), lon (required), language.
describe_stationARead-onlyIdempotent
One German railway station as its viafrei.de page shows it: address, step-free platforms now, lifts and escalators (out of service first), platforms, the next departures with live delays, service alerts, parking and charging. Use when asked about a station as a whole: "Was gibt es am Bahnhof Köln Hbf?", "tell me about Leipzig Hbf", "is Hannover Hbf step-free today?". Do NOT use for one lift (check_station_facilities), one train's delay or platform (get_train_departures) or a bus stop (get_departures). Show the attribution line.
Inputs: eva_no, station, language, departures.
find_addressARead-onlyIdempotent
Looks up a street address: its coordinate, and the named OpenStreetMap objects at it (company, shop, office) or that none are. Use when the person gives a STREET AND NUMBER — "Bahnhofstraße 12, Fulda" — for the point or the business there, never who lives there. The coordinate passes to any other tool as lat/lon. Do NOT use for a town/district/station name alone (find_place) or a company/shop/landmark by name (find_poi). At most 5 points; a door mapped twice is folded, points far apart say how far; several towns are a question. OpenStreetMap ODbL 1.0; show the attribution line.
Inputs: query (required), limit, language.
find_charging_stationARead-onlyIdempotent
Returns EV charging sites near a place or coordinate: operator, plugs, max power, price per kWh where published, and points free now where live status is published. Filters: plug, power (min/max kW), operator, free now, conditions (24/7, card, free of charge, public). Use when an EV driver asks where to charge ("Wo kann ich laden?", "CCS 150 kW near Leipzig", "ist gerade eine Säule frei?"). Do NOT use for petrol or diesel (find_cheapest_fuel) or E-Kennzeichen rules (get_driving_rules). Radius ≤ 25 km, ≤ 10 sites; missing availability is unknown, never free. Show the attribution line.
Inputs: lat, lon, limit, place, +8 more.
find_cheapest_fuelARead-onlyIdempotent
Returns the cheapest stations for one fuel grade near a place or coordinate: price per litre, brand, address, distance, open state. Use when the user asks where to fill up or what fuel costs. Do NOT use for charging an electric car (call find_charging_station), price history, or traffic (call check_autobahn_traffic). Radius ≤ 25 km, at most 10 stations. For a brand, a name, open now or at a named time, or nearest-first, call find_fuel_station. Each line names the age of its price and opening-hours claim. Prices are consumer information only; the attribution line and MTS-K note must be shown.
Inputs: lat, lon, fuel, limit, +3 more.
find_fuel_stationARead-onlyIdempotent
Finds filling stations around a place or coordinate under any combination of filters — grade, brand, name, open now, open at a time you name, open 24 h — sorted by distance, price or name. Use when the question is WHICH station: the closest diesel to a stop, an ARAL open tonight, what one forecourt sells. Do NOT use for the plain "where is fuel cheapest" question (call find_cheapest_fuel) or for charging an electric car (call find_charging_station). Every result carries the attribution and the MTS-K note, and says how old each price and opening-hours claim is.
Inputs: lat, lon, fuel, name, +9 more.
find_hydrogen_stationARead-onlyIdempotent
Returns hydrogen (H2) filling stations near a place or coordinate, nearest first, with operator, address, pumps (700 bar car, 350 bar truck/bus), opening hours where published and the age of the record. Use when someone asks where to refuel a fuel-cell car, lorry or bus ("Wasserstofftankstelle", "H2 tanken", "hydrogen station near me"). Do NOT use for petrol or diesel (call find_fuel_station) or EV charging (call find_charging_station); LPG/Autogas and CNG are not held — say so. Radius ≤ 150 km, ≤ 10 stations; no live availability or price is published. Shows the attribution line.
Inputs: lat, lon, limit, place, +3 more.
find_nearbyARead-onlyIdempotent
Overview of what is around a place or coordinate: fuel, EV charging, parking, nearest railway station and motorway junction, with distances; everyday places (shop, pharmacy, cash, food, hotel, workshop, police) only when named in categories. Use when asked "what is around me". Do NOT use for a fuel grade's price (find_cheapest_fuel), charger status (find_charging_station), parking occupancy (find_parking), a NAME lookup (find_place/find_poi/find_address), or a coordinate's address (describe_location). Radius ≤ 15 km, up to 3 per category (5 per need). Shows each source's attribution.
Inputs: lat, lon, place, language, +2 more.
find_parkingARead-onlyIdempotent
Parking near a place, a coordinate or along one motorway: lorry parks, car parks, P+R and disabled-badge bays, with total spaces, stated amenities (WC, shower) and published free spaces. Use when asked where to park or leave the car for the train ("Parkhaus in Köln", "Rastplatz A3", "P+R"). Do NOT use for fuel (find_cheapest_fuel) or EV charging (find_charging_station). Radius ≤ 25 km, ≤ 10 sites per list; ODbL and CC BY-SA sources are separate lists (up to three). No "free now" means no published count, not full. No prices: for "was kostet" say so, no call. Show each source's attribution.
Inputs: lat, lon, kind, road, +6 more.
find_placeARead-onlyIdempotent
Looks up a place name and returns every match, each with its kind, population, English name and coordinate; the official key (AGS/RS) only in the structured result. Use when the person asks where somewhere is, when you need a coordinate for another tool, and above all to RECOVER after a tool reported a name as ambiguous — this is where you find out which Neustadt is which. Pass near to rank and separate same-named places by distance. Do NOT use to find a company, shop or landmark: call find_poi. At most 10 results, radius <= 200 km. Every result carries an attribution line to show the user.
Inputs: query (required), lat, lon, kind, +4 more.
find_poiARead-onlyIdempotent
Finds a business or landmark by name or kind — company, shop, clinic, hotel, hostel — with address, category and coordinate. Use when the person names a THING rather than a town: "the adesso office in Dortmund", "the nearest Aldi", "a hotel in Weimar". The coordinate passes to any other tool as lat/lon. Do NOT use for a town, district or station (every tool's place resolves those), nor for fuel, charging or parking (own tools). Give "in" (a town) when you can: far faster than nationwide. 25 per page, 50 via cursor; radius <= 50 km. OpenStreetMap under ODbL 1.0; show the attribution line.
Inputs: name (required), in, lat, lon, +6 more.
find_roadworks_aheadARead-onlyIdempotent
Returns roadworks PLANNED on one motorway, one Bundes-/Landesstraße in NI, NW, HE, BW, MV, SN or TH (BY: B only), or city streets by place, in a date window: where, impact, dates, map links. Use when a date or window is named, it says geplant, or how long a site lasts ("Baustellen auf der A7 in den Sommerferien?"). ONE road/place per call. Do NOT use when more than one motorway is named, for the situation this minute, or for Baustellen with neither date nor geplant — all three are check_autobahn_traffic; whether a road is open — check_road_status. ≤ 92 days, max 20 sites. Show attribution.
Inputs: to, from, road, limit, +2 more.
find_sharingARead-onlyIdempotent
Returns rentable shared bikes near a place or coordinate: bike-sharing stations with bikes and free docks now, and free-floating bikes around, with distance and data age (nextbike incl. KVB Rad, MyRadl, VAG_Rad; Donkey Republic). Use when someone asks for a rental or shared bike ("Leihrad", "Fahrradverleih", "nächstes nextbike", "bike share near me"). Do NOT use for parking (find_parking) or a general look around a place (find_nearby). Radius ≤ 5 km, ≤ 20 stations; e-scooters are not covered. Shows each source's attribution.
Inputs: lat, lon, limit, place, +3 more.
find_speed_camerasARead-onlyIdempotent
A town's published speed-enforcement locations (fixed, red-light, section control, announced mobile checks, measuring sites) by kind and street plus OpenStreetMap's fixed cameras. § 23 Abs. 1c StVO binds a driver's device use, not publication. Use when someone planning a trip asks where speed cameras are ("Blitzer Köln"). Planning only: show the answer's StVO notice verbatim. To someone driving: the notice and the list for a stop. Never read locations to a driver or warn live. Do NOT use for speed limits (get_driving_rules) or roadworks (check_road_status). Area ≤ 25 km. Shows the attribution.
Inputs: lat, lon, limit, place, +2 more.
get_departuresARead-onlyIdempotent
Scheduled departures from any German stop — bus, tram, U-/S-Bahn, train, ferry — or the nearest stops around a place ("Abfahrten in der Nähe"). Use when asked when a bus, tram, U-/Stadtbahn or ferry goes ("welche Bahnen" at a Hbf too), or for another DAY or a time over 2 h away: "Wann fährt der nächste Bus ab Fulda Bahnhof?" Do NOT use for a rail station's trains today: get_train_departures. Plan times with live delay/cancellation where held; punctuality: check_transit_disruption. No A-to-B journeys: say so, no call. Holds ≥ 48 h ahead, ≤ 3 days. 15 per call. Show the attribution line.
Inputs: lat, lon, stop, when, +6 more.
get_driving_rulesARead-onlyIdempotent
Returns the German road rules a visitor needs: low-emission zones (Umweltzone) and the Feinstaubplakette, speed limits (advisory 130), winter tyres, alcohol, the Sunday lorry ban, tolls, Rettungsgasse, what must be in the car, electric cars. Use when someone drives through Germany or asks whether they may enter a city or street. Do NOT use for live traffic or closures: check_autobahn_traffic; to FIND a charger: find_charging_station. city narrows to its zone; place or lat+lon checks a point against the published zone boundaries. Sourced, dated; show the attribution. Not legal advice.
Inputs: lat, lon, city, place, +2 more.
get_train_departuresARead-onlyIdempotent
Next trains at a German railway station: platform, delay, cancellations. Use when asked when a train, S-Bahn or ICE leaves a named station, or if a train or line from it is late; later today ("heute Abend") stays here. A line with no DEPARTURE station ("ist die S1 pünktlich?"; a destination, "nach …", is not one) — check_transit_disruption. Lists U-Bahn and trams too. Do NOT use for one bus/tram/U-Bahn line, a non-railway stop, another day or over 2 h — get_departures. Types ICE/IC/RE/RB/S; no destination filter; whole station: describe_station. ≤ 15 rows, ≤ 120 min. Show the attribution line.
Inputs: when, limit, eva_no, station, +3 more.
stop_watchA
Ends a watch this conversation opened with watch_situation, so no further notifications arrive for it. Use when the person no longer needs to be told — "du musst mir nichts mehr zur A8 sagen", "stop watching that charger". No id at hand: pass kind ("weather") and key in the person's words ("A8", "Bamberg", "Kiel"); one match is stopped, several are listed. Do NOT use to look a situation up (call check_road_status), to list what is running (read viafrei://watches), or to cancel anything outside this chat. Another session's watch is never found. Results carry their attribution line.
Inputs: key, uri, kind, language, +1 more.
watch_situationA
Opens a watch so THIS conversation is told when something changes: a road closed or restricted, a motorway jam, a stop running late, a weather warning, a charger freeing up. Use when asked to be told later: "sag mir Bescheid, wenn die A8 wieder frei ist", "tell me when a warning comes for Kiel". A name is enough as key; no lookup first. Do NOT use to look up now, nor for e-mail, SMS or alerts outside this chat — we cannot send one; say so. Set hours (≤ 24, default 3) for the time asked; condition narrows it (only the reopening, one charge point). Session-scoped, ≤ 10 watches. Show attribution.
Inputs: key (required), kind (required), hours, until, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 24 tools
Most tools have clearly distinct purposes and the descriptions include extensive Do NOT cross-references. However, several clusters overlap meaningfully: road traffic/status/roadworks, bus/tram departures vs train departures vs region-wide disruption, and place/POI/address/location lookups. An agent can usually tell them apart, but only by carefully reading long descriptions.
All tool names use consistent snake_case verb_noun patterns such as find_*, check_*, get_*, describe_*, watch_situation, and stop_watch. The verb variety reflects real semantic differences rather than inconsistent conventions.
The server covers a broad transport and travel-info domain, so 24 tools are not absurd, and each has a defensible role. Still, 24 tools is above the ideal 3–15 range and includes many adjacent retrieval variants that make the surface feel heavy.
Coverage is broad: stations, departures, disruptions, roads, roadworks, fuel, charging, hydrogen, parking, sharing, places, weather warnings, and watches are all represented. Obvious gaps remain, such as A-to-B journey planning, a general weather forecast, LPG/CNG, and e-scooters, but the core information surface is robust.
Maintenance
Related MCP Connectors
Geocoding, routing, isochrones, traffic, weather, and place search for AI agents. 19 MCP tools.
Keyless open data for 84 German cities: 12 lean read-only MCP tools covering 67 data types.
GovData.de MCP — Germany's national open-data portal (CKAN API).
Routing, geocoding, places, matrix and map tools for location-aware AI workflows.
Related MCP Servers
- AlicenseBqualityDmaintenanceMCP server providing AI agents with access to German government open data. 12 tools across 6 categories: Autobahn traffic, DWD weather, NINA disaster warnings, SMARD energy market, Bundestag parliamentary data, and pollen forecasts. All APIs are free, no keys required.1621 PyPI3MIT
- AlicenseAqualityDmaintenanceAn MCP server that exposes the Deutsche Bahn public transport API to any MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.). Five tools cover station search, departures, journey planning, trip details, and nearby stations.61MIT
- AlicenseAqualityCmaintenanceKeyless remote MCP server for German public-infrastructure open data: weather, air quality, traffic, public transit, parking and roadworks across 84+ German cities (DWD, Umweltbundesamt, Mobilithek, GovData). 38 read-only tools.1217Apache 2.0
- AlicenseNot gradedqualityCmaintenanceProvides routing, distance/duration matrix, isochrones, snap to road, elevation, and geocoding tools from Openrouteservice for AI agents via MCP.118 npmMIT