Philippine-Geocoding
Related Servers
Alternatives to Philippine-Geocoding
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for the Philippine Standard Geographic Code (PSGC) API. Gives AI agents structured access to the full PH geographic hierarchy - regions, provinces, cities, municipalities, and barangays.5 npmMIT
- AlicenseAqualityCmaintenanceAn MCP server providing real-time access to Philippine government data including earthquakes, weather, typhoons, procurement, population, and air quality. It enables AI agents to query multiple official Philippine data sources through a unified interface for research and analysis purposes.4146 PyPI5MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server providing comprehensive cloud region data across all major providers. Query, filter, and compare cloud infrastructure locations worldwide.1460 npmMIT
- AlicenseAqualityDmaintenanceModel Context Protocol (MCP) server that provides weather forecast, warnings, water level associated with flood, and earthquake reports from Malaysia Government's Open API.41MIT
- AlicenseAqualityCmaintenanceA Model Context Protocol server that retrieves detailed geographic information about IP addresses using the ipinfo.io API, helping determine user location and network details.544MIT
- AlicenseAqualityCmaintenanceAn MCP server providing geocoding and place discovery services via Nominatim and OpenStreetMap. It enables users to perform forward and reverse geocoding, extract bounding boxes, and find nearby places or administrative hierarchies.10Apache 2.0
TDQS
Scored across 41 tools
Most tools have clearly distinct purposes based on geographic entity type and scope, with minimal overlap. However, some tools like get_region_cities_municipalities and get_region_cities/get_region_municipalities could cause confusion about when to use the combined vs. separate versions. The search_by_name and validate_code tools are clearly distinct from the hierarchical retrieval tools.
All tools follow a perfectly consistent verb_noun pattern with 'get_' prefix for retrieval operations, and entity names are consistently pluralized for lists and singular for specific items. The two non-get tools (search_by_name, validate_code) maintain the same naming convention with clear action prefixes.
With 41 tools, this is excessive for a geocoding server. Many tools could be consolidated into parameterized versions (e.g., a single get_entities tool with type and scope parameters). The server feels heavy and overwhelming despite covering a coherent domain.
The tool surface provides comprehensive coverage of Philippine geographic hierarchy with complete CRUD-like retrieval operations for all entity types (island groups, regions, provinces, districts, cities, municipalities, barangays). It includes both listing and specific retrieval, hierarchical navigation, search, and validation - no obvious gaps exist for the stated geocoding purpose.