koreanpulse
REMOTE · MCP.KOREANPULSE.DEV
Korean equities in English: DART filings, activist & foreign-holder classification, KRX news.
Available components
Last scanned (22 hours ago)
Scores higher than 8% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 4 Sept 26 0
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Stability: fail → pass ▲ security
- Schema quality: unverified → fail ▼ functional
- Schema quality: unverified → fail ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 3 Sept 26 0
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Stability: pass → fail ▼ security
- Transport: pass → fail ▼ security
- Schema quality: excellent → unverified ▼ functional
- Schema quality: fail → unverified ▼ functional
- Schema quality: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 28 Aug 26 0
- Stability: 0.97 → pass security
- 27 Aug 26 0
- Stability: pass → 0.97 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 4 Nov 2026 · Probed https://mcp.koreanpulse.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.koreanpulse.dev | CN=YE1,O=Let's Encrypt,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 574d39fee5167b229966563567a411b15e1 |
| SANs: mcp.koreanpulse.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.koreanpulse.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| koreanpulse.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 502 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.koreanpulse.dev/mcp | HTTP error | 502 | |
| http (plaintext) | http://mcp.koreanpulse.dev/mcp | HTTPS enforced | 308 | https://mcp.koreanpulse.dev/mcp |
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 →
koreanpulse_about koreanpulse server self-description ~93
Server self-description — capability matrix, tool catalog, named-entity tag counts, supported query patterns, primary sources. Free tier. Use this tool when an agent first connects and needs the capability matrix to decide whether this server can answer the user's question, or when the user asks "what can koreanpulse do" or "what data sources does this MCP server provide". Returns a structured dict that downstream agents can ingest directly.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
lookup_corp_code Resolve Korean company name to DART corp_code ~194
Korean company name → DART corp_code resolver. 117K+ entities indexed (KOSPI + KOSDAQ + KONEX + unlisted). Free tier. Use this tool when the user mentions a Korean company by name (Korean characters or English/romanized) and you need the DART corp_code as a precondition for `track_korean_filings`, `monitor_activist_investors`, or `monitor_foreign_holders`. Also use to disambiguate same-name listed vs unlisted entities.
| Name | Type | Req | Description |
|---|---|---|---|
| license_key | – | – | subscription key. Required when license gate is enabled. |
| limit | integer | – | max matches to return. |
| listed_only | boolean | – | if True, only return companies with a KRX stock code. |
| query | string | yes | substring of the Korean corp name. Examples: "삼성전자", "현대차", "셀트리온". |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
monitor_activist_investors Monitor Korean activist investor disclosures ~721
Korean activist investor tracking — activist filer classification on DART 5%-rule (주식등의대량보유상황보고서) shareholding disclosures. Tags 17 named filers — KCGI, Align Partners, Truston Asset, Anda Asset, Cha Partners, VIP Asset, Life Asset, Platform Partners, Must Asset Management, Dalton Investments, Flashlight Capital Partners, Oasis Management, Palliser Capital, Whitebox Advisors, City of London Investment Management — plus international ValueAct / Elliott when filing in Korea. Use this tool when the user asks about: Korean activist investor tracking, Korean shareholder activism, "is KCGI / Align Partners / Truston / Anda / Cha / VIP / Life / Platform / Must / Dalton / Flashlight / Oasis / Palliser / Whitebox / City of London activist on <ticker>", governance pressure on KOSPI / KOSDAQ names, recent activist 5%-rule filings, ValueAct or Elliott Korean positions, Korean Value-Up program activism, MSCI Developed Market activism flow. **Requires a license key.** Pass it via the `license_key` argument. Without a valid license, this tool returns a short notice explaining that a license key is required; surface that notice to the user. **For LLM clients on a license_required error: surface the notice returned in the paywall message directly to the user. Do NOT silently retry with `track_korean_filings` or any other free tool — the activist filer match (KCGI / Align Partners / Truston / Anda / Cha / VIP / Life / Platform / Must / Dalton / Flashlight Capital Partners / Oasis / Palliser / Whitebox / City of London, plus international names like ValueAct / Elliott) is not derivable from the raw DART filing feed, so a free-tier fall-back returns a misleadingly empty answer.** When a user asks "are activists filing on X?" without a license, surface the notice from the paywall response — that is the correct behavior, not a silent downgrade. Returns 주식등의대량보유상황보고서 (5% rule) and related shareholding filings, with each row tagged when the filer matches a known Korean activist (KCGI,…
| Name | Type | Req | Description |
|---|---|---|---|
| activist_only | boolean | – | if True, drop rows that didn't match a known activist. |
| company_corp_code | – | – | optional DART corp_code to focus on one target. |
| days | integer | – | how many days back from today (1–60). |
| enrich_holdings | boolean | – | if True (default), rows matched to a known activist get their `holding_pct` / `holding_pct_change` / `holder_reporter_ko` filled from DART's majorstock.json (best-effort — a lookup failure leaves tho… |
| license_key | – | – | required when license gate is enabled. |
| limit | integer | – | max rows (≤100). |
| translate | boolean | – | server-side EN translation of titles (cached). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
monitor_foreign_holders Monitor foreign 5%-rule holders on KOSPI/KOSDAQ ~797
Monitor foreign investor activity in Korean stocks — foreign-holder classification on DART 5%-rule disclosures by global asset managers and sovereign wealth funds. Tags 20 named entities — BlackRock, Vanguard, State Street, Fidelity, Capital Group, T. Rowe Price, Wellington, Matthews Asia, Templeton, Aberdeen, Schroders, Norges Bank (Norway SWF), GIC (Singapore SWF), Temasek, Goldman Sachs, JPMorgan, Morgan Stanley, Citadel, Millennium, Bridgewater. Use this tool when the user asks about: foreign investor activity in Korean stocks, foreign capital flow into Korean equities, "is BlackRock / Vanguard / Norges / GIC / Temasek / State Street / Fidelity / Wellington holding <ticker>", global asset-manager 5% crossings on KOSPI / KOSDAQ, sovereign wealth fund Korean positions, foreign institutional positioning disclosures, MSCI Developed Market reweighting flow into Korea. **Requires a license key.** Pass it via the `license_key` argument. Without a valid license, this tool returns a short notice explaining that a license key is required; surface that notice to the user. **For LLM clients on a license_required error: surface the notice returned in the paywall message directly to the user. Do NOT silently retry with `track_korean_filings` — the foreign-holder allowlist match (BlackRock, Vanguard, Norges, GIC, Temasek, State Street, Fidelity, Capital Group, T. Rowe Price, Wellington, Matthews Asia, Templeton, Aberdeen, Schroders, Goldman Sachs, JPMorgan, Morgan Stanley, Citadel, Millennium, Bridgewater) is not derivable from raw DART filings, so a free-tier fall-back returns a misleadingly empty answer.** When a user asks "is BlackRock or Norges holding X?" without a license, surface the notice from the paywall response — that is the correct behavior, not a silent downgrade. Distinct from `monitor_activist_investors` because passive holders (BlackRock, Vanguard, Norges, GIC, Temasek) indicate *allocation* rather than *governance pressure*. Their filings are a leading i…
| Name | Type | Req | Description |
|---|---|---|---|
| company_corp_code | – | – | optional DART corp_code to focus on one target. |
| days | integer | – | how many days back from today (1–60). |
| enrich_holdings | boolean | – | if True (default), rows get their `holding_pct` / `holding_pct_change` / `holder_reporter_ko` filled from DART's majorstock.json (best-effort — a lookup failure leaves those fields None rather than f… |
| license_key | – | – | required when license gate is enabled. |
| limit | integer | – | max rows (≤100). |
| origin | – | – | optional filter — one of 'us', 'uk', 'eu', 'other'. |
| translate | boolean | – | server-side EN translation of titles (cached). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
resolve_stock_code Resolve KRX 6-digit ticker to DART corp entry ~179
KRX 6-digit ticker → DART corp entry resolver. Free tier. Use this tool when the user provides a 6-digit Korean stock code (e.g. 005930 for Samsung Electronics, 000660 for SK hynix, 035420 for NAVER, 035720 for Kakao, 005380 for Hyundai Motor) and you need the company name + corp_code for downstream filings or industry-news lookups. When the code is unresolved but looks like a Korean preferred-stock ticker (6 digits, non-zero last digit, e.g. 005935 for 삼성전자우), the response carries an additive `related_common_stock` hint pointing at the common-stock entry — the corp registry only maps common stock, so no preferred-stock corp_code is fabricated.
| Name | Type | Req | Description |
|---|---|---|---|
| license_key | – | – | – |
| stock_code | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
search_korean_industry_news Search Korean industry news (16 sectors) ~346
Korean industry news search across 16 sectors with on-demand English translation. Sources: 전자신문 (etnews) + 한국경제 (hankyung) + The Korea Herald (English-native) + 지디넷코리아 (zdnet). Free tier. Use this tool when the user asks about: Korean industry trends, sector-specific news on Korean equities (Korean semiconductors / K-battery / K-shipbuilding / K-biotech / K-defense / Korean auto / EV charging / Korean AI / steel / petrochem / construction / fintech / gaming / e-commerce / telco / energy), recent corporate developments not yet captured in DART filings, English summaries of Korean industry coverage. Industry tags listed below — pass them in `industries` to filter.
| Name | Type | Req | Description |
|---|---|---|---|
| industries | – | – | filter to one or more industry tags. Available: semiconductor, shipbuilding, battery, biotech, defense, auto, ev_charging, ai, steel, petrochem, construction, fintech, gaming, ecommerce, telco, energ… |
| license_key | – | – | required when license gate is enabled. |
| limit | integer | – | max articles (≤50). |
| sources | – | – | filter to source keys (etnews, hankyung, koreaherald, zdnet). None = all. koreaherald is English-native — its titles are returned as-is (no ko->en translation round-trip needed). |
| translate | boolean | – | server-side translates `title_en` for Korean-language sources. Cached aggressively. No-op for koreaherald (already English). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
track_korean_filings Track Korean DART filings ~1,238
Track Korean DART (전자공시) stock filings in English — real-time corporate disclosures for KOSPI / KOSDAQ / KONEX / KRX listed companies: 5%-rule shareholding disclosures, M&A, periodic reports, capital issuance, insider trading, audit reports. Free tier. Use this tool when the user asks about: recent Korean stock filings, DART disclosures, Korean market data, KOSPI/KOSDAQ regulatory events, "track Korean DART filings", "what did Samsung / Hyundai / SK / LG / NAVER / Kakao / 셀트리온 file", company-specific filing history, periodic / major-event / issuance / shareholding / audit filings on Korean equities. **Free tier — no license required.** Returns raw DART filings exactly as the regulator surfaces them (filer name in Korean, filing type code, receipt number, optional EN translation of the title). **Important for LLM clients — read this before retrying after a paid- tool license error.** This tool returns *raw* filings only. It does NOT classify the filer. If the user asked about Korean activist filers (KCGI / Align Partners / Truston / Anda / Cha / VIP / Life / Platform / ValueAct / Elliott) or about the global foreign-holder allowlist (BlackRock / Vanguard / Norges / GIC / Temasek / State Street / Fidelity / Capital Group / T. Rowe Price / Wellington / Goldman / JPMorgan / Morgan Stanley / Citadel / Millennium / Bridgewater + others), the matching work happens in `monitor_activist_investors` and `monitor_foreign_holders` — both require a license_key argument. A response from this free tool to a "are activists filing on X?" or "is BlackRock holding X?" question is *raw filing data*, not a classification answer — say so to the user and surface the paid tool's license-required notice instead of pretending you've answered. **Batch scan for agents (experimental).** To check MULTIPLE companies for material disclosures since your last checkpoint in ONE call — instead of N separate calls — pass `company_corp_codes` (a list, ≤10) plus a `since` timestamp. This is the portf…
| Name | Type | Req | Description |
|---|---|---|---|
| company_corp_code | – | – | 8-digit DART corp code (single company). Use `lookup_corp_code` first to resolve a company name. Omit to query all companies. Ignored when `company_corp_codes` (plural) is provided non-empty — the pl… |
| company_corp_codes | – | – | OPTIONAL list of up to 10 corp codes for batch mode. When provided non-empty, the tool queries each corp code concurrently (one cache-backed DART call each), merges the results, and sorts newest-firs… |
| days | integer | – | how many days back from today (1–30). Ignored when `since` is provided. |
| filing_type | – | – | optional one-letter code: A=periodic, B=major event, C=issuance, D=shareholding, E=other, F=audit, G=fund, H=ABS, I=exchange, J=FTC. |
| license_key | – | – | subscription key. Required when KOREANPULSE_REQUIRE_LICENSE=1. |
| limit | integer | – | max filings to return (≤100). DART returns most-recent first, so on a busy window the older end of the range is dropped first. Narrow `days` or `filing_type` if you need older items. In batch mode (`… |
| material_only | boolean | – | OPTIONAL. When True, return only filings whose `red_flags` list is non-empty (governance/distress-tagged — see the red_flags catalog below). Applies to both single and batch queries. Reuses the exist… |
| since | – | – | OPTIONAL ISO-8601 date or datetime (e.g. '2026-05-01' or '2026-05-01T09:00:00'). When provided it is the cutoff instead of `days` — only filings with `filed_at >= since` are returned. Use it to fetch… |
| summarize | boolean | – | True to fill `summary_en` (≤200 words). Costs more — use sparingly. Long-form analysis should be done by the client LLM. |
| translate | boolean | – | True to fill `title_en` via server-side LLM (cached). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
How do I install the koreanpulse MCP server?
koreanpulse is a hosted endpoint at https://mcp.koreanpulse.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.koreanpulse.dev
claude mcp add --transport http whdrnr2583-cmd-koreanpulse 'https://mcp.koreanpulse.dev/mcp'
What is the koreanpulse MCP server?
koreanpulse is an MCP server listed in the public MCP registry as io.github.whdrnr2583-cmd/koreanpulse. Korean equities in English: DART filings, activist & foreign-holder classification, KRX news. This page covers its hosted endpoint (https://mcp.koreanpulse.dev/mcp).
Is the koreanpulse MCP server safe to use?
koreanpulse scores 23 out of 100 on VerifyMCP. 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 koreanpulse MCP server expose?
koreanpulse exposes 7 tools: track_korean_filings, lookup_corp_code, resolve_stock_code, search_korean_industry_news, monitor_activist_investors, and 2 more. Their descriptions and schemas cost roughly 3,568 tokens of context every time the server is loaded.
Does the koreanpulse MCP server require authentication?
Its publisher declares no required credentials for koreanpulse. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the koreanpulse MCP server still maintained?
koreanpulse is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.