Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Kr Equities

NPM · @PIPEWORX/MCP-KR-EQUITIES · 2 COMPONENTS

Korean equities MCP. Keyless, live per request.

84 Trust /100

Last scanned (7 hours ago)

Scores higher than 81% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-kr-equities). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 608 tokens (~101/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.10 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 31 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 30 Oct 26 81

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-kr-equities@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-kr-equities
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-kr-equities/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3649587962
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:353d87017bb8c32e40a098354fff8e8e434de0c1185635c3f02617485851fa927605a890846c5e962db95ba323e492fcc09365166615e294c9f204c8c

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~553 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
kr_index ~73

Level, change and recent daily history of a Korean market index: KOSPI, KOSDAQ or KOSPI200.

NameTypeReqDescription
daysnumber–Daily history rows to include (default 5, max 60)
indexstringyesKOSPI, KOSDAQ or KOSPI200

No output schema declared.

No examples provided.

kr_investor_flows ~63

Recent daily net buying by investor type (foreign, institutional, individual) in shares for one Korean listed stock, plus the foreign holding ratio, newest first.

NameTypeReqDescription
codestringyes6-character Korean stock code, e.g. 005930

No output schema declared.

No examples provided.

kr_price_history ~86

Daily OHLCV history for one Korean listed stock, newest first, with the performance over the window (first-to-last close change %). Use for "how has X performed" questions.

NameTypeReqDescription
codestringyes6-character Korean stock code, e.g. 005930
daysnumber–Trading days to return (default 20, max 120)

No output schema declared.

No examples provided.

kr_quote ~111

Current or last-close quote for one Korean listed stock by 6-character code: price, change, day range, volume, market cap, 52-week range, PER/PBR/EPS/dividend yield, foreign ownership, and the issuer identity and exchange (KOSPI/KOSDAQ). Returns market_status (OPEN/CLOSE) and the exchange timestamp.

NameTypeReqDescription
codestringyes6-character Korean stock code, e.g. 005930 (Samsung Electronics), 000660 (SK hynix)

No output schema declared.

No examples provided.

kr_search_stocks ~127

Resolve a Korean company name (Korean or English) or 6-character stock code to its listed issuer, code and market (KOSPI or KOSDAQ). Use this to map a ticker like 005930 to Samsung Electronics (삼성전자) or to find the code for "SK hynix". Includes ETFs, flagged via is_etf.

NameTypeReqDescription
limitnumber–Max results (default 10, max 30)
querystringyesCompany name (삼성전자, "samsung electronics", hynix) or stock code (005930)

No output schema declared.

No examples provided.

kr_top_by_market_cap ~93

The largest listed companies on KOSPI or KOSDAQ ranked by market capitalisation, with code, price, daily change and volume. Includes ranking offset for paging.

NameTypeReqDescription
limitnumber–Rows (default 10, max 50)
marketstringyesKOSPI or KOSDAQ
pagenumber–Page of results, 1-based (default 1)

No output schema declared.

No examples provided.

Install

How do I install the Kr Equities MCP server?

Kr Equities runs locally as an npm package, launched with npx -y @pipeworx/mcp-kr-equities. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-kr-equities

# add to Claude Code
claude mcp add pipeworx-io-kr-equities -- npx -y @pipeworx/mcp-kr-equities
Common questions

What is the Kr Equities MCP server?

Kr Equities is an MCP server listed in the public MCP registry as io.github.pipeworx-io/kr-equities. Korean equities MCP. Keyless, live per request. This page covers its npm package (@pipeworx/mcp-kr-equities).

Is the Kr Equities MCP server safe to use?

Kr Equities scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Kr Equities MCP server expose?

Kr Equities exposes 6 tools: kr_search_stocks, kr_quote, kr_price_history, kr_investor_flows, kr_index, kr_top_by_market_cap. Their descriptions and schemas cost roughly 553 tokens of context every time the server is loaded.

Is the Kr Equities MCP server still maintained?

Kr Equities is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Kr Equities MCP server under?

Kr Equities declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Kr Equities MCP server?

VerifyMCP ran 16 checks on Kr Equities, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.