F
licenseNot graded
qualityB
maintenanceExposes read-only location history and related data from Dawarich via MCP tools, designed to run behind an OAuth-terminating proxy.
-
Dawarich MCP
by xstb
Related Servers
Alternatives to Dawarich MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenancePrivacy-first MCP server for Strava activities, streams, routes and training data.29168 npm3MIT
- AlicenseAqualityBmaintenanceA read-only MCP server that exposes personal Flighty app flight data as geo-ready legs with coordinates, enabling queries by date, year, or flight number, and aggregate stats.3MIT
- AlicenseBqualityAmaintenanceMCP server for local fitness-data extraction and analysis from Garmin Connect, Intervals.icu, and Strava. Provides read-only analytical tools over DuckDB and targeted Strava enrichment.35271 npmAGPL 3.0
- AlicenseAqualityCmaintenanceMCP server that exposes PrivacyTracker's app privacy data, changelogs, policy diffs, and sync status through read-only tools and resources for MCP-compatible clients.11Apache 2.0
- AlicenseAqualityAmaintenanceMCP server for OP3 podcast analytics: downloads, geography, app share. Read-only.630 npm1MIT
TDQS
A4.1/5.0
Scored across 9 tools
Disambiguation5/5
Each tool targets a distinct data type or operation: stats aggregates, timeline summarizes days, visits identifies places, track points and list points differ by scope, track detail is a compact overview, export transforms, reverse geocode converts coordinates, and summarize_journeys creates a trip table. Even the two point-related tools are clearly separated by whether they target a specific track or a date range.
Naming Consistency5/5
All tools follow the consistent pattern dawarich_<verb>_<noun>. Verbs are either get, list, export, reverse, or summarize, making the action easy to predict. No camelCase or mixed conventions are present.
Tool Count5/5
With 9 tools, the server is well-scoped for a location history integration. Each tool covers a meaningful query or export need without unnecessary redundancy or bloat.
Completeness4/5
The server covers the main read-side workflows: overview stats, timelines, visits, raw points, track details, export in multiple formats, geocoding, and journey summaries. A minor gap is the lack of a direct photo retrieval tool despite timeline mentioning photos, and no write operations, but that appears outside the intended read-only scope.
Maintenance
ActivitySlowing
ResponsivenessNo issues