Skip to main content
Glama
xiaobenyang-com

Philippine-Geocoding

Related Servers

Alternatives to Philippine-Geocoding

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP 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.
      9 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      An 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.
      41
      70 PyPI
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A Model Context Protocol (MCP) server providing access to 2,198+ verified global GIS spatial services, layers, and open geospatial data sources.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Model Context Protocol (MCP) server that provides weather forecast, warnings, water level associated with flood, and earthquake reports from Malaysia Government's Open API.
      4
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that retrieves detailed geographic information about IP addresses using the ipinfo.io API, helping determine user location and network details.
      5
      34 PyPI
      44
      MIT

    TDQS

    B3.1/5.0

    Scored across 41 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues