Rhein-Ruhr Fahrplan MCP
PYPI · RHEIN-RUHR-FAHRPLAN-MCP
Public transit data for the Rhein-Ruhr region: live departures, trips, disruptions, GTFS schedules.
Available components
Last scanned (17 hours ago)
Scores higher than 82% of PyPI servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 15 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to MarcProe/rhein-ruhr-fahrplan-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 17 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 871 tokens (~96/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +3
- Stability: unverified → 0.23 ▲ functional
- 14 Oct 26 +29
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 12 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 8 Oct 26 34
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Analysed pypi/rhein-ruhr-fahrplan-mcp@1.2.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | MarcProe/rhein-ruhr-fahrplan-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/MarcProe/rhein-ruhr-fahrplan-mcp/.github/workflows/publish.yml@refs/tags/v1.2.2 |
| Rekor log index | 3109689215 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:58dcef5a8a325c7e8dc86b9eda6781255ec42bbe91936cec782d6d615131615e |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 15 packages
| Packages resolved | 15 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_stop Find Stop ~113
Haltestelle im Rhein-Ruhr-Gebiet finden (GTFS-Index; Live-Fallback EFA). Liefert stop_id, Name, DHID (globale ID), Koordinaten und ggf. Steig-Details. Der GTFS-Index enthält nur Haltestellen der konfigurierten Verkehrsunternehmen (FAHRPLAN_AGENCY_IDS); unbekannte Haltestellen werden live über die EFA gesucht.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_default_start Get Default Start ~99
Konfigurierte Standard-Start-Haltestelle abrufen (FAHRPLAN_DEFAULT_START). Löst die konfigurierte Angabe (DHID, EFA-ID oder Name) auf und liefert die kanonische DHID plus Name. Die aufgelöste Haltestelle kann direkt für next_departures, stop_schedule oder als origin in plan_connection verwendet werden. Ohne gesetzte FAHRPLAN_DEFAULT_START: Hinweis mit Anleitung.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
line_disruptions Line Disruptions ~77
Aktuelle Störungen/Hinweise an einer Haltestelle (und optional Linie). Nutzt die in den Live-Abfahrten eingebetteten EFA-infos (Bauarbeiten, Umleitungen, Haltestellenverlegungen). line schränkt optional ein.
| Name | Type | Req | Description |
|---|---|---|---|
| line | – | – | – |
| stop_ref | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
next_arrivals Next Arrivals ~54
Live-Ankünfte einer Haltestelle mit Echtzeitprognose. stop_ref: DHID (empfohlen), stop_id oder exakter Name.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| stop_ref | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
next_departures Next Departures ~104
Live-Abfahrten einer Haltestelle mit Echtzeitprognose. stop_ref: DHID (empfohlen), stop_id oder exakter Name. Liefert Linie, Richtung, Soll- und Prognosezeit, Verspätung in Minuten, Steig und aktuelle Störungshinweise. Mit gesetztem FAHRPLAN_OPERATOR werden nur Fahrten dieses Unternehmens geliefert, sonst alle.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| stop_ref | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
plan_connection Plan Connection ~114
Verbindung von A nach B planen (EFA TripRequest, ganzes Rhein-Ruhr-Gebiet). origin/destination: DHID oder exakter Haltestellenname. departure_time optional 'YYYY-MM-DD HH:MM'. Mit gesetztem FAHRPLAN_OPERATOR werden Verbindungen mit Legs dieses Unternehmens bevorzugt (hart filtern kann EFA nicht).
| Name | Type | Req | Description |
|---|---|---|---|
| departure_time | – | – | – |
| destination_ref | string | yes | – |
| max_results | integer | – | – |
| origin_ref | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
stop_schedule Stop Schedule ~104
Sollfahrplan aus dem GTFS-Feed: nächste geplante Abfahrten. stop_ref: DHID oder stop_id aus der Datenbank. day_offset: 0=heute, 1=morgen, -1=gestern. Nutzt den lokalen Feed (monatlich aktualisiert), keine Echtzeit – für Prognosen next_departures verwenden.
| Name | Type | Req | Description |
|---|---|---|---|
| day_offset | integer | – | – |
| limit | integer | – | – |
| stop_ref | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
sync_status Sync Status ~27
Status des GTFS-Imports: Feed-Version, Gültigkeit, Zeilenzahlen.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
update_feed Update Feed ~90
GTFS-Feed aktualisieren: CKAN prüfen, nur bei neuer Ressource importieren. Manueller Trigger des Automatismus (Der Server prüft auch selbst alle FAHRPLAN_FEED_CHECK_INTERVAL Sekunden). Idempotent: Bei aktuellem Feed passiert nichts. Bei neuer Ressource: Download + Import, ~1–2 Minuten (je nach Anzahl konfigurierter Unternehmen).
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Rhein-Ruhr Fahrplan MCP server?
Rhein-Ruhr Fahrplan MCP runs locally as a PyPI package, launched with uvx rhein-ruhr-fahrplan-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · rhein-ruhr-fahrplan-mcp
claude mcp add marcproe-rhein-ruhr-fahrplan-mcp -- uvx rhein-ruhr-fahrplan-mcp
What is the Rhein-Ruhr Fahrplan MCP server?
Rhein-Ruhr Fahrplan MCP is listed in the public MCP registry as io.github.MarcProe/rhein-ruhr-fahrplan-mcp. Public transit data for the Rhein-Ruhr region: live departures, trips, disruptions, GTFS schedules. This page covers its PyPI package (rhein-ruhr-fahrplan-mcp).
Is the Rhein-Ruhr Fahrplan MCP server safe to use?
Rhein-Ruhr Fahrplan MCP scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 October 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Rhein-Ruhr Fahrplan MCP server expose?
Rhein-Ruhr Fahrplan MCP exposes 9 tools: find_stop, get_default_start, next_departures, next_arrivals, stop_schedule, and 4 more. Their descriptions and schemas cost roughly 782 tokens of context every time the server is loaded.
Is the Rhein-Ruhr Fahrplan MCP server still maintained?
Rhein-Ruhr Fahrplan MCP is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Rhein-Ruhr Fahrplan MCP server under?
Rhein-Ruhr Fahrplan MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.