# Odpt (npm · @pipeworx/mcp-odpt)

ODPT — Japan rail timetables and live train/service status (Public Transportation Open Data Center).

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `gateway.pipeworx.io`: 64/100, [markdown](https://verifymcp.io/servers/pipeworx-io-odpt/odpt-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-odpt/odpt-mcp)
- npm · `@pipeworx/mcp-odpt`: 68/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-odpt/pipeworx-mcp-odpt.md), [page](https://verifymcp.io/servers/pipeworx-io-odpt/pipeworx-mcp-odpt)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-odpt`
- Version: `0.1.0`
- 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-21.

- **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**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1063 tokens (~265/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**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Odpt MCP server?

Odpt runs locally as an npm package, launched with npx -y @pipeworx/mcp-odpt. 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-odpt -- npx -y @pipeworx/mcp-odpt
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-16 (score 68, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-15 (score 53)

First indexed and scored.

## MCP tools (4)

### `odpt_resolve_station` (~287 tokens)

Find a Japan train station by name, in English or Japanese ("Shinjuku" or "新宿"), and return its ODPT station id(s), operator, railway and coordinates — for looking up Japanese railway/metro stations (Tokyo Metro, JR East, Toei and other operators). ODPT has no name-search endpoint, so this fetches station master data for the given operator (or a short list of major Tokyo operators if none is given) and matches client-side — one station can have several ids, one per operator/railway that serves it. Use the returned station_id with odpt_station_timetable. Needs an ODPT developer consumer key via _apiKey; Pipeworx supplies one if omitted. Example: odpt_resolve_station({ query: "Shinjuku" }).

Input parameters:

- `_apiKey` (string, required): Optional: your own ODPT developer consumer key. Pipeworx supplies one if omitted.
- `limit` (number): Max matches to return, 1-50. Default 10.
- `operator` (string): Limit to one operator, e.g. "Tokyo Metro", "JR East", "Toei", or an exact odpt.Operator id. Default: searches several major Tokyo operators.
- `query` (string, required): Station name in English or Japanese, e.g. "Shinjuku" or "新宿".

### `odpt_station_timetable` (~280 tokens)

Scheduled departure timetable at a Japanese train station (Tokyo Metro, JR East, Toei and other Japan railway operators): destination, departure time, train type and direction, for weekday/Saturday/holiday calendars. Resolve the station first with odpt_resolve_station to get its exact station_id (or pass a plain station name and this will resolve it for you, taking the first match). Needs an ODPT developer consumer key via _apiKey; Pipeworx supplies one if omitted. Example: odpt_station_timetable({ station: "Shinjuku", operator: "Tokyo Metro" }).

Input parameters:

- `_apiKey` (string, required): Optional: your own ODPT developer consumer key. Pipeworx supplies one if omitted.
- `calendar` (string): Optional: keep only this calendar, e.g. "odpt.Calendar:Weekday" or "odpt.Calendar:SaturdayHoliday".
- `operator` (string): Operator to search when `station` is a plain name and could match more than one operator, e.g. "Tokyo Metro".
- `railway` (string): Optional: keep only this railway, e.g. "odpt.Railway:TokyoMetro.Marunouchi".
- `station` (string, required): Station name (English or Japanese) or an exact odpt.Station id from odpt_resolve_station.

### `odpt_train_timetable` (~217 tokens)

Stop-by-stop scheduled timetable for one specific Japanese train run, by railway and train number: every station it calls at with arrival/departure time. Covers Tokyo Metro, JR East, Toei and other Japan railway operators. Train numbers come from odpt_station_timetable rows. Needs an ODPT developer consumer key via _apiKey; Pipeworx supplies one if omitted. Example: odpt_train_timetable({ railway: "odpt.Railway:JR-East.Yamanote", train_number: "1234G" }).

Input parameters:

- `_apiKey` (string, required): Optional: your own ODPT developer consumer key. Pipeworx supplies one if omitted.
- `railway` (string, required): Exact odpt.Railway id, e.g. "odpt.Railway:JR-East.Yamanote" or "odpt.Railway:TokyoMetro.Marunouchi".
- `train_number` (string, required): The train number as shown in a station timetable row, e.g. "1234G".

### `odpt_service_status` (~226 tokens)

Live service status (current train information) for a Japanese railway line: normal operation, delays, or suspension, with the operator's own status text in Japanese and English and when it was last updated. Covers Tokyo Metro, JR East, Toei and other Japan railway operators publishing to ODPT. Needs an ODPT developer consumer key via _apiKey; Pipeworx supplies one if omitted. Example: odpt_service_status({ railway: "Yamanote", operator: "JR East" }).

Input parameters:

- `_apiKey` (string, required): Optional: your own ODPT developer consumer key. Pipeworx supplies one if omitted.
- `operator` (string, required): Operator, e.g. "Tokyo Metro", "JR East", "Toei", or an exact odpt.Operator id. Required if railway is not an exact id.
- `railway` (string): Railway/line name (e.g. "Yamanote", "Marunouchi") or an exact odpt.Railway id. Optional if operator is given — returns all of that operator's lines.

## Diagnostics

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

## Score history

- 2026-11-21: 68
- 2026-11-20: 68
- 2026-11-19: 68
- 2026-11-18: 68
- 2026-11-17: 68
- 2026-11-16: 68
- 2026-11-15: 53

## Common questions

### What is the Odpt MCP server?

Odpt is an MCP server listed in the public MCP registry as io.github.pipeworx-io/odpt. ODPT, Japan rail timetables and live train/service status (Public Transportation Open Data Center). This page covers its npm package (@pipeworx/mcp-odpt).

### Is the Odpt MCP server safe to use?

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

Odpt exposes 4 tools: odpt_resolve_station, odpt_station_timetable, odpt_train_timetable, odpt_service_status. Their descriptions and schemas cost roughly 1,010 tokens of context every time the server is loaded.

### Is the Odpt MCP server still maintained?

Odpt 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 licence is the Odpt MCP server under?

Odpt 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 Odpt MCP server?

VerifyMCP ran 15 checks on Odpt, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Odpt: Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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-odpt
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-odpt
- Repository: https://github.com/pipeworx-io/mcp-odpt
- Website: https://pipeworx.io/packs/odpt
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-odpt/pipeworx-mcp-odpt.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-odpt/pipeworx-mcp-odpt/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-odpt/pipeworx-mcp-odpt.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-odpt/pipeworx-mcp-odpt
