OpenKRX MCP Server
Related Servers
Alternatives to OpenKRX MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceMCP server that provides Korean Exchange (KRX) Open API market data as tools, covering indices, stocks, ETPs, bonds, derivatives, commodities, and ESG.31MIT
- AlicenseAqualityCmaintenanceProvides Korean stock market data, including DART electronic disclosures and KRX trading information, enabling users to query company profiles, financial statements, and stock trade details via MCP clients.9MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query real-time and historical Korean stock market data from KRX (Korea Exchange) including indices, stocks, ETFs, bonds, derivatives, and commodities via MCP tools and resources.26 npm1MIT
- AlicenseNot gradedqualityBmaintenanceKorean stocks (KOSPI/KOSDAQ/KONEX), no signup, no API key. 12 read-only tools, streamable-http. Post-filing price paths BY DART FILING TYPE (market-adjusted median h0/h1/h5, 95% CI) + per-event ledger with receipt times (HH:MM) that public APIs omit. Plus T+1 closes, preliminary earnings, daily close history. Registry: com.aikstockdata/mcp. Updated each trading day ~18:30 KST, not real-time.7MIT

pykrx-mcpofficial
AlicenseNot gradedqualityCmaintenanceProvides Korean stock market data (KOSPI, KOSDAQ, KONEX) including prices, fundamentals, investor trading, short selling, and indices via MCP protocol, enabling natural language queries from AI agents like ChatGPT and Claude.33 PyPI3MIT- AlicenseCqualityAmaintenanceEnables querying South Korean stock disclosures, financial statements, and shareholder reports via the OpenDART API from any MCP-compatible client.87MIT
TDQS
Scored across 31 tools
Most tools are cleanly separated by market and instrument (e.g., KOSPI/KOSDAQ/KONEX stocks, ETF/ETN/ELW, bond sub-markets), so an agent can usually select the right one from the name alone. A few boundaries remain fuzzy without Korean market domain knowledge—KRX vs KOSPI index series, general futures/options vs stock futures/options, and the two warrant types—so it is not perfect.
Every tool uses a get_ prefix and snake_case, following a consistent get_<market>_<record> pattern where record is daily, base_info, or info. This makes tool names highly predictable across the whole set.
At 31 tools, this server is above the 25+ point where a flat tool list starts to burden an agent, even though each tool corresponds to a distinct KRX dataset. A parameterized interface grouping market and record type would be more appropriate for the apparent scope.
The daily-data surface is broad: stocks, indices, funds, bonds, derivatives, commodities, emissions, and ESG/SRI products all have dedicated tools, so core read-only workflows are covered. It lacks conveniences like date-range queries, intraday data, or unified search, but those fall outside the apparent daily-snapshot scope.