Skip to main content
Glama
SebastianWild

Dawarich MCP

by SebastianWild
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Dawarich MCP

No user-submitted related servers found.

    Related Servers

    • Foursquare MCP Server

      jbeker
      F
      license
      A
      quality
      D
      maintenance
      Exposes Foursquare/Swarm check-in data and user activity through 13 tools, enabling user management, check-in history, venue details, mayorships, lists, and cross-user search.
      13
      -

    • mcp-geo

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables geographic utilities from public APIs: geocoding addresses and places, reverse geocoding coordinates, retrieving country details, timezone data, and sunrise/sunset times through natural language requests.
      2 npm
      1
      MIT

    • SQLite Geography Server

      pdichone
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables exploration of geographical data including countries, cities, states/provinces, and regions through a SQLite database. Supports searches by name, location coordinates, currency, and regional groupings with comprehensive statistical queries.
      6
      -

    • MapGO MCP

      Nomit83
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides geospatial tools for AI assistants to determine location hierarchy, border distance, coastline distance, and point-to-point distance using MapGO.
      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

    B3.1/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools are clearly distinct: places, visits, points, timeline, stats, and recalculate all have separate purposes. However, the three trip tools (create/update/delete) are functionally identical stubs that all report an API gap, making them hard to distinguish by action despite different names.

    Naming Consistency5/5

    All tools follow a consistent dawarich_<verb>_<noun> pattern in snake_case, with verbs like search, find, create, update, delete, add, merge, and bulk_update. This is highly predictable and readable.

    Tool Count4/5

    At 19 tools, the server is slightly over the ideal 3-15 range but still reasonable for a domain covering places, visits, points, trips, stats, timeline, and map context. The three non-functional trip tools could be trimmed, but the count is not excessive.

    Completeness3/5

    Core place/visit/point operations are well represented, plus useful extras like timeline, stats, and map context. However, trip tools are non-functional stubs that only report an API gap, creating dead ends for trip workflows, and there is no delete_visit tool. These are notable gaps.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources