Skip to main content
Glama
uedayou

loa-mcp-server

by uedayou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to loa-mcp-server

No user-submitted related servers found.

    Related Servers

    • geojp-mcp

      55tarkun
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Japanese address and parcel lookup using ReverseGeoJP and ChibanJP APIs, enabling AI agents to convert coordinates to addresses and vice versa.
      4
      37 npm
      MIT

    • kenall-mcp

      knsh14
      A
      license
      B
      quality
      D
      maintenance
      MCP server that provides access to the Kenall postal code API for Japanese address lookups, enabling lookup by postal code and search by address.
      2
      MIT

    • chuk-mcp-geocoder

      IBM
      A
      license
      A
      quality
      C
      maintenance
      An 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.
      10
      Apache 2.0

    • geocode-mcp

      danishashko
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for geocoding, reverse geocoding, place/POI search, and distance calculation using OpenStreetMap Nominatim, with no API key required.
      43 npm
      1
      MIT

    • geocodage-mcp

      cvagner
      A
      license
      A
      quality
      D
      maintenance
      MCP server for geocoding French addresses, POIs, and cadastral parcels using the Géoplateforme API. Supports direct geocoding, reverse geocoding, and capability queries.
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 8 tools

    Disambiguation4/5

    Tools are largely distinct, but get_address_location and get_address_locations (singular/plural) could be confused, and get_address_locations vs save_address_locations_to_file also share a similar batch pattern. However, extensive descriptions with explicit usage guidance minimize misselection.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores (get, search, list, reverse_geocode, save). The singular/plural pair is the only minor deviation but remains predictable.

    Tool Count5/5

    8 tools is well-scoped for an address geocoding and GeoJSON server, covering search, single/batch fetch, hierarchy exploration, reverse geocoding, and file export. Each tool has a distinct role and the count is within the ideal range.

    Completeness4/5

    Core workflows are fully covered: search, single/batch geocoding, drill-down via prefectures and child addresses, banchi enumeration, reverse geocoding, and file export. Minor gaps exist such as lack of upward hierarchy traversal or explicit linkage from list_banchi to get_address_location, but these are workable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources