Akshare One MCP

MCP server that provides access to Chinese stock market data using akshare-one

MCP Servers Python Listed MIT

Is Akshare One MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 5.0 / 10
Provenance None
Signed commits 45%
Last push 2d ago
Compare Akshare One MCP
Suggest a correction

In detail: Akshare One MCP scores 53.1/100 (Grade C), ranked #848 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.0/10; 45% of recent commits are signed; last pushed 2026-09-24. Every point is earned from checkable signals — never paid placement. How scoring works →

How Akshare One MCP compares in MCP Servers

  1. #477 Bexio MCP Server 53.3 +0.2
  2. #478 Transcriptor MCP 53.2 +0.1
  3. #479 Akshare One MCP 53.1 this agent
  4. #480 Elasticsearch MCP Server 53.1 ±0
  5. #481 NotebookLM MCP (PleasePrompto) 53.1 ±0

Bars show each HVTrust score; the tick marks Akshare One MCP’s 53.1.

Where the 53.1 comes from

HVTrust dimensions vs the MCP Servers average

53.1 / 100 · 100.0% confidence

Akshare One MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.5 / 25
1.8 below avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
0.6 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
13.3 / 20
1.2 above avg 12.1
AdoptionLog-scaled stars · package downloads
5.7 / 20
1.5 below avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-25
Rank Moved
Rank dropped 10 spots (#840 → #850)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.0/10. Tighten the weakest checks to improve public safety evidence.
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.
55.6
Activity sub-score · out of 100
#479

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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-09-26 06:32 UTC · Repo last pushed 2 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
230
Forks
52
Last Push
2026-09-24
2 days ago
Commits (4 wk)
4?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
4
Rank Change
▲2
was #850

Analysis

Activity Inputs

55.6 / 100
StarsRepository reach
14.2 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
8.7 / 25
CommunityFork signal
8.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.0 / 10
OpenSSF Scorecard · scanned Sep 23, 2026
Signed Commits
45%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 0
CII-Best-Practices 0
Code-Review 0
Contributors 0
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 3
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 10
Vulnerabilities 10

Common questions about Akshare One MCP

Public trust evidence for Akshare One MCP 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 Akshare One MCP publish package provenance?
No published build provenance is currently detected for Akshare One MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Akshare One MCP have an OpenSSF Scorecard?
Akshare One MCP has an OpenSSF Scorecard score of 5.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Akshare One MCP actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does Akshare One MCP use?
Akshare One MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Akshare One MCP's commits signed?
44% of the last 100 commits to Akshare One MCP 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
high confidence
Implemented
Akshare One MCP 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
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Akshare One MCP'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.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-19
Activity Resumed
Activity resumed

Maintain Akshare One MCP?

For maintainers

HVTrust scores Akshare One MCP 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
Rank 18HVTrust 3Listed 2Grade 2Scorecard 1Score 1Fresh 1Delisted 1MCP 1
2026-09-25
Rank Moved
Rank dropped 10 spots (#840 → #850)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank dropped 326 spots (#522 → #848)
2026-09-23
HVTrust Changed
HVTrust up 13.4pts (39.5 → 52.9)
2026-09-22
Newly Listed
First tracked at rank #522
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Activity Resumed
Activity resumed
2026-09-19
Grade Changed
Trust grade D → C
2026-09-19
Rank Moved
Rank rose 301 spots (#1199 → #898)
2026-09-19
HVTrust Changed
HVTrust up 13.4pts (37.7 → 51.1)
2026-09-19
Activity Score Changed
Activity score up 34pts (22 → 56)
2026-09-09
Rank Moved
Rank dropped 12 spots (#1175 → #1187)
2026-09-08
Rank Moved
Rank dropped 16 spots (#1159 → #1175)
2026-09-07
Rank Moved
Rank dropped 19 spots (#1140 → #1159)
2026-09-06
Rank Moved
Rank dropped 14 spots (#1126 → #1140)
2026-09-05
Rank Moved
Rank dropped 34 spots (#1092 → #1126)
2026-09-04
Rank Moved
Rank dropped 25 spots (#1067 → #1092)
2026-09-03
Rank Moved
Rank dropped 54 spots (#1013 → #1067)
2026-09-02
Rank Moved
Rank dropped 49 spots (#964 → #1013)
2026-09-01
Rank Moved
Rank dropped 40 spots (#924 → #964)
2026-08-31
Rank Moved
Rank dropped 28 spots (#896 → #924)
2026-08-30
Scorecard Added
OSSF Scorecard: 4.0/10
2026-08-30
Rank Moved
Rank rose 388 spots (#1284 → #896)
2026-08-30
HVTrust Changed
HVTrust up 22.3pts (16.0 → 38.3)
2026-08-29
Rank Moved
Rank dropped 11 spots (#1273 → #1284)
2026-08-26
Rank Moved
Rank dropped 27 spots (#1235 → #1262)
2026-08-16
Rank Moved
Rank dropped 25 spots (#1206 → #1231)
2026-08-10
Rank Moved
Rank dropped 69 spots (#1127 → #1196)
2026-08-08
Newly Listed
First tracked at rank #1123

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 53.1 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/akshare-one-mcp.svg)](https://hvtracker.net/agents/akshare-one-mcp)
HTML:
<a href="https://hvtracker.net/agents/akshare-one-mcp"><img src="https://hvtracker.net/badge/akshare-one-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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