k-data-mcp

MCP server for Korean market data, metered per call in USDC over x402. No account, no API key, no signup — the server pays each request from a wallet you supply.

What you get

• Kimchi premium on a tradeable basis. Everyone quotes the premium against the official USD/KRW rate, but Korean capital controls mean the KRW exit leg actually goes through USDT — so that number is not something you can trade on. This returns both, and they routinely disagree in sign: official can read −0.27% while the realizable basis is +0.19%.

• Premium history and percentile context. A continuously recorded archive answers "is this premium unusual right now?" — percentile, mean, stdev, z-score over 1h–90d. No free source publishes this, and it cannot be reconstructed after the fact.

• Korean headlines translated to English, from Yonhap, Maeil Business and Hankyung. Korean myriad units (억 / 조) are expanded deterministically before translation, so "989억달러" comes back as $98.9 billion rather than the 10×-off answer language models produce unaided.

• Upbit KRW quotes and market summaries, USD/KRW.

Related MCP server: korean-agriculture-mcp

Install

npx k-data-mcp

Claude Desktop / Claude Code

{
  "mcpServers": {
    "k-data": {
      "command": "npx",
      "args": ["-y", "k-data-mcp"],
      "env": {
        "K_DATA_PRIVATE_KEY": "0xYOUR_DEDICATED_WALLET_KEY",
        "K_DATA_MAX_SPEND_USD": "1"
      }
    }
  }
}

Wallet setup

Each tool call spends real USDC, so the server will not start without a key and a budget.

1. Create a dedicated wallet — not your main one. The key sits in a config file and every call spends from it.

2. Fund it with the USDC you're willing to spend on Base. No ETH needed: x402 settles with an off-chain EIP-3009 signature and the facilitator pays the gas.

3. Set K_DATA_MAX_SPEND_USD. The server refuses any call that would push cumulative spend past it.

Tools

list_endpoints is free — call it first to see current prices and decide what's worth buying.

Prices are read from the provider's catalog at startup, so this table reflects whatever the service currently charges.

How payment works

Every paid endpoint answers an unpaid request with HTTP 402 and a PAYMENT-REQUIRED header describing the price, asset and recipient. This server signs an EIP-3009 authorization for that exact amount and retries; the facilitator settles it on Base. Nothing is held on account — you pay per call, and stop paying when you stop calling.

License

MIT