MCP Server 12306
12306 MCP Server 是一个基于 Model Context Protocol (MCP) 的高性能火车票查询后端系统。它通过标准化接口提供官方 12306 的实时数据服务,包括余票查询、车站信息、列车经停站、中转换乘方案等核心功能。
Is MCP Server 12306 safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare MCP Server 12306
How does it stack up against its MCP Servers neighbours?
- Markifact: AI Performance Marketing +0.2 higher
- Synter Media AI MCP Server +0.2 higher
- SearXNG HTTP MCP 0.1 lower
In detail: MCP Server 12306 scores 49.0/100 (Grade D), ranked #1039 of 1387 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 1.9/10; 30% of recent commits are signed; no published advisory affects its latest release (mcp-server-12306); last pushed 2026-11-05. Every point is earned from checkable signals — never paid placement. How scoring works →
How MCP Server 12306 could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 1.9 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +14.9 → 63.9 C · #325 of 779
- Publish build provenance for its packagesPyPI Trusted Publishing attestations +14.7 → 63.7 C · #329 of 779
- Sign every commit30% signed today +3.5 → 52.5 C · #525 of 779
Chain of custody
Scanners check what the code says. This traces who ships MCP Server 12306 and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/drfccv/mcp-server-12306, MIT, last pushed 2026-11-05. 30% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Weak
OpenSSF Scorecard rates the repository's practices 1.9/10 (scanned Oct 31, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflown/a
- Token Permissionsn/a
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 0CI-Tests -1CII-Best-Practices 0Code-Review 0Contributors 0Dangerous-Workflow -1Dependency-Update-Tool 0Fuzzing 0License 10Maintained 5Packaging -1Pinned-Dependencies 0SAST 0Security-Policy 0Signed-Releases -1Token-Permissions -1Vulnerabilities 0 -
Published packages Not linked
- PyPI mcp-server-12306 Source link isn't a GitHub repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: mcp-server-12306 0.5.0.post20261103. No published advisory affects it (OSV, checked 2026-11-11).
Changes to this chain
- 2026-08-26 OSSF Scorecard: 2.3/10
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues MCP Server 12306’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How MCP Server 12306 compares in MCP Servers
- #584 Markifact: AI Performance Marketing 49.2 +0.2
- #585 Synter Media AI MCP Server 49.2 +0.2
- #586 MCP Server 12306 49.0 this agent
- #587 SearXNG HTTP MCP 48.9 −0.1
- #588 Funplay Godot MCP 48.9 −0.1
Bars show each HVTrust score; the tick marks MCP Server 12306’s 49.0.
Where the 49.0 comes from
HVTrust dimensions vs the MCP Servers average
49.0 / 100 · 100.0% confidenceMCP Server 12306 MCP Servers average (779 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
52.2 / 100Common questions about MCP Server 12306
Does MCP Server 12306 publish package provenance?
Does MCP Server 12306 have an OpenSSF Scorecard?
Is MCP Server 12306 actively maintained?
What license does MCP Server 12306 use?
Are MCP Server 12306's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to MCP Server 12306's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain MCP Server 12306?
For maintainers
HVTrust scores MCP Server 12306 from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/mcp-server-12306)
<a href="https://hvtracker.net/agents/mcp-server-12306"><img src="https://hvtracker.net/badge/mcp-server-12306.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON