Retrieve live arrivals for any German public transport station using its station ID. Get real-time data for trains, buses, trams, U-Bahn, and S-Bahn.
458,158 tools. Updated 2026-08-14 23:05
"Deutsche Bahn" matching MCP tools:
- Get live departures for any German public transport stop by its station ID. Includes trains, buses, trams, U-Bahn, and S-Bahn.
- Find educational resources across content, collections, and topic pages with one parallel search, returning organized results.Apache 2.0
- Search the global GLEIF database by company name to verify business entities. Retrieve LEI codes, registration details, legal addresses, and founding dates for due diligence and KYC processes.MIT
- Retrieve Swiss train composition and car ordering for a train number, showing classes, sectors, wheelchair access, bike hooks, dining car, family zones. Check boarding zones and amenities in advance.MIT
- Check current disruptions in Swiss public transport, including train cancellations, delays, and platform changes. Filter by location or line to get relevant alerts.MIT
Matching MCP Servers
- Flicense-qualityCmaintenanceProvides unified access to Deutsche Bahn APIs for real-time railway data, station information, timetables, disruptions, parking, and accessibility services.18
- AlicenseAqualityCmaintenanceProvides access to Deutsche Bahn train timetables, station information, and schedule changes through Model Context Protocol tools and resources.47016MIT
Matching MCP Connectors
Deutsche Bundesbank (Germany's central bank) statistics MCP.
Germany shipping labels for AI agents: buy Deutsche Post and more, track and refund via Shippo.
- Ban a user from a Telegram supergroup or channel permanently until unbanned.MIT
- Trace majority-ownership chains for a public company, upward to its ultimate controller or downward to its controlled entities, citing evidence and abstaining when no verified control edge exists.MIT
- Retrieve comprehensive company data by LEI code. Access full business details, BIC codes, and corporate events using the 20-character Legal Entity Identifier.MIT
- Retrieve current Austrian railway (OeBB) service alerts and disruptions, including affected stations and date ranges. Filter by product type to see relevant travel interruptions.MIT
- Retrieve official German statistical data from Destatis, including population, GDP, unemployment, and inflation indicators for analysis and reporting.MIT
- Retrieve current German energy prices for electricity and gas, including day-ahead market rates and import costs, using official Bundesnetzagentur data.MIT
- Search over 6000 German federal laws and regulations by title or abbreviation to find specific legal information from gesetze-im-internet.de.MIT
- Search Deutsche Bahn train stations by name or station code to find matching locations in the timetable database.MIT
- Validate e-invoice XML for compliance with XRechnung/ZUGFeRD standards, checking syntax, required fields, and German business rules (BR-DE).MIT
- Query the German federal legislation database to find laws, ordinances, and administrative provisions. Search by keywords, abbreviations, or full-text content.
- Search German federal court decisions from BGH, BVerfG, and other high courts to locate binding judgments. Filter by court, date, or document type to access official case law with ECLI references.
- ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across Pipeworx's 1455 STRUCTURED data sources (SEC filings, FRED/BLS economics, FDA, USPTO patents, markets, science, government records, etc.) in ONE call — this is NOT open-web search. Decomposes your question into focused facets, routes each to the right one of 5,529 tools IN PARALLEL, and returns a findings packet: verbatim evidence + confidence + source + fetched_at + a stable pipeworx:// citation per finding, with explicit gaps[] for facets the data couldn't answer (never invented). Best for broad/multi-part questions over structured data ("compare X and Y's regulatory + financial exposure", "research the filings + market picture for ACME"). For a single lookup use ask_pipeworx (one LLM call, not many). For BREAKING or colloquial CURRENT-NEWS / "what's the world saying about X" topics, prefer ask_pipeworx — it routes to live news APIs and the *-news-feeds packs; deep_research returns mostly empty gaps[] when the topic isn't in the structured catalog. Second-hop iteration: depth:"standard" re-angles unanswered gaps (gap recovery); depth:"thorough" additionally chases the best leads from the first pass — so multi-step questions resolve in one call. Every finding carries a `hop` field and a citation_uri — a resolvable pipeworx:// record URI, present only when the source emits one that resources/read can actually serve, so a citation you get back is always fetchable. "standard" and "thorough" also return contradictions[] flagging findings that disagree. Large records are semantically excerpted to the passages relevant to each facet (not head-truncated), so answers deep in a long filing/series aren't missed. Expect 15-60s (thorough with its follow-up + contradiction pass: up to ~90s).Connector
- "What's the ticker for…" / "find the CIK for…" / "what's the LEI for…" / "what's the RxCUI for…" / "look up the ID for…" / "what is X's official identifier" / "who owns X" / "is X a subsidiary of Y" — resolve a user-spoken NAME to the canonical/official identifiers other tools require as input. Use FIRST whenever you have a name but need an ID. SUPPORTED TYPES: "company" (cross-source identity spine: 10-digit CIK + ticker + company_name from SEC EDGAR, legal-entity LEI from GLEIF with parent/ultimate-parent/children ownership when the LEI resolves, and security FIGI from OpenFIGI when a ticker is implied; every identifier is labelled with the source that established it, and an identifier that could NOT be resolved is stated explicitly under `unresolved` rather than omitted — accepts ticker, CIK, or company name as input), "drug" (returns RxCUI + ingredient + brand from RxNorm + pipeworx://rxnorm/concept/{rxcui} citation; accepts brand or generic name). LEI/FIGI enrichment degrades gracefully — if GLEIF or OpenFIGI is unavailable, the EDGAR identifiers still return. Each call cascades through several lookup endpoints internally — using resolve_entity replaces 2-3 manual lookups.Connector
- Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. Call with NO args for a `trending_scan` of the top ~200 markets by weekly volume; pass `event` for the strongest per-event partition_check, or `topic` for a themed cross-event scan. `event` (recommended for a specific market): pass a Polymarket event slug like "fed-decision-may-2026" or "when-will-bitcoin-hit-150k"; walks child markets, checks date-axis / threshold-axis ordering AND computes the partition_check (sum of YES prices across mutually-exclusive legs — should ≈1; deviations >3pp emit a BUY/SELL EVERY LEG signal). `topic` (for cross-event scanning): pass a seed question like "Strait of Hormuz traffic returns to normal" or "Fed rate decision"; searches related events across the platform, flattens markets, runs the comparator on the union. Cross-event mode catches "...by May 31" vs "...by Jun 30" patterns that single-event misses. SEMANTIC ANCHOR: cross-event pairs require ≥0.30 Jaccard similarity on question tokens (prevents Powell-Fed-Pause being paired with Powell-DOJ-probe); skipped_low_similarity surfaces the rejected pair count. PARTITION FILTER: drops will-person-X / will-manager-Y / will-someone-else- placeholder slugs; partitions with >20% placeholder fraction return null arb signal. Response: opportunities[] (gap_pp, suggested_trade, reasoning, monotonicity violation context), and in event mode partition_check{sum_yes_prices, gap_from_1, placeholders_filtered, suggested_trade}. FILL CHECK: when the partition signal fires, arbitrage.fill_check prices it against live CLOB depth (theoretical_edge_pp_at_book vs realizable_edge_pp at 1000 shares/leg, thin_legs[]) — realizable_edge_pp ≤ 0 means the overround exists only at last-trade, not in the book; do not trade it. For custom sizing use polymarket_fill_risk.Connector