garmin-mcp (Object-Orient/garmin-sync) is an MCP server listed on the M8ven Trust Index. It scores 69 out of 100, grade C. It declares 6 tools. No publisher has claimed this listing.
Read-only MCP server that exposes Garmin Connect health data from a local SQLite database to AI assistants, enabling queries for recent days, sleep, weekly trends, and a guarded SQL query surface.
Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
Limited view: static analysis for Python is partially covered.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
Object-Orient
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
GARMIN_DB_PATHMCP_MAX_ROWSMCP_HOSTthe address the server binds inside its own process. Loopback unless setMCP_PORTENV_FILEGARMIN_EMAIL/ GARMIN_PASSWORD your Garmin Connect loginGARMIN_PASSWORDGARMIN_EMAIL / your Garmin Connect loginGARMINTOKENSREFETCH_WINDOW_DAYSMAX_CONSECUTIVE_FAILURESgive up on a collector after this many failures in a row, so rate limiting ends the run instead of prolonging it. Default 10MAX_DAY_ATTEMPTStries it is recorded in the sync_gaps table and steppedFETCH_ACTIVITY_DETAILSREQUEST_SLEEPpause between calls. Raise it if you see 429BACKFILL_STARTonce you have seen a run work — every extra year is anotherLOG_DIRMQTT_HOSToptional Home Assistant status publishing. Empty disables itMQTT_PORTMQTT_USERMQTT_PASSMQTT_PREFIXMQTT_DISCOVERY_PREFIXDATABASE_URLTool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
6/6 tools missing one or more hints — list_tables (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); describe_table (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); query (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Tool inputs are validated
4/6 tool handlers declare input schemas (67%)
Declare an inputSchema with zod/joi/yup on every tool definition.
Tool handlers catch errors
Only 0/6 tool handlers wrap calls in try/catch (0%)
Wrap each tool handler body in try/catch and return a structured error response.
Tests exist
No test files found
Add tests that exercise each declared tool.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/object-orient/garmin-sync)?variant=verified to the badge URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check