"Identifying Servers Without Any API Key Configuration" matching MCP servers:

Enables retrieval of InBody body composition data including profile, scan history, and full metrics via MCP tools.

MCP server for Cronometer nutrition tracking, enabling food diary management, nutrition data retrieval, food search, and biometric tracking via Cronometer's mobile REST API.

MCP server for Cronometer nutrition tracking using the mobile API. Enables food logging, nutrition data retrieval, diary management, and fasting tracking.

Enables AI agents to query personal health data collected by any wearable or phone fitness app through Android Health Connect or Apple Health, exposing read-only tools for metrics like heart rate, sleep stages, VO2 max, and body composition. It can run locally over USB with nothing stored, or be self-hosted on Cloudflare Workers with D1 to retain history beyond Health Connect's 30-day limit.

An MCP server that provides an interface to Google's Fitness API, enabling interaction with fitness data through natural language using the Multi-Agent Conversation Protocol.

Enables users to search and retrieve fitness exercise information from the Api Ninjas database. It supports filtering by exercise name, target muscle, type, and difficulty level.

MCP server for the Fitbit Web API with OAuth PKCE, local cache, and trend analysis.

MCP server for the Google Health API: heart rate, activity, sleep, SpO2, HRV, ECG and irregular-rhythm notifications, read into a local SQLite cache for fast offline queries and trend analysis. OAuth 2.0 with automatic token refresh, incremental sync, a cache-only offline mode, and a doctor command that diagnoses a setup without spending quota.

Provides local MCP tools to query your own Xiaomi Mi Fitness health data (sleep, workouts, heart rate, etc.) stored in a local SQLite database, enabling AI assistants to access personal health records without exposing credentials.

Ask your Oura Ring about sleep, readiness, activity, stress and heart rate in ChatGPT or Claude, in any language. Read-only, 10 task-oriented tools; runs in a sandbox demo mode with no credentials.

Exposes the Oura API v2 as an MCP server with tools to query all 19 data collections (e.g., sleep, heartrate) with automatic pagination and explicit truncation warnings.

A stateless MCP server that normalizes strength training logs into a deterministic canonical schema, enabling consumers to build analytics downstream without storing data server-side.

Enables LLM clients to read a user's locally-decrypted calisthenics training data and propose plan updates without direct mutations.

Enables Claude to query personal WHOOP health data including recovery, sleep, strain, workouts, and profile via WHOOP's OAuth 2.0 REST API.

Provides six deterministic, source-attributed hydration calculators (water intake, dehydration check, pregnancy intake, kidney-safe intake, athlete plan, energy optimization) as MCP tools, enabling AI clients to call them via stdio without custom HTTP coding.

MCP server to read daily activity, sleep, heart rate, and body metrics from Google Health API, allowing AI assistants like Claude to access your health data. Optionally syncs health metrics to an Obsidian vault.

MCP server for the Oura Ring API v2, enabling natural language queries about sleep, readiness, activity, heart rate, and more.

Enables Claude to access your personal Strava data read-only, including activities, splits, heart-rate and pace streams, zones, and lifetime totals, so it can coach from real training without manual exports.

A local-first, read-only MCP server that provides compact recovery, sleep, strain, HRV, heart-rate, workout, and body-measurement data from WHOOP without sending credentials to a third party.

A read-only MCP server for the WHOOP API v2 that lets you query and analyze your own recovery, sleep, strain, cycles, and workout data. Note: currently a pre-alpha scaffold with stubbed internals.