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.

cn.pianam/12306-train-mcp

REMOTE · PIANAM.CN

MCP server for China Railway 12306 ticket availability: schedules and seats by Chinese station name.

Available components

+6 this week 74 Trust /100

Last scanned (14 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability83
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 179 tokens (~89/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • 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 hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1

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

  • 15 Nov 26 +3
    • HSTS header: unverified → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
  • 14 Nov 26 −2
    • Injection markers: unverified → pass ▲ security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.17 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 13 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: 0.10 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 12 Nov 26 +1

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

  • 10 Nov 26 +1
    • Stability: unverified → 0.03 ▲ 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 · Probed https://pianam.cn/train-mcp/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pianam.cn CN=YR1,O=Let's Encrypt,C=US 11 Nov 2026 9 Feb 2027 RSA 2048 SHA256-RSA 52faeb2a8c950aa4b834de3ec969b579723
SANs: pianam.cn, www.pianam.cn
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of pianam.cn. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
cn. DS published 33094 8 Verified
pianam.cn. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pianam.cn/train-mcp/mcp Verified 200
http (plaintext) http://pianam.cn/train-mcp/mcp HTTPS enforced 301 https://pianam.cn/train-mcp/mcp
MCP tools · 2 exposed · ~179 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
query_train_tickets ~131

查询中国大陆12306火车票余票信息。参数from_city出发城市/车站中文名,to_city到达城市/车站中文名,date出发日期格式YYYY-MM-DD;留空默认明天。

NameTypeReqDescription
datestring–出发日期,格式 YYYY-MM-DD;留空默认明天
from_citystringyes出发城市或车站中文名,如 "青岛"、"北京南"
to_citystringyes到达城市或车站中文名,如 "北京"、"上海虹桥"

Structured output declared, but exposes no named fields.

No examples provided.

search_station ~48

按关键词搜索12306车站名称,返回匹配的车站中文名列表。不确定城市有哪些车站时使用。

NameTypeReqDescription
keywordstringyes关键词,如 "北京"

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the cn.pianam/12306-train-mcp server?

cn.pianam/12306-train-mcp is a hosted endpoint at https://pianam.cn/train-mcp/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.

remote · pianam.cn

# add to Claude Code
claude mcp add --transport http cn-pianam-12306-train-mcp 'https://pianam.cn/train-mcp/mcp'
Common questions

What is the cn.pianam/12306-train-mcp server?

cn.pianam/12306-train-mcp is listed in the public MCP registry as cn.pianam/12306-train-mcp. MCP server for China Railway 12306 ticket availability: schedules and seats by Chinese station name. This page covers its hosted endpoint (https://pianam.cn/train-mcp/mcp).

Is the cn.pianam/12306-train-mcp server safe to use?

cn.pianam/12306-train-mcp scores 74 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 cn.pianam/12306-train-mcp server expose?

cn.pianam/12306-train-mcp exposes 2 tools: query_train_tickets, search_station. Their descriptions and schemas cost roughly 179 tokens of context every time the server is loaded.

Does the cn.pianam/12306-train-mcp server require authentication?

No. We connected to cn.pianam/12306-train-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the cn.pianam/12306-train-mcp server still maintained?

cn.pianam/12306-train-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 did VerifyMCP test on the cn.pianam/12306-train-mcp server?

VerifyMCP ran 12 checks on cn.pianam/12306-train-mcp, 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 cn.pianam/12306-train-mcp: 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.