tossinvest-openapi-mcp
Related Servers
Alternatives to tossinvest-openapi-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceA 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
- FlicenseAqualityBmaintenanceMCP server for Toss Securities Open API that exposes Korean (KRX) and US market data, portfolio holdings, order management, and conditional orders through 28 tools, with read-only and authenticated remote modes.28-
- AlicenseAqualityBmaintenanceA read-only MCP server exposing Toss Securities Open API tools for Korean and US stock quotes, symbol search, order books, candles, exchange rates, market calendars, rankings, and market indicators. It does not implement account access or order placement, ensuring no side effects.13MIT
- AlicenseAqualityDmaintenanceMCP server wrapping Toss Securities Open API, enabling stock price queries and trading for Korean and US stocks via natural language.3615 npmMIT
- AlicenseCqualityBmaintenanceSafe-by-default MCP server for the official Toss Securities Open API, providing read-only market and account data with optional order operations protected by multiple safety gates.27244 npm2MIT
- AlicenseAqualityAmaintenanceA read-only MCP server for Toss Securities Open API that enables AI assistants to retrieve stock prices, resolve symbols, check holdings, buying power, exchange rates, and OHLCV candles without placing orders.2911 npm1MIT
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: code generation, API overview, endpoint detail, integration guide, schema detail, category listing, endpoint listing, schema listing, and keyword search. No two tools overlap in functionality, and descriptions clearly differentiate them.
All tool names use a consistent verb_noun pattern in snake_case (e.g., generate_code_sample, list_endpoints, search_endpoints). The verbs are either 'get', 'list', 'generate', or 'search', and the pattern is uniform across all 9 tools.
With 9 tools, the set is well-scoped for an API exploration assistant. Each tool contributes to a specific aspect of the workflow (overview, categorization, endpoint details, schemas, search, integration guides, code generation), without being too many or too few.
The tool surface covers the full lifecycle of discovering and understanding an OpenAPI specification: from high-level overview to category listing, endpoint listing and detail, schema listing and detail, keyword search, integration guides, and code sample generation. There are no obvious gaps for the stated purpose.