K-Stock MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KIS_ENV | No | KIS environment: `paper` (default) or `real`. Anything else is rejected rather than silently treated as real. | paper |
| KIS_CANO | No | KIS account number (CANO) used together with `KIS_ACNT_PRDT_CD` as an alternative to `KIS_ACCOUNT_NO`. | |
| KIS_APP_KEY | No | KIS Open API app key for the chosen environment. | |
| DART_API_KEY | No | OpenDART API key. Required for DART-based tools such as `get_ipo_schedule`, `get_disclosure`, and `get_financials`. | |
| KIS_ACCOUNT_NO | No | KIS account number, e.g. `12345678-01`, `1234567801` or `12345678` (product code defaults to `01`). Required for `get_balance`. Can be used instead of `KIS_CANO` + `KIS_ACNT_PRDT_CD`. | |
| KIS_APP_SECRET | No | KIS Open API app secret for the chosen environment. | |
| KIS_ACNT_PRDT_CD | No | KIS account product code used together with `KIS_CANO` as an alternative to `KIS_ACCOUNT_NO`. | |
| KSTOCK_MCP_CACHE_DIR | No | Cache directory: stores KIS token (mode 0600), symbol master (1 day), and DART company codes (7 days). | ~/.cache/kstock-mcp |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_stockA | Find Korean listed securities (KOSPI/KOSDAQ/KONEX) by name or code. Returns code, name, market, type. |
| get_quoteA | Current price, day range, volume, valuation ratios and order book for a stock (KIS, KRX market). |
| get_ohlcvA | Historical candles (open/high/low/close/volume), oldest first. Up to ~300 rows per call; see 'truncated'. |
| get_balanceA | Holdings and account summary for the configured KIS account (paper by default). Read-only. |
| get_ipo_scheduleA | Upcoming/ongoing IPO (공모주) schedule from OpenDART equity filings: subscription dates, price text, underwriters, and an optional equal-allocation estimate whose formula and assumptions are in the response. |
| get_disclosureA | Recent DART disclosures for a company, newest first, with links to the DART viewer. |
| get_financialsC | Key financial statement accounts (assets, liabilities, equity, revenue, operating income, net income) from DART. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a clearly distinct data type or resource: account balance, disclosures, financials, IPO schedule, historical candles, current quote, and symbol lookup. The closest pair (get_ohlcv vs get_quote) is well separated by 'historical candles' versus 'current price', so an agent can select correctly without guessing.
All names follow a consistent snake_case verb_noun pattern (get_balance, get_disclosure, get_financials, get_ipo_schedule, get_ohlcv, get_quote, search_stock). The single search_ prefix is a meaningful and standard distinction from the get_ lookup family rather than an inconsistency.
Seven tools is well scoped for a read-only Korean market data server. Each tool covers a distinct data need (quote, candles, financials, disclosures, IPO calendar, lookups, account) and none appear redundant or filler.
The read-only data surface is broad and coherent: discovery (search_stock), pricing (get_quote, get_ohlcv), fundamentals (get_financials, get_disclosure, get_ipo_schedule), and account state (get_balance). Minor gaps remain, such as order/trade history or watchlist management, but these are plausibly out of scope for a read-only server.