updated 2026-08-12 05:02 UTC

MCP Server 12306

drfccv/mcp-server-12306

12306 MCP Server​​ 是一个基于 ​​Model Context Protocol (MCP)​​ 的高性能火车票查询后端系统。它通过标准化接口提供官方 12306 的实时数据服务，包括余票查询、车站信息、列车经停站、中转换

MCP Servers Python Grade D Listed MIT
31.1/100
Rank #753 of 1283
Compare MCP Server 12306

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-07 · 5d ago
Recent change
Rank +1

Is MCP Server 12306 safe? MCP Server 12306 scores 31.1/100 (Grade D), ranked #753 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 22% of recent commits are signed; last pushed 2026-08-07. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#348 Figma MCP Rust — 31.2 (D) → #349 NotebookLM MCP (PleasePrompto) — 31.2 (D) → #351 MCP Cn Commerce — 30.9 (D) → #352 Pyxel MCP — 30.9 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 41 spots (#714 → #755)
2026-08-08
Newly Listed
First tracked at rank #712
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for MCP Server 12306 View MCP Servers Report missing data
55.4
Activity sub-score · out of 100
#350
In MCP Servers

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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 5 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
359
Forks
58
Last Push
2026-08-07
5 days ago
Commits (4 wk)
3?
Downloads (7d)
1,373
pypi
HN mentions (30d)
—
Open Issues
1
Rank Change
▲1
was #754

Analysis

HVTrust Dimensions vs MCP Servers

31.1 / 100 · 67.0% confidence

MCP Server 12306 MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
1.1 / 25
3.9 below avg 5.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
12.9 / 20
in line with avg 12.4
AdoptionLog-scaled stars · package downloads
10.3 / 20
4.5 above avg 5.8

Activity Inputs

55.4 / 100
StarsRepository reach
15.3 / 30
FreshnessLast push recency
24.3 / 25
ActivityRecent commits
7.5 / 25
CommunityFork signal
8.2 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
22%
of last 100 commits verified

Is MCP Server 12306 safe?

Public trust evidence for MCP Server 12306 is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does MCP Server 12306 publish package provenance?
No published build provenance is currently detected for MCP Server 12306. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does MCP Server 12306 have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for MCP Server 12306. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is MCP Server 12306 actively maintained?
Actively maintained. The repository was pushed to within the last 5 day(s).
What license does MCP Server 12306 use?
MCP Server 12306 ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Server 12306's commits signed?
22% of the last 100 commits to MCP Server 12306 are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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
Scored in HVTrust

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 Server Support
medium confidence
Implemented
MCP Server 12306 appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Listed 1Rank 1
2026-08-10
Rank Moved
Rank dropped 41 spots (#714 → #755)
2026-08-08
Newly Listed
First tracked at rank #712
GitHub → PyPI: mcp-server-12306

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 31.1 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/mcp-server-12306.svg)](https://hvtracker.net/agents/mcp-server-12306)
HTML:
<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

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON