Korea Stock MCP
MCP Server for Korean stock analysis. 한국 주식 분석을 위한 MCP 서버입니다.
Is Korea Stock MCP safe? Promising trust profile, but some evidence still deserves review.
Compare Korea Stock MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Korea Stock MCP scores 65.3/100 (Grade B), ranked #469 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 2.8/10; 6% of recent commits are signed; last pushed 2026-09-23. Every point is earned from checkable signals — never paid placement. How scoring works →
How Korea Stock MCP compares in MCP Servers
- #269 Google Workspace MCP 65.3 ±0
- #270 Hackmd MCP 65.3 ±0
- #271 Korea Stock MCP 65.3 this agent
- #272 MCP Uptime Kuma 65.1 −0.2
- #273 PageIndex MCP 65.1 −0.2
Bars show each HVTrust score; the tick marks Korea Stock MCP’s 65.3.
Where the 65.3 comes from
HVTrust dimensions vs the MCP Servers average
65.3 / 100 · 100.0% confidenceKorea Stock MCP MCP Servers average (775 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 B 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
45.6 / 100Supply Chain Trust
Common questions about Korea Stock MCP
Does Korea Stock MCP publish package provenance?
Does Korea Stock MCP have an OpenSSF Scorecard?
Is Korea Stock MCP actively maintained?
What license does Korea Stock MCP use?
Are Korea Stock MCP'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 Korea Stock 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.
Maintain Korea Stock MCP?
For maintainers
HVTrust scores Korea Stock 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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/korea-stock-mcp)
<a href="https://hvtracker.net/agents/korea-stock-mcp"><img src="https://hvtracker.net/badge/korea-stock-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON