updated 2026-11-10 04:07 UTC

Korea Stock MCP

Repository Website

MCP Server for Korean stock analysis. 한국 주식 분석을 위한 MCP 서버입니다.

MCP Servers TypeScript Listed ISC

Is Korea Stock MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 2.4 / 10
Provenance Attested
Signed commits 6%
Last push today
Advisories None known
Compare Korea Stock MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Korea Stock MCP scores 64.9/100 (Grade C), ranked #540 of 1374 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.4/10; 6% of recent commits are signed; no published advisory affects its latest release (korea-stock-mcp); last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Korea Stock MCP 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Korea Stock MCP 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.

  1. Source Partly signed

    github.com/jjlabsio/korea-stock-mcp, ISC, last pushed 2026-11-10. 6% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 2.4/10 (scanned Nov 1, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies4
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies 4
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked and attested

    • npm korea-stock-mcp Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: korea-stock-mcp 1.4.1. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-09-09 OSSF Scorecard: 2.8/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 Korea Stock MCP’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.

Signed credential (JSON) How to verify

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 Korea Stock MCP compares in MCP Servers

  1. #306 ZulipChat MCP Server 64.9 ±0
  2. #307 E18e MCP 64.9 ±0
  3. #308 Korea Stock MCP 64.9 this agent
  4. #309 Web Researcher MCP 64.7 −0.2
  5. #310 Webcomponents MCP Server 64.7 −0.2

Bars show each HVTrust score; the tick marks Korea Stock MCP’s 64.9.

Where the 64.9 comes from

HVTrust dimensions vs the MCP Servers average

64.9 / 100 · 100.0% confidence

Korea Stock MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.8 / 25
in line with avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
10.5 / 17
1.8 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
12.0 / 20
in line with avg 12.2
AdoptionLog-scaled stars · package downloads
8.6 / 20
1.0 above avg 7.6

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-11-01
Rank Moved
Rank dropped 17 spots (#526 → #543)
2026-10-15
Grade Changed
Trust grade B → C
2026-10-15
Rank Moved
Rank dropped 10 spots (#504 → #514)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.4/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent
View MCP Servers Report missing data
46.2
Activity sub-score · out of 100
#308
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 C 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 →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
184
Forks
42
Last Push
2026-11-10
today
Commits (4 wk)
0?
Downloads (7d)
219
npm
HN mentions (30d)
—
Open Issues
3
Rank Change
▼1
was #539

Analysis

Activity Inputs

46.2 / 100
StarsRepository reach
13.6 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
7.6 / 20

Common questions about Korea Stock MCP

Korea Stock MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Korea Stock MCP publish package provenance?
Yes. Korea Stock MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Korea Stock MCP have an OpenSSF Scorecard?
Korea Stock MCP has an OpenSSF Scorecard score of 2.4/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 Korea Stock MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Korea Stock MCP use?
Korea Stock MCP ships under ISC. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Korea Stock MCP's commits signed?
6% of the last 100 commits to Korea Stock 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
Korea Stock MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
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
high confidence
Match
Published package metadata matches the tracked repo
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 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.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 19Grade 8HVTrust 5Scorecard 1Delisted 1Listed 1Provenance 1MCP 1
2026-11-01
Rank Moved
Rank dropped 17 spots (#526 → #543)
2026-10-15
Grade Changed
Trust grade B → C
2026-10-15
Rank Moved
Rank dropped 10 spots (#504 → #514)
2026-10-12
Grade Changed
Trust grade C → B
2026-10-09
Grade Changed
Trust grade B → C
2026-10-09
Rank Moved
Rank dropped 18 spots (#488 → #506)
2026-10-02
Rank Moved
Rank dropped 17 spots (#462 → #479)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 615 spots (#1077 → #462)
2026-09-23
HVTrust Changed
HVTrust up 42.8pts (22.7 → 65.5)
2026-09-22
Newly Listed
First tracked at rank #1077
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-11
Rank Moved
Rank dropped 14 spots (#425 → #439)
2026-09-09
Scorecard Added
OSSF Scorecard: 2.8/10
2026-09-09
Grade Changed
Trust grade C → B
2026-09-09
Rank Moved
Rank rose 179 spots (#602 → #423)
2026-09-09
HVTrust Changed
HVTrust up 5.9pts (59.6 → 65.5)
2026-09-07
Rank Moved
Rank dropped 49 spots (#544 → #593)
2026-09-05
Grade Changed
Trust grade D → C
2026-09-05
Rank Moved
Rank rose 533 spots (#1070 → #537)
2026-09-05
HVTrust Changed
HVTrust up 20.4pts (39.4 → 59.8)
2026-09-04
Grade Changed
Trust grade C → D
2026-09-04
Rank Moved
Rank dropped 616 spots (#454 → #1070)
2026-09-04
HVTrust Changed
HVTrust down 20.5pts (59.9 → 39.4)
2026-09-03
Rank Moved
Rank dropped 37 spots (#417 → #454)
2026-09-02
Grade Changed
Trust grade D → C
2026-09-02
Rank Moved
Rank rose 513 spots (#930 → #417)
2026-09-02
HVTrust Changed
HVTrust up 20.6pts (39.9 → 60.5)
2026-09-01
Rank Moved
Rank dropped 35 spots (#895 → #930)
2026-08-31
Rank Moved
Rank dropped 31 spots (#864 → #895)
2026-08-30
Rank Moved
Rank dropped 35 spots (#829 → #864)
2026-08-29
Rank Moved
Rank dropped 44 spots (#785 → #829)
2026-08-28
Rank Moved
Rank dropped 25 spots (#760 → #785)
2026-08-27
Rank Moved
Rank dropped 21 spots (#739 → #760)
2026-08-26
Rank Moved
Rank dropped 99 spots (#640 → #739)
GitHub → Website → npm: korea-stock-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 64.9 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/korea-stock-mcp.svg)](https://hvtracker.net/agents/korea-stock-mcp)
HTML:
<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

Data sources
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.4 · Raw JSON