MCP TMAP Server
Related Servers
Alternatives to MCP TMAP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA server that connects to Naver Maps and Search APIs, enabling geocoding and local search functionality for Korean locations.22MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for Korean public transit that enables route planning with real-time bus and subway arrivals, including fallback options. It combines ODsay route search with real-time data from Gyeonggi Bus and Seoul Metro systems.-
- AlicenseNot gradedqualityDmaintenanceA server that enables AI models to access Kakao Map features (place search, address lookup, route finding) and Daum search services (web, image, blog, cafe) through Model Context Protocol.17MIT
- FlicenseNot gradedqualityBmaintenanceThis MCP server provides accessibility risk assessment for Seoul subway trips, considering wheelchair, stroller, and other mobility constraints. It offers tools to check station facilities, elevator status, and calculates risk scores for routes based on a deterministic engine.-

inavi-mcpofficial
AlicenseAqualityAmaintenanceAn MCP server for the iNavi Maps API that gives AI assistants iNavi Maps API specifications and ready-to-use HTML templates for interactive map visualizations (geocoding, POI search, route planning).6280 npmMIT- AlicenseAqualityBmaintenancemcp-server-public-transport is an open-source, locally hosted server providing an interface for accessing public transport data across Europe.139PythonMIT
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one is for geocoding addresses to coordinates, and the other is for retrieving public transit routes between coordinates. There is no overlap in functionality, making it impossible to confuse them.
The naming is inconsistent: 'fullTextAddressGeocoding' uses camelCase, while 'publicTransitRoutes' uses a different style with mixed lower and upper case. There is no clear pattern, and the verb usage differs ('fullTextAddress' vs. 'publicTransit'), making it chaotic.
With only 2 tools, the server feels thin for a mapping/transit domain. It lacks basic operations like reverse geocoding, route alternatives, or transit schedule details, making it under-scoped for typical navigation or location-based tasks.
The server is severely incomplete for a mapping/transit service. It misses essential operations such as reverse geocoding, route optimization, transit stop information, or map data retrieval. The two tools provide only a narrow slice of functionality, leading to significant gaps in agent workflows.