Skip to main content
Glama
668,996 tools. Updated 2026-10-17 08:49

"Railway" matching MCP tools:

  • Get live arrivals for ANY railway station by its EVA number. Mirror of ``station_board_departures`` for arriving trains (all categories, real-time delays, disruption messages). Get the EVA from ``get_city_resource(slug, resource='stations')``. Read-only.
    ConnectorNo auth
  • Mint a one-time uploader script for a private Storage blob (any file type). Storage is the org's binary store: bytes go to the Railway bucket, metadata to ``drive_objects``. Objects stay private until a human seat calls ``storage_publish`` (agent seats must ``request_gated_approval(gate=publish)``). Document MIME types (Markdown, HTML, plain text, diagram JSON/YAML) are stored as blobs; versioned edit / ``/s/`` publish still use ``file_upload_request``. Pass ``work_id`` and/or ``project_id`` to attach after ingest (``kind=artifact``; transcripts stay on shared files). Pass ``parent_id`` to place the file in a folder. Batch uploads are multiple grants (one file each) — console multi-select uses sequential ingest, not a multi-file grant. Returns ``upload_url``, ``upload_token``, ``max_bytes``, and a self-deleting Python ``script``. Token is single-use and expires in ~10 min. ``drive_upload_request`` is a deprecated alias of this tool.
    ConnectorNo auth
  • Find the best connections by train, tram, bus, boat and mountain railway between two places in Switzerland, over the official Swiss timetable. Door to door: an address or a named place works as well as a station, and the walk to and from the nearest stops is included. Use it for "how do I get from A to B", "the next connections from Olten to Zürich", "when is the next train to …", "I need to be in Bern by 9" — it gives departure and arrival times, changes and platforms. Prefer it to the departure board for any question with a destination. Every journey comes with a picture_url: a link that opens a ready-made image of the connection, for looking at or sharing. Inputs: from and to are each A station or stop name ("Zürich HB", "Bern", "Lausanne, Flon"), an address ("Bahnhofstrasse 1, Winterthur"), a named place ("ETH Zürich", "Kunsthaus"), a coordinate as "geo:47.3769,8.5417", or a place_id returned by find_place ("stop:8503000"). Names are read the way a rider types them; an ambiguous name returns candidates instead of a guess. Give departure (leave at or after) or arrival (be there by), not both; with arrival, the answer also brings the first connection arriving up to 30 minutes after it, for a user who said "around"; both are Swiss local time in ISO 8601, e.g. "2026-09-26T08:00"; an explicit offset or Z is converted. A bare "08:00" means today (tomorrow if it has long passed). Omit for now. via is up to three stations or stops the journey must pass through (then one best journey is returned); to stop somewhere on the way, use plan_day_out. max_transfers caps the number of changes (0 = direct only). limit is how many alternatives to return (1–8, default 4). All times are planned timetable times with their Swiss offset; live delays are not included. Example: {"from": "Winterthur", "to": "Bern", "departure": "2026-09-26T07:00"}
    ConnectorNo auth
  • Search parcels by their ACTUAL cadastral use (ALKIS "tatsächliche Nutzung", also called Nutzungsart, Grundstücksnutzung or Flächennutzung), nationwide or within a region — cemeteries, quarries, sports grounds, landfills, allotments, power stations, industrial land, anything the cadastre records as a use. This is a discovery tool for sites matching a use profile; to look up ONE known parcel by Gemarkung/Flur/Flurstücksnummer or to get its size, use assetfy_db_find_parcels instead, which covers all states. Spelling differences between states are handled: the states write the same use as "Industrie- und Gewerbefläche", "Industrie Und Gewerbeflaeche", "IndustrieUndGewerbeflaeche" or "Industrie und Gewerbe", and any of those spellings finds all of them. Search broadly and with the stem of a word — "friedhof" also finds "Parkfriedhof" and "Historischer Friedhof". Note the coverage: NRW, Hessen, Brandenburg, Mecklenburg-Vorpommern, Schleswig-Holstein and Baden-Württemberg are searched in their own ALKIS land-use datasets and carry the detailed designation (e.g. "Lagerfläche") plus further attributes such as Zustand; Niedersachsen, Hamburg, Bremen, Saarland, Sachsen, Sachsen-Anhalt, Thüringen and Rheinland-Pfalz are searched through the coarser parcel attribute, which knows only the main category. Baden-Württemberg records Funktion and Vegetationsmerkmal but no Zustand. Bayern and Berlin are not covered by this tool and come back in skipped_states rather than as an empty result — assetfy_db_screen_sites covers both. A nationwide search is therefore not exhaustive, and absence of a hit is not evidence of absence. This tool knows nothing about listings; for railway land that is for sale (Grundstücke mit Gleisanlagen zum Verkauf) use assetfy_db_rail_listings. SEVERAL CRITERIA AT ONCE — a use PLUS a share of the parcel ("must cover at least 80 % of the Flurstück"), a size window, a building coverage (Bebauungsgrad), or a Bebauungsplan — is covered by assetfy_db_screen_sites, which evaluates all of them in one database pass per state. Checking candidates from here one by one with assetfy_db_planning_at_point and assetfy_db_buildings runs out of calls before the last criterion is reached, which is the reason assetfy_db_screen_sites exists. This tool is for a single use as the question: which parcels carry it, where, and how large. If a nationwide search times out on a common use, split it by bundesland rather than retrying — and say in the answer which states you actually covered.
    ConnectorOAuth
  • Nearest listed level crossings to a point, closest first. Returns one line per crossing — distance in MILES, then name, type, region and a status URL ending .md. Distance is straight-line (great circle) between the point and the crossing, NOT distance by road or along the railway: it answers 'which crossings are near this place', not 'which will this train reach next'.
    ConnectorNo auth
  • Turn a place (address, POI, town) into coordinates. Ask two ways, and they combine: `query` is free text — one run-together string, the way a person types into a search box — and `street`, `housenumber`, `city`, `postcode` and `country` name the parts of an address separately. At least one of the two is required. Pass the parts whenever you already hold the address in parts (a form, a CRM row, a manifest): components are REQUIREMENTS, not hints, so `city: "London"` means a result outside London cannot come back at all, where "London" inside `query` only reorders. `country` takes an ISO 3166-1 alpha-2 code or a country name ("GB", "United Kingdom"); a value naming no country is refused rather than silently matching nothing. Returns up to `limit` (default 10) candidates with name, one-line label, lat/lon, type and address parts. Pass `focus` {lat, lon} to rank results near a location higher. A bare city or town name (no comma) lists that city's airports and main railway stations directly behind it, ahead of namesakes elsewhere. Each hit also carries `match`: a per-component matched/inferred/unmatched verdict, the `score_gap` to the runner-up, and which backend answered. READ IT before acting on an address — an unmatched or inferred postcode on the top hit means the answer does not carry the address you asked for, and a small `score_gap` means the ranking barely chose, so show the alternatives instead of picking one. Use `verify_places` when the address came from a model or a user and needs checking rather than using. Results are matched in `lang` (default "en"), so English exonyms — "Munich", "Cologne", "Geneva" — resolve to the place meant; pass `lang` when querying in another language, or "default" for each place's local name.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that exposes the Railway API as tools for Claude. Manage Railway projects, services, deployments, variables, environments, and domains directly from Claude.
    60 npm
    MIT

Matching MCP Connectors

  • Develop, manage, and debug Railway projects, services, and deployments from within agents.

  • Indian Railways IRCTC helps you to view, track trains schedules, ticket status and more.

  • Search real estate listings (Immobilien, Angebote, Inserate, Exposés) directly in the database with structured filters — the tool for "vermietete Wohnungen mit hohen Mieteinnahmen", "Zwangsversteigerungen im Raum X", "Garagen unter 20.000 €", "BVVG-Flächen", "Gewerbeobjekte", "Grundstücke ab 800 m²". Pick the market with `type`: housebuy (Haus), apartmentbuy (Eigentumswohnung), landbuy (Grundstück, Bauplatz), garagebuy (Garage, Stellplatz), officebuy (Gewerbe, Büro), agriculture (BVVG-Flächen, landwirtschaftliche Flächen der Bodenverwertungs- und -verwaltungs GmbH). Boolean filters cover the special cases: foreclosure for Zwangsversteigerungen, rented for vermietete Kapitalanlagen, private_offer for Angebote ohne Makler, price_reduced, leasehold for Erbbaurecht. Monthly rental income (Mieteinnahmen), gross yield and return on equity are returned for every hit where the platform reported them. Mieteinnahmen is the monthly rent the portal states — what the portals label "Cashflow" — not a cashflow after costs and financing: it is never negative, so it cannot tell a positive from a negative cashflow. Not every filter exists for every type — BVVG parcels carry no foreclosure or rented flag, only houses and apartments have rooms — and any filter that cannot apply is reported back in ignored_filters instead of being silently dropped. For prices per m² across a whole postcode area rather than single listings, use assetfy_db_price_heatmap; for cadastral parcels rather than marketed properties, use assetfy_db_find_parcels. For listings involving railway land — alte Gleisanlagen, Gleisanschluss, Bahngelände — use assetfy_db_rail_listings, which joins them with the cadastre and the rail network.
    ConnectorOAuth
  • Parcels (Flurstücke) along railway lines whose actual use (tatsächliche Nutzung) is "Bahnverkehr" — the railway land, as a rule owned by DB InfraGO — measured ACROSS the track: how wide that land is beside the outermost existing track, on each side. Answers "welche Bahngrundstücke sind breit genug für ein weiteres Gleis", "wo passt ein Überholgleis / eine Kreuzungsstelle / ein drittes Gleis", "wo reicht der Bahnkorridor für einen Gleisausbau". The line is sampled every step_m with a cross-section (Querprofil); in each, the existing tracks come from the ISR and the free width is the contiguous Bahnverkehr land beyond the outer track. Returns (1) abschnitte: continuous stretches where the free width on one side stays ≥ required_free_width_m for at least min_run_length_m — the candidate sites — with side (e.g. "östlich der Gleise"), length, free width, nearest station and the parcels involved; and (2) flurstuecke: those parcels with Gemarkung/Flur/Flurstück, area, Bahnverkehr share, free width and length along the track. Needs a region (landkreis, lat/lon + radius_m or bbox) and/or strecke_nr; at most 80 km of line per call — split by strecke_nr if the region holds more (the refusal lists the lines). The use comes from the parcel attribute where the state has it, otherwise from the state’s own land-use dataset (NRW, Hessen, Brandenburg, Mecklenburg-Vorpommern, Baden-Württemberg, Berlin, Bayern) and only then live from the state ALKIS WFS; where none exists the parcels the track runs over are used instead, and the result says so (tn_quelle). This is a screening, not a plan: the ISR draws double track schematically 6 m apart (real 4.0–4.5 m, so the real free width is about 1 m larger), station tracks and sidings are not in the ISR, and terrain, embankments, masts and buildings are not considered — check candidates with assetfy_db_buildings, the planning tools and assetfy_get_aerial_image (the start and ende of an abschnitt span its bbox).
    ConnectorOAuth
  • Find land parcels, property units or buildings matching search criteria — the sourcing tool. Give a `location` (place name, area code or postcode district) or a `bbox`. STRATEGY MODE (preferred). Pass a `strategy` key from `sourcing_strategies` with `lad_code` or `postcode_district`, and the search runs the published preset: its filters, its ranking, and a `score_components` breakdown on every row saying which term earned what. Override any published filter with `strategy_overrides` — `{"min_yield_pct": 8}` — or pass null for a key to switch that filter off. An unknown key is rejected rather than ignored. `listing_state` restricts to on- or off-market units; page with `cursor` from `next_cursor`. Strategy mode ignores the legacy filters below. Filter land by use class and `max_built_coverage` (built footprint as a share of plot, so 0.2 finds substantially empty plots), units by type, bedrooms, EPC band and tenure, and either by owner — `min_years_owned` is the usual off-market signal, and `owner_types` separates companies from public bodies. Returns parcels with ownership attached where the bulk register knows it. For land or units, use sourcing_owners to resolve a specific set afterwards. PARKS, HEATHS, RAILWAYS, CEMETERIES AND UTILITY LAND ARE EXCLUDED BY DEFAULT. The scan is ordered by parcel size, and the largest parcels in any area are its open spaces — unfiltered, a Camden search returned Regent's Park, Hampstead Heath, a cemetery and railway land as its top six, while 13,047 residential parcels in the same borough never appeared. Pass `include_undevelopable=True` to see them; they come back with no indicative land value, because a residual on a heath is a meaningless number that reads as an authoritative one. BUILDINGS: asset="buildings" searches recorded footprints with footprint area, storey count, unit count, dominant EPC and tenure. Supply one location, bbox or drawn polygon. Results include matching footprints and stable building IDs for linked-unit inspection. Page with offset, limit up to 100. Unit/owner/strategy criteria are rejected for buildings. INVENTORY PAGINATION: for land or units, supply offset=0, then next_offset while has_more is true. These bounded pages apply every criterion before pagination; derived-score/strategy criteria are not accepted in this mode. Unit size uses min/max_floor_area_m2; land and buildings use min/max_area_m2. Repeated warehouse reads are cached for five minutes. Results remain metered by the gateway. No unknown tenure or EPC is asserted to meet a positive filter. UK only. Costs 40 credits.
    ConnectorNo auth
  • Scheduled departures from any German stop — bus, tram, U-Bahn, S-Bahn, train, ferry. 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 railway station's trains now or later today — get_train_departures. Plan times, with a live delay or cancellation per row where held; regional punctuality check_transit_disruption. No A-to-B journeys: say so, no call. Holds ≥ 48 h ahead, ≤ 3 days; further out, say so. 15 per call. Show the attribution line.
    ConnectorNo auth
  • Spot-trade a tokenized equity (xStocks / Ondo) via Jupiter, non-custodial. side: buy | sell. amount is in base units of the INPUT token (USDC 6dp for a buy, the equity token for a sell). These are tokenized SECURITIES: the call is geo-gated (Reg S = no US persons; declare jurisdiction once via the jurisdiction arg) and OFAC-screened, and requires per-execution confirmation -- WITHOUT confirm=true it returns a quote + disclaimer and does NOT execute (no autonomous equity execution). With confirm=true it returns an UNSIGNED base64 tx to sign + broadcast; pass signed_transaction to broadcast a caller-signed tx. Value-bearing: past the daily free tier an x402 payment_header is required. ip = caller origin IP for the Reg S geo gate (US IP -> refused even with an attestation; an agent's Railway Singapore egress resolves to SG and passes). ``venue_hint`` is ADVISORY, never required -- equity routes via the issuer registry (one surface today); an unknown hint raises. ``idempotency_key`` (optional): see jupiter_swap -- same replay-on-retry semantics, same key reused across build + broadcast. ``verify`` (extending default True): when broadcasting (signed_transaction supplied), await on-chain confirmation and re-read the equity mint balance -- the response gains a ``verification`` block ({confirmed, slot, post_state, expected_vs_actual}). Gate follow-on decisions on ``verification.confirmed``, never on tx_signature alone. Set False to skip for latency-sensitive callers. Verify any prior signature later with the standalone ``verify_transaction`` tool.
    Connector
    Destructive
    No auth
  • Search Assetfy real estate listings around named places, filtered by structured criteria (price, plot and living area, rooms) and ranked — the tool for "finde mir eine Wohnung/ein Haus/ein Grundstück in X für unter Y". Takes place names or coordinates plus those criteria and returns a scored shortlist. The criteria are hard limits: a listing whose value lies outside them is dropped (counted in filtered_out); a listing that does not state the value stays in, with the gap named in its risks. Every criterion goes into a structured field; there is no free-text input. Needs locations or center_points — without a place use assetfy_db_search_listings for the whole listing stock, and assetfy_db_rail_listings for listings involving railway land (alte Gleisanlagen, Gleisanschluss, Bahngelände). Covers listings for sale (Kaufangebote, Verkaufsangebote, Immobilien, Objekte): Wohnung/apartmentbuy, Haus/housebuy, Grundstück/Bauplatz/landbuy, Garage/Stellplatz/garagebuy, Gewerbe/Büro/officebuy, Zwangsversteigerung/official_foreclosure. This searches MARKETED PROPERTIES, not the cadastre: for parcels by Gemarkung/Flur/Flurstücksnummer use assetfy_db_find_parcels, and for parcels by their recorded use use assetfy_db_find_parcels_by_use — neither of those knows anything about prices or listings. Use assetfy_search_real_estates instead when you already have a coordinate and just want what is nearby, without ranking.
    ConnectorOAuth
  • Aerial image (Luftbild, Luftaufnahme, Orthofoto — what users often call a Satellitenbild; digitales Orthophoto DOP20 — 20 cm ground resolution, Bremen and Nordrhein-Westfalen 10 cm) of a location in Germany, fetched live from the official WMS of the state survey office — the imagery of the aerial layer on the Assetfy map. Returns the image itself (JPEG, north up, true to scale) together with its footprint: bbox in WGS84, metres per pixel, state and the required attribution. Use it to check the results of the other tools by eye: whether tracks still lie on railway land from assetfy_db_rail_corridor_parcels or assetfy_db_rail_listings, whether the free strip beside the track is really free (embankment, trees, buildings, masts, roads, station tracks), whether a parcel is built on, what a site looks like. Give either lat/lon with size_m — a square centred on the coordinate — or a bbox [west, south, east, north], e.g. spanned by start and ende of a corridor abschnitt; a bbox is padded by 10 % (at least 25 m) and widened to an aspect ratio of at most 2:1 so the surroundings stay visible. Up to 3000 m edge length per image — split longer stretches. Keep size_m near 100–300 m to see tracks, masts and small buildings; above about 1000 m only the coarse layout remains. Parcel boundaries are not drawn in: relate them through the bbox. The imagery is the state's current flight, as a rule one to three years old; the service supplies no capture date. For CAD/GIS the result also carries cad: the same area north-up in the state's UTM system (EPSG:25832, Berlin/Brandenburg/M-V/Sachsen EPSG:25833) as a direct download URL of the state WMS in full resolution (no login), with the world file (.jgw) to save next to it — the image then sits in place under a DXF. With the same lat/lon and size_m as assetfy_get_site_plan the extent is exactly that of the DXF.
    ConnectorOAuth
  • Find parcels (Flurstücke) by their actual cadastral use AND several further criteria AT ONCE — the multi-criteria variant of assetfy_db_find_parcels_by_use, for a site profile across many parcels. Returns only the parcels that pass every criterion: the use, how much of the parcel that use covers, the parcel size, how densely it is already built (Bebauungsgrad), and whether a Bebauungsplan applies. Example: "Lagerflächen, die mindestens 80 % des Flurstücks einnehmen, 10.000 bis 100.000 m², 5 bis 30 % bebaut, mit B-Plan, deutschlandweit". Every criterion is evaluated in one database pass: a nationwide screening takes one call per state, and the hits need no per-parcel follow-up calls to assetfy_db_planning_at_point or assetfy_db_buildings for these criteria. Every hit reports the measured figures it passed on (nutzung_anteil_prozent, bebauungsgrad_prozent, the Bebauungsplan) so the numbers can be checked, plus assetfy_url. The distance to the nearest Autobahn junction is covered by max_autobahn_km and measured in the database. Noise from the strategic noise maps is covered by max_laerm_lden_db / max_laerm_lnight_db, and every hit reports its loudest mapped band as umgebungslaerm. Bebauungspotenzial is covered by grz_min/grz_max, gfz_min/gfz_max and min_bgf_potenzial_m2 ("GFZ unter 0,5, mindestens 1.500 m² zusätzliche BGF"), and every hit reports it as bebauungspotenzial, with keine_bauflaeche: true where the map greys the parcel out as no building land (forest, farmland, roads) — such parcels stay in the result, the user decides; with these filters nutzungsart may be left out, but then the search needs a region (zip, or lat/lon + radius_m). Existing EV fast-charging nearby ("weniger als 5 HPC-Ladepunkte im Umfeld") is covered by max_hpc_ladepunkte with ladesaeulen_radius_km, counted against the Ladesäulenregister of the Bundesnetzagentur. The criteria this tool does NOT cover — distance to a substation, to a railway line — apply to the RESULT, not to the search: screen here first, then check the few survivors, or use near_use in assetfy_db_find_parcels_by_use for a second cadastral use nearby. Coverage: all 16 states, from three kinds of data — every hit says which in nutzung_quelle. States with their own detailed ALKIS land-use dataset carry the detailed designation (e.g. "Lagerfläche"); the others record the use as text at the parcel — always the main category, the detail only in some states — so a main category ("Industrie", "Friedhof", "Bahnverkehr") finds parcels in all of them while a detailed term can miss parcels there. Bayern has no parcels: there the hit is the ALKIS use area itself, with its size, Bebauungsgrad and Bebauungsplan, and no Flurstück number. See the coverage note in the result for the current split.
    ConnectorOAuth
  • Listings FOR SALE (zum Verkauf) — Grundstücke, Gewerbeobjekte, Häuser and BVVG land from the Assetfy listing stock (real_estates_*) — that involve railway land: alte Gleisanlagen, Gleise, Gleisanschluss, Anschlussgleis, Bahngelände, Bahnbrache, ehemaliger Güterbahnhof, Bahntrasse, Bahndamm, Stellwerk, Lokschuppen. This is the tool that joins the property market with railway and cadastral data; it answers "Grundstücke zum Verkauf mit alten Gleisanlagen", "Gewerbefläche mit Gleisanschluss kaufen", "ehemaliges Bahngelände zu verkaufen". Every hit carries its evidence: (1) the listing names railway facilities — the title, for BVVG also the description; "Bahnhofsnähe", "Bahnhofstraße" or "S-Bahn" do not count; (2) the parcel (Flurstück) under the listing coordinate has the actual use (tatsächliche Nutzung) Bahnverkehr — only where the coordinate is not a locality geocode shared with other listings, and checked against the advertised plot area; (3) the nearest operating line from the Infrastrukturregister (ISR) of DB InfraGO — railway land without an operating line within 100 m points to disused, dismantled, siding or station tracks, and the NRW cadastre adds the state "außer Betrieb, stillgelegt"; (4) where the listing has an exact address with house number (as for the exact markers on the Assetfy map, but not when the geocoder put a business or institution in front of the street — that is the address of a POI, not of the property), its distance to the nearest operating line counts by itself: up to 100 m "stark", up to 500 m "mittel" — proximity to a line, not proof of tracks on the plot. evidenz is "stark", "mittel" or "schwach"; "schwach" — a railway parcel at the coordinate that is much larger than the listing or cannot be compared because the listing states no plot area (usually a geocode on the neighbouring track), or a railway term only in a long BVVG description (usually the transport connection) — is left out unless include_weak is set. Nationwide by default, or within a Landkreis, bbox or radius. The cadastral check runs where the state cadastre in the database carries the actual use; elsewhere only the listing text counts, and the result lists which states were checked. No source says whether tracks are still on site — confirm with the exposé and the aerial image (assetfy_get_aerial_image at the listing coordinate). For railway land that is not on the market use assetfy_db_rail_corridor_parcels or assetfy_db_find_parcels_by_use with nutzungsart "Bahnverkehr".
    ConnectorOAuth
  • Next trains from 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 ("RE1 from Köln Hbf late?"); later today ("heute Abend") stays here. A line with no DEPARTURE station ("ist die S1 pünktlich?"; a destination, "nach …"/"zum …", is not one) — check_transit_disruption. Do NOT use for buses, trams, a non-railway stop, another day or a time over 2 h away — get_departures. Train type: categories (ICE/IC/RE/RB/S); no destination filter. ≤ 15 rows, ≤ 120 min. Show the attribution line.
    ConnectorNo auth
  • [OBSERVATION TOOL] Return current verified multimodal physical state of a port. Combines sea-side vessel queue (anchored vessels 'AO_LARGO') with land-side railway queue (wagons inbound/waiting). Returns sources for full provenance. Args: port_id: UN/LOCODE e.g. "BRPNG" (Paranaguá), "BRSSZ" (Santos).
    ConnectorNo auth
  • Railway lines (Bahnstrecken, Gleise) of the German federal rail network from the Infrastrukturregister (ISR) of DB InfraGO: route number (Streckennummer), sections (Streckenabschnitt von–bis, km), number of tracks (eingleisig / zweigleisig), line speed, electrification, traffic type (Personenverkehr, Güterverkehr, S-Bahn), line class, ETCS and TEN classification — plus stations and junctions (Betriebsstellen: Bahnhof, Haltepunkt, Abzweig, Überleitstelle) and, on request, bridges and tunnels and the line geometry. Search by Streckennummer, by a station or section name, by Landkreis, bbox or around a coordinate. Answers "welche Bahnstrecken verlaufen durch X", "wie ist die Strecke 6088 ausgebaut", "wo ist die Strecke eingleisig". For the parcels along a line — the railway land itself and whether there is room for another track — use assetfy_db_rail_corridor_parcels.
    ConnectorOAuth
  • Look up wheelchair-accessible / multipurpose toilets inside a train station, including floor, gender, equipment (wheelchair, ostomate, diaper table) and the nearest exit. Covers 526 Tokyo stations (Tokyo Bureau of Social Welfare data). Major stations outside Tokyo (Yokohama, Kawasaki, Omiya, Chiba, Fujisawa, Shin-Yokohama…) return an in-station layer that groups accessible toilets by ticket gate — inside vs outside — per railway operator. Accepts Japanese (新宿, 横浜) or romaji (Shinjuku, Yokohama) for major stations.
    ConnectorNo auth
  • Look up wheelchair-accessible / multipurpose toilets inside a train station, including floor, gender, equipment (wheelchair, ostomate, diaper table) and the nearest exit. Covers 526 Tokyo stations (Tokyo Bureau of Social Welfare data). Major stations outside Tokyo (Yokohama, Kawasaki, Omiya, Chiba, Fujisawa, Shin-Yokohama…) return an in-station layer that groups accessible toilets by ticket gate — inside vs outside — per railway operator. Accepts Japanese (新宿, 横浜) or romaji (Shinjuku, Yokohama) for major stations.
    ConnectorNo auth
  • Search trains running between two Indian railway stations. Returns train number, name, departure/arrival time, distance, class availability (1A/2A/3A/SL/CC/EC), and running days (Mon-Sun).
    ConnectorNo auth