# Rhein-Ruhr Fahrplan MCP (pypi · rhein-ruhr-fahrplan-mcp)

Public transit data for the Rhein-Ruhr region: live departures, trips, disruptions, GTFS schedules.

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- pypi · `rhein-ruhr-fahrplan-mcp`: 82/100 (this document), [markdown](https://verifymcp.io/servers/marcproe-rhein-ruhr-fahrplan-mcp/rhein-ruhr-fahrplan-mcp.md), [page](https://verifymcp.io/servers/marcproe-rhein-ruhr-fahrplan-mcp/rhein-ruhr-fahrplan-mcp)

## Channel facts

- Registry: `pypi`
- Package: `rhein-ruhr-fahrplan-mcp`
- Version: `1.2.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-24.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 15 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to MarcProe/rhein-ruhr-fahrplan-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 17 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 871 tokens (~96/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add marcproe-rhein-ruhr-fahrplan-mcp -- uvx rhein-ruhr-fahrplan-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "marcproe-rhein-ruhr-fahrplan-mcp": {
      "command": "uvx",
      "args": [
        "rhein-ruhr-fahrplan-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "marcproe-rhein-ruhr-fahrplan-mcp": {
      "command": "uvx",
      "args": [
        "rhein-ruhr-fahrplan-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add marcproe-rhein-ruhr-fahrplan-mcp -- uvx rhein-ruhr-fahrplan-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "marcproe-rhein-ruhr-fahrplan-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "rhein-ruhr-fahrplan-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add marcproe-rhein-ruhr-fahrplan-mcp --command uvx --arg rhein-ruhr-fahrplan-mcp
```

### Hermes

```yaml
mcp_servers:
  marcproe-rhein-ruhr-fahrplan-mcp:
    command: "uvx"
    args: ["rhein-ruhr-fahrplan-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "marcproe-rhein-ruhr-fahrplan-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "rhein-ruhr-fahrplan-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add marcproe-rhein-ruhr-fahrplan-mcp -t stdio -c uvx -a rhein-ruhr-fahrplan-mcp
```

### Other

```json
{
  "mcpServers": {
    "marcproe-rhein-ruhr-fahrplan-mcp": {
      "command": "uvx",
      "args": [
        "rhein-ruhr-fahrplan-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 82, +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.

### 2026-10-21 (score 81, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-10-14 (score 78, +29)

- [security improvement] 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).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] 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

### 2026-10-12 (score 49, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-08 (score 34)

First indexed and scored.

## MCP tools (9)

### `find_stop` (~113 tokens)

Find Stop

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.

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `get_default_start` (~99 tokens)

Get Default Start

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.

### `next_departures` (~104 tokens)

Next Departures

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.

Input parameters:

- `limit` (integer)
- `stop_ref` (string, required)

### `next_arrivals` (~54 tokens)

Next Arrivals

Live-Ankünfte einer Haltestelle mit Echtzeitprognose.

stop_ref: DHID (empfohlen), stop_id oder exakter Name.

Input parameters:

- `limit` (integer)
- `stop_ref` (string, required)

### `stop_schedule` (~104 tokens)

Stop Schedule

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.

Input parameters:

- `day_offset` (integer)
- `limit` (integer)
- `stop_ref` (string, required)

### `plan_connection` (~114 tokens)

Plan Connection

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).

Input parameters:

- `departure_time`
- `destination_ref` (string, required)
- `max_results` (integer)
- `origin_ref` (string, required)

### `line_disruptions` (~77 tokens)

Line Disruptions

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.

Input parameters:

- `line`
- `stop_ref` (string, required)

### `sync_status` (~27 tokens)

Sync Status

Status des GTFS-Imports: Feed-Version, Gültigkeit, Zeilenzahlen.

### `update_feed` (~90 tokens)

Update Feed

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).

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/marcproe-rhein-ruhr-fahrplan-mcp/rhein-ruhr-fahrplan-mcp#diagnostics

## Score history

- 2026-10-24: 82
- 2026-10-23: 82
- 2026-10-22: 81
- 2026-10-21: 81
- 2026-10-20: 78
- 2026-10-19: 78
- 2026-10-18: 78
- 2026-10-17: 78
- 2026-10-16: 78
- 2026-10-15: 78
- 2026-10-14: 78
- 2026-10-13: 49
- 2026-10-12: 49
- 2026-10-08: 34

## Common questions

### 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.

## Links

- PyPI project: https://pypi.org/project/rhein-ruhr-fahrplan-mcp/
- Socket report: https://socket.dev/pypi/package/rhein-ruhr-fahrplan-mcp
- Repository: https://github.com/MarcProe/rhein-ruhr-fahrplan-mcp
- Changelog RSS feed: https://verifymcp.io/servers/marcproe-rhein-ruhr-fahrplan-mcp/rhein-ruhr-fahrplan-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/marcproe-rhein-ruhr-fahrplan-mcp/rhein-ruhr-fahrplan-mcp.json
- HTML version of this page: https://verifymcp.io/servers/marcproe-rhein-ruhr-fahrplan-mcp/rhein-ruhr-fahrplan-mcp