finance-mcp-server-ko
Related Servers
Alternatives to finance-mcp-server-ko
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceA personal finance MCP server that combines DART official disclosures, Telegram analyst chatter, and Toss Securities live trading to give LLM agents research and execution capabilities.46MIT
- AlicenseNot gradedqualityAmaintenanceRead-only MCP server that connects LLMs to personal investment accounts (Toss Securities, KIS), market data, SEC filings, and Binance futures for context-aware investment responses.1MIT
- AlicenseAqualityCmaintenanceA local MCP server that automatically generates tools from Toss Securities' official OpenAPI spec, enabling real API calls with multi-layered order safety and OAuth 2.0 authentication.361MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that retrieves Korean stock fundamentals and financial data from OpenDART, enabling LLMs to access corporate disclosures, financial statements, and dividend information.Apache 2.0
- AlicenseAqualityDmaintenanceMCP server wrapping Toss Securities Open API, enabling stock price queries and trading for Korean and US stocks via natural language.3629 npmMIT
- AlicenseAqualityCmaintenanceSelf-hosted MCP server that wraps the Toss Securities Open API, enabling natural language queries for account balances, holdings, transactions, and stock prices via Claude.4MIT
TDQS
Scored across 46 tools
Distinct resource categories (company data, market data, trading, Telegram) are clear, but several tools overlap: search_company vs get_company_profile_by_query, get_financial_statements vs get_full_financial_statement, and multiple connection/credential-check tools. Descriptions mitigate most ambiguity, but an agent could still easily misselect between profile lookup tools or the various health-check tools.
Almost all tools follow a consistent snake_case verb_noun pattern (get_, search_, place_, cancel_, modify_). Minor inconsistencies exist around connection tools mixing test_connection, check_api_key, and check_api_credentials, and data tools lack a consistent integration prefix, but there is no chaotic naming.
46 tools is far above the typical well-scoped MCP server size, and the set mixes three largely unrelated integrations (DART, Toss, Telegram) plus six overlapping health-check tools. Many tools are individually useful, but the server would be better split into separate DART, trading, and Telegram servers, with several duplicate lookup/health-check tools removed.
The DART/Toss surface is quite complete: company search/profile, key and full financial statements, shareholder data, disclosures, dividends, market data, account read tools, and the order lifecycle (place/cancel/modify/get) are all present. Minor gaps exist—Telegram is read-only with no send_message tool, and some DART areas like audit reports or corporate governance details are not directly exposed—but core workflows are covered.