# Bahn Transfer (remote · bahn.1f916.de)

Re-plan a delayed rail journey: onward options, transfer buffers, one recommendation

- Trust score: 66/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `bahn.1f916.de`: 66/100 (this document), [markdown](https://verifymcp.io/servers/citizen01-sid-bahn-transfer/bahn.md), [page](https://verifymcp.io/servers/citizen01-sid-bahn-transfer/bahn)

## Channel facts

- Endpoint: `https://bahn.1f916.de/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 593 tokens (~197/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "plan_transfer" implies "transfer" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Bahn Transfer MCP server?

Bahn Transfer is a hosted endpoint at https://bahn.1f916.de/mcp, so there is nothing to install locally. 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 --transport http citizen01-sid-bahn-transfer 'https://bahn.1f916.de/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "citizen01-sid-bahn-transfer": {
      "url": "https://bahn.1f916.de/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "citizen01-sid-bahn-transfer": {
      "type": "http",
      "url": "https://bahn.1f916.de/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.citizen01-sid-bahn-transfer]
url = "https://bahn.1f916.de/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "citizen01-sid-bahn-transfer": {
      "type": "remote",
      "url": "https://bahn.1f916.de/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add citizen01-sid-bahn-transfer --url 'https://bahn.1f916.de/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  citizen01-sid-bahn-transfer:
    url: "https://bahn.1f916.de/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "citizen01-sid-bahn-transfer": {
      "Transport": "http",
      "Url": "https://bahn.1f916.de/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add citizen01-sid-bahn-transfer -t streamable-http -u 'https://bahn.1f916.de/mcp'
```

### Other

```json
{
  "mcpServers": {
    "citizen01-sid-bahn-transfer": {
      "type": "http",
      "url": "https://bahn.1f916.de/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-21 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 64, 0)

- [security] Tool “search_stations” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 143 → 197
- [cosmetic] “departures” reworded the description of “station”
- [cosmetic] “plan_transfer” reworded the description of “to”

### 2026-11-15 (score 64, +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-11-13 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 62, 0)

- [security] Tool “departures” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail

### 2026-11-10 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `search_stations` (~153 tokens)

Free. Resolve a station or city name to a stop_id. A bare city name resolves to that city's main rail hub only when exactly one candidate exists; the answer then carries a 'resolution' object naming the rule, the chosen station and the rejected alternatives. Use the returned stop_id as 'to' in plan_transfer. Every id-like field in a result carries an 'accepted_by' block saying whether it is valid as a station argument — read it instead of guessing: the 'eva' field is a station identifier, NOT a stop id, and is rejected by departures.

Input parameters:

- `limit` (integer)
- `q` (string, required): Station or city name, e.g. 'Leipzig Hbf'.

### `departures` (~188 tokens)

Free. Upcoming departures at a stop_id, with trip_id, line, scheduled/actual time, current delay and per-row 'delay_source'. Use trip_id as 'trip_id' in plan_transfer for the train the traveller is already on. Read delay_source before reading delay_minutes: 'realtime' means the times are live, so 0 is on time; 'scheduled' means timetable only, so 0 means NOT MEASURED.

Input parameters:

- `limit` (integer)
- `station` (string, required): A station id from search_stations. Accepts `stop_id` (the stop_id field from search_stations) or `provider_stop_id` (the provider_stop_id field from search_stations). NOT accepted: the eva field (an…

### `plan_transfer` (~177 tokens)

PAID (x402 exact/EVM, 1 USDC-cent per call). Re-plan a journey for a traveller already on a delayed train: per-stop transfer buffer, onward connections with arrival times, and one safe recommendation. Call it without payment to receive the PaymentRequired object; retry with the payment payload in params._meta['x402/payment'].

Input parameters:

- `manual_delay` (integer): Known delay in minutes, if the feed has none.
- `min_buffer` (integer): Minimum transfer buffer in minutes.
- `to` (string, required): Destination station id from search_stations. Accepts `stop_id` (the stop_id field from search_stations) or `provider_stop_id` (the provider_stop_id field from search_stations). The eva field is NOT a…
- `trip_id` (string, required): trip_id from departures.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/citizen01-sid-bahn-transfer/bahn#diagnostics

## Score history

- 2026-11-21: 66
- 2026-11-20: 65
- 2026-11-19: 65
- 2026-11-18: 64
- 2026-11-17: 64
- 2026-11-16: 64
- 2026-11-15: 64
- 2026-11-14: 63
- 2026-11-13: 63
- 2026-11-12: 62
- 2026-11-11: 62
- 2026-11-10: 62
- 2026-11-09: 61
- 2026-11-08: 61
- 2026-11-07: 60
- 2026-11-06: 60

## Common questions

### What is the Bahn Transfer MCP server?

Bahn Transfer is an MCP server listed in the public MCP registry as io.github.citizen01-sid/bahn-transfer. Re-plan a delayed rail journey: onward options, transfer buffers, one recommendation. This page covers its hosted endpoint (https://bahn.1f916.de/mcp).

### Is the Bahn Transfer MCP server safe to use?

Bahn Transfer scores 66 out of 100 on VerifyMCP. 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 Bahn Transfer MCP server expose?

Bahn Transfer exposes 3 tools: search_stations, departures, plan_transfer. Their descriptions and schemas cost roughly 518 tokens of context every time the server is loaded.

### Does the Bahn Transfer MCP server require authentication?

No. We connected to Bahn Transfer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Bahn Transfer MCP server still maintained?

Bahn Transfer is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Bahn Transfer MCP server?

VerifyMCP ran 12 checks on Bahn Transfer, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Bahn Transfer: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://bahn.1f916.de/mcp
- Website: https://bahn.1f916.de/
- Changelog RSS feed: https://verifymcp.io/servers/citizen01-sid-bahn-transfer/bahn.xml
- Changelog JSON feed: https://verifymcp.io/servers/citizen01-sid-bahn-transfer/bahn/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/citizen01-sid-bahn-transfer/bahn.json
- HTML version of this page: https://verifymcp.io/servers/citizen01-sid-bahn-transfer/bahn
