Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Odpt

NPM · @PIPEWORX/MCP-ODPT · 2 COMPONENTS

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

68 Trust /100

Last scanned (18 hours ago)

Scores higher than 39% of npm servers

Category Maps and Location

Trust breakdown (7 categories)

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
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 16 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Nov 26 53

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed npm/@pipeworx/mcp-odpt@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~1,010 tokens

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 →

Tool Tokens
odpt_resolve_station ~287

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

NameTypeReqDescription
_apiKeystringyesOptional: your own ODPT developer consumer key. Pipeworx supplies one if omitted.
limitnumber–Max matches to return, 1-50. Default 10.
operatorstring–Limit to one operator, e.g. "Tokyo Metro", "JR East", "Toei", or an exact odpt.Operator id. Default: searches several major Tokyo operators.
querystringyesStation name in English or Japanese, e.g. "Shinjuku" or "新宿".

No output schema declared.

No examples provided.

odpt_service_status ~226

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

NameTypeReqDescription
_apiKeystringyesOptional: your own ODPT developer consumer key. Pipeworx supplies one if omitted.
operatorstringyesOperator, e.g. "Tokyo Metro", "JR East", "Toei", or an exact odpt.Operator id. Required if railway is not an exact id.
railwaystring–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.

No output schema declared.

No examples provided.

odpt_station_timetable ~280

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

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

No output schema declared.

No examples provided.

odpt_train_timetable ~217

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

NameTypeReqDescription
_apiKeystringyesOptional: your own ODPT developer consumer key. Pipeworx supplies one if omitted.
railwaystringyesExact odpt.Railway id, e.g. "odpt.Railway:JR-East.Yamanote" or "odpt.Railway:TokyoMetro.Marunouchi".
train_numberstringyesThe train number as shown in a station timetable row, e.g. "1234G".

No output schema declared.

No examples provided.

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.

npm · @pipeworx/mcp-odpt

# add to Claude Code
claude mcp add pipeworx-io-odpt -- npx -y @pipeworx/mcp-odpt
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.