Korean stock market intelligence for AI assistants — track DART filings, foreign & activist investor activity, and classified Korean industry news, in English. MCP server for ChatGPT / Claude / Cursor / FastMCP agents.
koreanpulse shows mixed quality across 7 tools. Strengths: all tools have names starting with action verbs (track_, lookup_, resolve_, search_, monitor_, etc.); detailed descriptions present for most tools; input parameters include type definitions and descriptions; tool annotations (READ_ONLY risk flags) present. Weaknesses: output schemas are NOT documented anywhere in the provided source, the mcp.json lists tool names and descriptions but no return type specifications; parameter descriptions vary significantly in detail; several parameters lack constraints (enums, min/max bounds); no pagination parameters visible despite track_korean_filings returning up to 30 items and monitor_* tools returning up to 50 items; error handling guidance is absent from tool descriptions.
Server metadata — version, available tools, corp index size.
Resolve a Korean company name (or partial name) to its DART corp_code.
License-gated (requires a license_key argument). Korean activist investor tracking — DART type-D shareholding disclosures with activist filer auto-tagging (17 named filers: KCGI, Align, Truston, Anda, Cha, Life, Platform, VIP, Must, Dalton, Flashlight Capital Partners, Oasis, Palliser, Whitebox, City of London, plus international ValueAct / Elliott). Disclosure data only — not a buy/sell recommendation.
License-gated (requires a license_key argument). Monitor foreign investor activity in Korean stocks — DART type-D 5%-rule disclosures by foreign passive holders (BlackRock, Vanguard, State Street, Fidelity, T. Rowe Price, Wellington, Norges, GIC, Temasek, Goldman, JPM, Morgan Stanley, Citadel, Millennium, Bridgewater + 5 more). Disclosure data only — not a buy/sell recommendation.
Resolve a 6-digit KRX stock code to its DART corp entry.
Output schemas completely absent. mcp.json lists tool names and descriptions but provides zero information about return types, field structures, or what data the agent receives back. This forces LLMs to guess what fields exist and violates the requirement that agents know what to expect from a tool response.
Pagination parameters missing. track_korean_filings accepts 'limit' but no 'offset' or 'page' parameter; monitor_activist_investors and monitor_foreign_holders accept 'limit' but no pagination cursor or offset. When tools return lists capped at 30-50 items, agents need a way to fetch subsequent pages.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | 2026-07-28+ | v2 |
Search recent Korean industry news (etnews / 한국경제 / Korea Herald / zdnet) classified into 16 industries.
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.
No error handling guidance in descriptions. Tools expose API keys (DART_API_KEY, OPENAI_API_KEY) and external service calls but descriptions do not indicate what errors are retryable, how to recover from rate limits, or how to handle credential failures. Agents have no direction on next steps when a call fails.
Parameter constraints not enumerated. 'filing_type' and 'industry' are described as free-form strings with no enum values, valid range, or format documented. LLMs cannot self-correct when passing invalid filing_type codes or unknown industries, they must guess.
Inconsistent parameter naming across similar tools. monitor_activist_investors uses 'activist_name' (string filter) while monitor_foreign_holders uses 'foreign_holder_name' (string filter). Both tools also accept 'company_corp_code' but track_korean_filings uses 'company_corp_codes' (array). These inconsistencies force agents to reason about parameter names rather than compose calls naturally.
Ambiguous date parameter handling. 'since' parameter in track_korean_filings accepts ISO-8601 but is described only as 'ISO-8601 date or datetime cutoff (e.g. ...), no min/max bounds, no semantics (inclusive? exclusive?), no clarification of whether time zone matters for a Korean service.
License key handling unclear. monitor_activist_investors and monitor_foreign_holders state 'requires a license_key argument' but description does not clarify: is the key validated server-side per call? Does it gate the entire tool or only certain result types? What happens if key is missing or invalid? This ambiguity invites errors.