概要
What is Koreafilings Mcp?
Koreafilings Mcp is an x402-paid HTTP API that converts Korean corporate disclosures (DART · 전자공시) into machine-ready English summaries. Pay 0.005 USDC per summary over Base, no API key, no signup. Built for autonomous AI agents and indie agent builders who need diverse data sources and prefer pay-per-call to subscriptions.
How to use Koreafilings Mcp?
Install the TypeScript SDK via npm install koreafilings, the Python SDK via pip install koreafilings, or the MCP server via uv tool install koreafilings-mcp for Claude Desktop, Cursor, Continue, etc. Configure a payer private key and Base network. Invoke tools: find_company (free), list_recent_filings (free), get_pricing (free), get_recent_filings(ticker, limit) (paid), get_disclosure_summary(rcpt_no) (paid). Also accessible via direct HTTP with curl and x402 v2 payment flow.
Key features of Koreafilings Mcp
- Pay-per-call with 0.005 USDC per summary, no subscriptions.
- No API key, no signup, no procurement loop.
- x402 standard payment transport on Base mainnet.
- English summaries with extracted quantitative data (amounts, dates, counterparties).
- Caching: first agent pays LLM cost; subsequent requests hit cache at same flat price.
Use cases of Koreafilings Mcp
- AI agents fetching English summaries of Korean corporate filings for trading decisions.
- Indie developers building automated investment tools with pay-per-call data.
- Autonomous agents discovering and paying for diverse public-records data without human signup.
FAQ from Koreafilings Mcp
How is pricing and authentication handled?
No API keys, no signup. Authentication is via an Ethereum wallet signing a transferWithAuthorization. Payment is 0.005 USDC per summary, settled on-chain over Base mainnet via the x402 v2 transport.
What dependencies or runtime are required?
The MCP server requires Python 3.11+ and uv. The TypeScript SDK works in Node 18+, browsers, Cloudflare Workers, and Vercel Functions. Python SDK requires Python 3.8+. All require a wallet private key on Base network and USDC balance.
Where does the data come from and is it cached?
Data comes from the DART (전자공시) Korean corporate disclosure system. Summaries are cached in PostgreSQL; the first request for a disclosure pays the LLM cost, subsequent requests hit the cache and pay the same 0.005 USDC.
What are the known limits?
The free endpoints are rate-limited only by HTTP server capacity. Paid endpoints charge dynamically per summary; the server declares the exact amount in the 402 challenge. No explicit limit on concurrent requests is mentioned.
What transports are supported?
The MCP server (stdio), TypeScript/JavaScript SDK (HTTP), Python SDK (HTTP), and direct HTTP (curl). All use the x402 v2 transport with PAYMENT-SIGNATURE header and settle on-chain.
