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.

RZD Tickets MCP

NPM · MCP-RZD-TICKETS

Read-only MCP server for RZD trains, cars, seats, adjacent pairs and car photos.

Available components

0 this week 83 Trust /100

Last scanned (20 hours ago)

Scores higher than 73% 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 Security98
  • 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
  • 36 of 103 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 141 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1202 tokens (~171/item across 7 items; 7 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 98% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
What we tested

Checks we ran (16)

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

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.

  • 19 Nov 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → pass ▲ functional
  • 18 Nov 26 −1
    • Security disclosure: pass → unverified ▼ functional
    • Stability: pass → 0.97 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → pass ▲ functional
  • 11 Nov 26 0
    • Security disclosure: pass → unverified ▼ functional
  • 10 Nov 26 +1

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

  • 8 Nov 26 −2
    • Stability: pass → 0.87 functional
  • 2 Nov 26 +1
    • Stability: 0.97 → pass security
  • 1 Nov 26 −1
    • Stability: pass → 0.97 functional
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/mcp-rzd-tickets@0.1.2

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 103 packages
Packages resolved 103
Deprecated 1
Stale 35
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~1,202 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
rzd_checkout_url ~152

Build the official RZD search/checkout handoff URL. This tool does not book or pay.

NameTypeReqDescription
adultsinteger–Adult passengers.
childreninteger–Child passengers.
datestringyesTravel date in YYYY-MM-DD.
destinationstringyesRZD expressCode or nodeId of destination station.
destinationNodeIdstring–Optional nodeId for building checkout URL.
largeFamilyboolean–Search large-family availability.
originstringyesRZD expressCode or nodeId of origin station, e.g. 2038000 or 5a13...
originNodeIdstring–Optional nodeId for building checkout URL.

No output schema declared.

No examples provided.

rzd_find_places ~363

Search trains and return only matches by seat/car filters. Use requirePair=true for adjacent lower+upper places.

NameTypeReqDescription
adultsinteger–Adult passengers.
carTypestring–coupe, platz, or raw RZD car type text.
childreninteger–Child passengers.
datestringyesTravel date in YYYY-MM-DD.
departureFromstring–Local departure lower bound HH:mm.
departureTostring–Local departure upper bound HH:mm.
destinationstringyesRZD expressCode or nodeId of destination station.
destinationNodeIdstring–Optional nodeId for building checkout URL.
includeAccessibleboolean–Include disabled/special places.
includeImagesboolean–Fetch RZD car photo gallery URLs when CarPricing says HasImages=true.
includeSideboolean–Include side places.
largeFamilyboolean–Search large-family availability.
maxPricenumber–Maximum price in RUB.
minPlacesinteger–Minimum places in a car row.
originstringyesRZD expressCode or nodeId of origin station, e.g. 2038000 or 5a13...
originNodeIdstring–Optional nodeId for building checkout URL.
placeKindstring–Seat kind filter.
requirePairboolean–Return only adjacent lower+upper pairs.
servicestring–Raw RZD service class code, e.g. 2К, 2А, 2Ш. The code set is open-ended.
trainstring–Single exact train number.
trainsarray–Exact train numbers, e.g. ["097Э"].

No output schema declared.

No examples provided.

rzd_parse_search_url ~36

Extract route nodeIds, date and passengers from an official ticket.rzd.ru search URL.

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

rzd_search_trains ~207

Return train-level availability, prices, car groups and checkout URL for a route/date.

NameTypeReqDescription
adultsinteger–Adult passengers.
childreninteger–Child passengers.
datestringyesTravel date in YYYY-MM-DD.
departureFromstring–Local departure lower bound HH:mm.
departureTostring–Local departure upper bound HH:mm.
destinationstringyesRZD expressCode or nodeId of destination station.
destinationNodeIdstring–Optional nodeId for building checkout URL.
largeFamilyboolean–Search large-family availability.
originstringyesRZD expressCode or nodeId of origin station, e.g. 2038000 or 5a13...
originNodeIdstring–Optional nodeId for building checkout URL.
trainstring–Single exact train number.
trainsarray–Exact train numbers, e.g. ["097Э"].

No output schema declared.

No examples provided.

rzd_service_classes ~33

Explain how to read open-ended RZD ServiceClass codes. This is a decoding guide, not a closed enum.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

rzd_station_suggest ~46

Find RZD station nodeId and expressCode by station name.

NameTypeReqDescription
querystringyesStation name fragment, e.g. Красноярск or Анзеби.

No output schema declared.

No examples provided.

rzd_train_cars ~365

Drill into CarPricing for selected trains and return cars, seat stats, lower/upper places, and adjacent pairs.

NameTypeReqDescription
adultsinteger–Adult passengers.
carTypestring–coupe, platz, or raw RZD car type text.
childreninteger–Child passengers.
datestringyesTravel date in YYYY-MM-DD.
departureFromstring–Local departure lower bound HH:mm.
departureTostring–Local departure upper bound HH:mm.
destinationstringyesRZD expressCode or nodeId of destination station.
destinationNodeIdstring–Optional nodeId for building checkout URL.
includeAccessibleboolean–Include disabled/special places.
includeImagesboolean–Fetch RZD car photo gallery URLs when CarPricing says HasImages=true.
includeSideboolean–Include side places.
largeFamilyboolean–Search large-family availability.
maxPricenumber–Maximum price in RUB.
minPlacesinteger–Minimum places in a car row.
originstringyesRZD expressCode or nodeId of origin station, e.g. 2038000 or 5a13...
originNodeIdstring–Optional nodeId for building checkout URL.
placeKindstring–Seat kind filter.
requirePairboolean–Return only adjacent lower+upper pairs.
servicestring–Raw RZD service class code, e.g. 2К, 2А, 2Ш. The code set is open-ended.
trainstring–Single exact train number.
trainsarray–Exact train numbers, e.g. ["097Э"].

No output schema declared.

No examples provided.

Install

How do I install the RZD Tickets MCP server?

RZD Tickets MCP runs locally as an npm package, launched with npx -y mcp-rzd-tickets. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mcp-rzd-tickets

# add to Claude Code
claude mcp add ex3lite-mcp-rzd-tickets -- npx -y mcp-rzd-tickets
Common questions

What is the RZD Tickets MCP server?

RZD Tickets MCP is listed in the public MCP registry as io.github.ex3lite/mcp-rzd-tickets. Read-only MCP server for RZD trains, cars, seats, adjacent pairs and car photos. This page covers its npm package (mcp-rzd-tickets).

Is the RZD Tickets MCP server safe to use?

RZD Tickets MCP scores 83 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 RZD Tickets MCP server expose?

RZD Tickets MCP exposes 7 tools: rzd_station_suggest, rzd_search_trains, rzd_train_cars, rzd_find_places, rzd_checkout_url, and 2 more. Their descriptions and schemas cost roughly 1,202 tokens of context every time the server is loaded.

Is the RZD Tickets MCP server still maintained?

RZD Tickets MCP 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 RZD Tickets MCP server under?

RZD Tickets 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.

What did VerifyMCP test on the RZD Tickets MCP server?

VerifyMCP ran 16 checks on RZD Tickets MCP, 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.