# Db Rail (npm · @pipeworx/mcp-db-rail)

DB Rail MCP — German + European rail and public transport, keyless.

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

## Components

- remote · `gateway.pipeworx.io`: 63/100, [markdown](https://verifymcp.io/servers/pipeworx-io-db-rail/db-rail-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-db-rail/db-rail-mcp)
- npm · `@pipeworx/mcp-db-rail`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-db-rail/pipeworx-mcp-db-rail.md), [page](https://verifymcp.io/servers/pipeworx-io-db-rail/pipeworx-mcp-db-rail)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-db-rail`
- Version: `0.2.1`
- 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-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-db-rail).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 861 tokens (~215/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Db Rail MCP server?

Db Rail runs locally as an npm package, launched with npx -y @pipeworx/mcp-db-rail. 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 pipeworx-io-db-rail -- npx -y @pipeworx/mcp-db-rail
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-db-rail": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-db-rail"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-db-rail": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-db-rail"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-db-rail -- npx -y @pipeworx/mcp-db-rail
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-db-rail": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-db-rail"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-db-rail --command npx --arg -y --arg @pipeworx/mcp-db-rail
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-db-rail:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-db-rail"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-db-rail": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-db-rail"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-db-rail -t stdio -c npx -a -y @pipeworx/mcp-db-rail
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-db-rail": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-db-rail"
      ]
    }
  }
}
```

## 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-04 (score 82, +1)

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

### 2026-11-01 (score 81, +2)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (4)

### `dbrail_locations` (~157 tokens)

Search German / European rail stations, stops, and places by name (e.g. "Berlin Hbf", "München", "Zürich HB"). Returns matches with a stop id, coordinates, and country. Keyless. You do NOT have to call this first — dbrail_departures, dbrail_arrivals and dbrail_journeys all accept a plain station name and resolve it themselves; use this when you want to disambiguate between similarly-named stations or need coordinates.

Input parameters:

- `query` (string, required): Search term, e.g. "Berlin Hbf", "Hamburg", "Wien Hauptbahnhof".
- `results` (number): Max results to return (default 10, max 25).

### `dbrail_departures` (~241 tokens)

Live departures board for a German / European station. Pass a station NAME ("Berlin Hbf") or a stop id from dbrail_locations. Returns upcoming departures with line/train number, destination, scheduled and real-time departure, delay in minutes, platform/track, and operator. Keyless, real-time where the operator publishes it.

Input parameters:

- `id` (string, required): Station name ("Berlin Hbf") or stop id from dbrail_locations.
- `mode` (string): Filter by transport mode. Pass "rail" for trains only (high-speed, long-distance, night, regional) — recommended at big stations, where trams/buses otherwise dominate the board. Or pass explicit MOTI…
- `results` (number): Max departures to return (default 15, max 50).
- `when` (string): ISO date/time to start the board from (e.g. "2026-07-25T18:00:00Z"). Defaults to now.

### `dbrail_arrivals` (~227 tokens)

Live arrivals board for a German / European station. Pass a station NAME ("München Hbf") or a stop id from dbrail_locations. Returns upcoming arrivals with line/train number, origin, scheduled and real-time arrival, delay in minutes, platform/track, and operator. Keyless, real-time where the operator publishes it.

Input parameters:

- `id` (string, required): Station name ("München Hbf") or stop id from dbrail_locations.
- `mode` (string): Filter by transport mode. Pass "rail" for trains only (high-speed, long-distance, night, regional) — recommended at big stations, where trams/buses otherwise dominate the board. Or pass explicit MOTI…
- `results` (number): Max arrivals to return (default 15, max 50).
- `when` (string): ISO date/time to start the board from. Defaults to now.

### `dbrail_journeys` (~182 tokens)

Plan a multi-leg rail / public-transport journey between two places in Europe. Pass station NAMES ("Berlin Hbf" -> "München Hbf") or stop ids. Returns route options, each with total duration, number of transfers, and every leg (mode, line, from/to with platforms, scheduled + real-time times). Keyless.

Input parameters:

- `departure` (string): ISO date/time to depart at (e.g. "2026-07-25T18:00:00Z"). Defaults to now.
- `from` (string, required): Origin station name or stop id, e.g. "Berlin Hbf".
- `results` (number): Max journey options to return (default 3, max 6).
- `to` (string, required): Destination station name or stop id, e.g. "München Hbf".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-db-rail/pipeworx-mcp-db-rail#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Db Rail MCP server?

Db Rail is an MCP server listed in the public MCP registry as io.github.pipeworx-io/db-rail. DB Rail MCP, German + European rail and public transport, keyless. This page covers its npm package (@pipeworx/mcp-db-rail).

### Is the Db Rail MCP server safe to use?

Db Rail scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 Db Rail MCP server expose?

Db Rail exposes 4 tools: dbrail_locations, dbrail_departures, dbrail_arrivals, dbrail_journeys. Their descriptions and schemas cost roughly 807 tokens of context every time the server is loaded.

### Is the Db Rail MCP server still maintained?

Db Rail is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Db Rail MCP server under?

Db Rail declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Db Rail MCP server?

VerifyMCP ran 16 checks on Db Rail, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-db-rail
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-db-rail
- Repository: https://github.com/pipeworx-io/mcp-db-rail
- Website: https://pipeworx.io/packs/db-rail
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-db-rail/pipeworx-mcp-db-rail.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-db-rail/pipeworx-mcp-db-rail/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-db-rail/pipeworx-mcp-db-rail.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-db-rail/pipeworx-mcp-db-rail