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.

C
Limited view
69/100

garmin-mcp

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

Code Verified⚡ Live Monitored: not connected

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

Is this your MCP?

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.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: GARMIN_PASSWORD, MQTT_PASS
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configGARMIN_DB_PATH
configMCP_MAX_ROWS
configMCP_HOSTthe address the server binds inside its own process. Loopback unless set
configMCP_PORT
configENV_FILE
configGARMIN_EMAIL/ GARMIN_PASSWORD your Garmin Connect login
🔐 secretGARMIN_PASSWORDGARMIN_EMAIL / your Garmin Connect login
configGARMINTOKENS
configREFETCH_WINDOW_DAYS
configMAX_CONSECUTIVE_FAILURESgive up on a collector after this many failures in a row, so rate limiting ends the run instead of prolonging it. Default 10
configMAX_DAY_ATTEMPTStries it is recorded in the sync_gaps table and stepped
configFETCH_ACTIVITY_DETAILS
configREQUEST_SLEEPpause between calls. Raise it if you see 429
configBACKFILL_STARTonce you have seen a run work — every extra year is another
configLOG_DIR
configMQTT_HOSToptional Home Assistant status publishing. Empty disables it
configMQTT_PORT
configMQTT_USER
🔐 secretMQTT_PASS
configMQTT_PREFIX
configMQTT_DISCOVERY_PREFIX
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
// quality suggestions

Tool 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.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/object-orient/garmin-sync)](https://m8ven.ai/mcp/object-orient/garmin-sync)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 5d43b01d13bf7e1eafc1d0ef8b675cd8255c0718
code hash: 5d1bdd8a1a0fcaa8bb548e1deae197fa379c30fe8e4afc3cd00dbc7423f1dc5c
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

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
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client