神岛数据统计 MCP 服务器
Related Servers
Alternatives to 神岛数据统计 MCP 服务器
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables access to SORACOM IoT platform data including Harvest sensor data, file storage, SoraCam camera footage/events, and SIM statistics through authenticated API calls.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables desktop agents and clients to access geospatial services via a hosted MCP server, including OpenStreetMap queries, address and business search, POI discovery, routing, matrices, isochrones, map matching, optimization, elevation and terrain, basemap styling, spatial analysis, rendering, usage, and service status.28 npmMIT
- AlicenseAqualityDmaintenanceProvides map services such as geocoding, POI search, and route planning through the Amap API, enabling AI applications to interact with map data via natural language.12MIT
- AlicenseAqualityDmaintenanceGeospatial API tools for AI agents — geocoding, reverse geocoding, routing, isochrone, distance matrix, static maps, H3 hexagons, elevation, GPS map-matching, point-in-polygon, address normalisation, timezone lookup, and batch geocoding. Built on OpenStreetMap infrastructure. Cost-effective alternative to Google Maps API.1814 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides comprehensive geographic information services and route planning for AI agents via the Amap (Gaode Maps) API. It supports geocoding, multi-modal navigation, POI searches, and administrative region queries.3-

Magic Lane MCP Serverofficial
AlicenseBqualityCmaintenanceEnables AI agents to become geospatially intelligent assistants with tools for location search, smart routing, round trip planning, reverse geocoding, isochrone analysis, route visualization, geofence management, and interactive map display.85 npm7Apache 2.0
TDQS
Scored across 19 tools
Each tool targets a distinct data entity (map info, comments, lists, stats), but getMapInfoByUserId and getMapReleaseInfoByUserId could be confused, as could getMapCommentListByUserId and getCommentList. Overall, scope is clear.
All tools use the get prefix and camelCase, generally following get<Resource>By<Parameter>. Some tools like getMapStatList and getMapPlayerStatList deviate from the By pattern, but the naming is still predictable.
19 tools is within the 16-25 heavy range; for a data retrieval server this is reasonable, though it could potentially be streamlined.
Covers user profiles, social lists, map/model data, statistics, and user interactions. Missing model details and leaderboard data, but core statistics workflows are covered.