KiMCP
Related Servers
Alternatives to KiMCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to use Kakao's Local, Search, and Vision APIs for address conversion, place search, web/blog/search, and OCR, requiring only a REST API key.6MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to search places and addresses, compute driving, walking, and kickboard routes, optimize waypoints, and calculate distance and time matrices. Results can be displayed as interactive maps within conversations.1267 npmMIT
- AlicenseAqualityDmaintenanceProvides access to Naver Search APIs, allowing AI agents to search across multiple categories (blogs, news, books, images, shopping items, etc.) with structured responses optimized for LLM consumption.134Apache 2.0
- AlicenseAqualityDmaintenanceProvides Naver Map API functions (geocoding, reverse geocoding, directions, static map, and usage queries) as MCP tools for use in Claude Desktop, VS Code, and other MCP clients.426 npm2Apache 2.0
- AlicenseBqualityDmaintenanceConnects to Kakao Local API and Kakao Maps, enabling access to location-based services and map functionality in Korea.4MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to access South Korean tourism information via the official Korea Tourism Organization API, providing comprehensive search for attractions, events, food, and accommodations with multilingual support.832 PyPI9MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of overlap or confusion between tools. The single tool has a clear, specific purpose.
The tool name follows a clear verb_noun pattern and is descriptive. However, with only one tool, there is not enough surface area to fully demonstrate naming consistency across a set.
A single tool feels too thin for a general-purpose server, even for a focused web-fetching utility. There is no room for alternative operations or related functionality.
For the stated purpose of fetching and stripping HTML from a webpage, the tool fully covers the core use case. Minor gaps exist, such as handling raw HTML or additional page metadata, but these are not obvious dead ends.