# Metrics Nest (remote · api.metricsnest.app)

Ask Claude, ChatGPT or Cursor about your Apple Health data: workouts, sleep, food. Read-only.

- Trust score: 80/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.metricsnest.app`: 80/100 (this document), [markdown](https://verifymcp.io/servers/app-metricsnest-metrics-nest/api.md), [page](https://verifymcp.io/servers/app-metricsnest-metrics-nest/api)

## Channel facts

- Endpoint: `https://api.metricsnest.app/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 4256 tokens (~163/item across 26 items; 26 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Metrics Nest MCP server?

Metrics Nest is a hosted endpoint at https://api.metricsnest.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http app-metricsnest-metrics-nest 'https://api.metricsnest.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-metricsnest-metrics-nest": {
      "url": "https://api.metricsnest.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-metricsnest-metrics-nest": {
      "type": "http",
      "url": "https://api.metricsnest.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-metricsnest-metrics-nest]
url = "https://api.metricsnest.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-metricsnest-metrics-nest": {
      "type": "remote",
      "url": "https://api.metricsnest.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-metricsnest-metrics-nest --url 'https://api.metricsnest.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-metricsnest-metrics-nest:
    url: "https://api.metricsnest.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-metricsnest-metrics-nest": {
      "Transport": "http",
      "Url": "https://api.metricsnest.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-metricsnest-metrics-nest -t streamable-http -u 'https://api.metricsnest.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-metricsnest-metrics-nest": {
      "type": "http",
      "url": "https://api.metricsnest.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 79, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 78, +39)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 93
- [functional] First check of Destructive annotations: 100
- [functional] First check of Schema quality: good

### 2026-11-16 (score 39)

First indexed and scored.

## MCP tools (26)

### `get_profile` (~116 tokens)

Profile

The account behind this key: its plan, the days this key may read (meta.history_floor and history_ceiling, null when open), the categories this key may read, the paired devices and when each last synced, the account time zone, and when this share expires (expires_at: past it, every call fails until the person renews the share in the app). Call this first.

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.

### `list_metrics` (~66 tokens)

List metrics

Every metric there is a figure for, with its unit and the first and last day. Use the exact metric names from here in query_metrics.

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.

### `query_metrics` (~353 tokens)

Query metrics

Each day's figures as the Metrics Nest app shows them, or weekly or monthly buckets. One row per metric and day (one per reading for metrics read reading by reading), already combined: food and water include what was logged in the app and what other apps wrote to Health, so never add rows together. Paged: follow next_cursor while it is set; meta.truncated names the days a page covers when there are more. A window outside what the share allows is narrowed to it (meta.history_floor and history_ceiling).

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.
- `cursor` (string): The cursor from the previous page, to continue.
- `from` (string): First day, inclusive. Omitted: six days before `to`, so the last seven days only. Pass it for anything longer, up to 366 days per call.
- `granularity` (string): day (default) returns each day; week and month one row per bucket: the average as numValue, and bucket.min, max, sum and count. For a total such as steps or kcal in a week, read bucket.sum. Use week…
- `limit` (integer): Rows per page, 1 to 500.
- `metric` (string): A metric name from list_metrics. Omitted: all metrics, which pages a lot.
- `to` (string): Last day, inclusive. Omitted: today in the account time zone.

### `query_intraday` (~136 tokens)

Query hourly readings

Hour-by-hour readings such as heart rate, kept 90 days. One row per metric, hour and device. Needs the intraday category.

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.
- `cursor` (string): The cursor from the previous page, to continue.
- `date` (string): One day. Omitted: the most recent hours.
- `device` (string)
- `limit` (integer): Rows per page, 1 to 500.
- `metric` (string): A metric name from list_metrics.

### `list_nights` (~174 tokens)

List nights

One row per night, keyed by the morning it ended on: bed and wake times, and seconds asleep and in each stage. With several devices, the longest sleep is the night. get_night has the stages.

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.
- `cursor` (string): The cursor from the previous page, to continue.
- `from` (string): First day, inclusive. Omitted: 365 days before `to`, the most one call covers. For older rows, call again with an earlier `to`.
- `limit` (integer): Rows per page, 1 to 500.
- `to` (string): Last day, inclusive. Omitted: today in the account time zone.

### `get_night` (~69 tokens)

Get a night

One night in full, including the stage-by-stage hypnogram.

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.
- `wake_date` (string, required): The morning the night ended, YYYY-MM-DD.

### `list_workouts` (~170 tokens)

List workouts

Workouts with activity, start and end, duration, distance, energy, the heart rate summary and the note. Sets and the route are on get_workout.

Input parameters:

- `activity` (string)
- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.
- `cursor` (string): The cursor from the previous page, to continue.
- `from` (string): First day, inclusive. Omitted: 365 days before `to`, the most one call covers. For older rows, call again with an earlier `to`.
- `limit` (integer): Rows per page, 1 to 500.
- `to` (string): Last day, inclusive. Omitted: today in the account time zone.

### `get_workout` (~92 tokens)

Get a workout

One workout in full: the heart rate trace (average bpm and how many readings, minute by minute from the start) and zones, and the exercises and sets and the route when they were shared.

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.
- `id` (string, required): The workout id from list_workouts.

### `query_logs` (~207 tokens)

Query food, drink and weight logs

What the person logged in the app: food with calories, macros and fruit and veg portions, drinks by kind (coffee, water, alcohol...), and typed weight. Each entry carries its time and part of day: morning, midday, evening or late. For a day's totals, use query_metrics.

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.
- `cursor` (string): The cursor from the previous page, to continue.
- `from` (string): First day, inclusive. Omitted: six days before `to`, so the last seven days only. Pass it for anything longer, up to 366 days per call.
- `kind` (string)
- `limit` (integer): Rows per page, 1 to 500.
- `part_of_day` (string)
- `to` (string): Last day, inclusive. Omitted: today in the account time zone.

### `list_exercises` (~118 tokens)

List exercises

Every exercise logged in a workout (bench press, squat...), most recently done first, with how many workouts it was in, the first and last day, the heaviest weight lifted in kg (best_weight_kg), and the muscles it trains (null where the person never said, for an exercise of their own). Use an id or name from here in exercise_history. Needs the sets category.

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.

### `exercise_history` (~231 tokens)

Exercise history

How one exercise has gone over time, as the app's exercise screen shows it: every workout it was in, newest first, with the sets (weight kg, reps, RPE, time s, distance m, and reps_left — how many more reps the set had in it, which is how the app asks effort), the best set (the heaviest, then most reps) and its weight in kg (top_weight_kg), volume, mean RPE, hard sets (within three reps of failure) and whether it was a PR (heavier, or the same weight for more reps). Nothing is estimated. For "how is my bench press improving", read top_weight_kg and best_set over time. Needs the sets category.

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.
- `exercise` (string, required): An id or name from list_exercises.
- `from` (string): First day, inclusive. Omitted: all history.
- `to` (string): Last day, inclusive.

### `muscle_sets` (~181 tokens)

Hard sets per muscle

Which muscles the training landed on over a window (default the last 7 days): hard sets per muscle — sets within three reps of failure, or unrated — read against the 10–20 per week most hypertrophy guidance uses, which muscles are still recovering (two or more hard sets in the last 48 hours), and exercises whose sets were not counted because the person never said what they train. For "what have I been training" or "what should I train next". Needs the sets category.

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.
- `from` (string): First day, inclusive. Omitted: six days before `to`.
- `to` (string): Last day, inclusive. Omitted: today in the account time zone.

### `list_clients` (~57 tokens)

List clients

For a coach: the people who approved you as their coach, with what each lets you read and from when. Pass a client id as `client` to any other tool to read that person. A client who stopped sharing shows as ended.

### `list_goals` (~90 tokens)

List goals

The goals set in the app: daily or weekly targets on a metric (a calorie ceiling, a water or step target) and journeys toward a value (a weight to reach), each with its progress as the phone last computed it. Needs the goals category.

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.

### `goal_history` (~169 tokens)

Goal history

One goal's progress day by day, newest first: the figure, the fraction of the way there and whether it was met, as the phone computed it on each sync. Use it for how a goal has gone, not only where it stands. The id is from list_goals.

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.
- `from` (string): First day, inclusive. Omitted: 365 days before `to`, the most one call covers. For older rows, call again with an earlier `to`.
- `id` (string, required): A goal id from list_goals.
- `to` (string): Last day, inclusive. Omitted: today in the account time zone.

### `list_badges` (~59 tokens)

List badges

The badges earned in the app, with tier and the time each was earned. Needs the goals category.

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.

### `propose_workout` (~354 tokens)

Suggest a workout

Suggest a workout for the person to approve in the Metrics Nest app. This only leaves a suggestion: nothing is planned until they approve it on their phone, where they can also edit or reject it, and no workout is ever created, changed or deleted here. Call list_exercises first and give each exercise its exercise_id from there whenever it is one they have done; for one they have not, take its exercise_id from list_exercise_catalog when the app has it, and otherwise leave exercise_id out and give the name. Weights are kg. Make up a new idempotency_key for each suggestion and send the same one only when retrying this exact call: a retry answers the suggestion already made instead of making a second. Works only where the person allowed this connection to suggest workouts (get_profile says can_propose). list_proposals shows what became of each suggestion.

Input parameters:

- `activity` (string): strength (default), run, ride, hike, swim, row, yoga, hiit or other.
- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.
- `exercises` (array, required): In the order they are to be done.
- `idempotency_key` (string, required): Unique per suggestion; the same key again returns the first suggestion instead of a duplicate.
- `planned_for` (string, required): The day it is meant for, in the account time zone: today up to 28 days ahead.
- `rationale` (string): Why this session, in a few sentences the person reads before approving.
- `title` (string, required): What the session is, as the person will see it: "Upper body A".

### `list_exercise_catalog` (~60 tokens)

List the exercise catalog

Every exercise the Metrics Nest app offers, with the exercise_id propose_workout takes for it, its name and other names, its group, and the muscles it trains. The same for everybody; list_exercises is what this person has actually done.

### `list_saved_workouts` (~92 tokens)

List saved workouts

The workouts the person saved in the Metrics Nest app to start whenever they like ("Leg day", "Push A"), each with its id, exercises, sets and reps. propose_removing_saved_workout takes the id; propose_saved_workout adds a new one.

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.

### `propose_saved_workout` (~250 tokens)

Suggest a saved workout

Suggest a named workout for the person to keep and start whenever they like ("Leg day"), rather than a session on one day (that is propose_workout). Nothing is saved until they approve it in the Metrics Nest app, where they can edit it first. Same exercises as propose_workout: exercise_id from list_exercises or list_exercise_catalog where there is one. Make up a new idempotency_key for each suggestion. Works only where the person allowed this connection to suggest (get_profile says can_propose).

Input parameters:

- `activity` (string): strength (default), run, ride, hike, swim, row, yoga, hiit or other.
- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.
- `exercises` (array, required): In the order they are to be done.
- `idempotency_key` (string, required): Unique per suggestion; the same key again returns the first suggestion instead of a duplicate.
- `rationale` (string): Why this workout, in a few sentences the person reads before approving.
- `title` (string, required): The name it will be saved under: "Leg day".

### `propose_removing_saved_workout` (~130 tokens)

Suggest removing a saved workout

Suggest taking one of the person's saved workouts away. Nothing is removed until they approve it in the Metrics Nest app; the workouts already done from it stay. The id is from list_saved_workouts.

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.
- `idempotency_key` (string, required): Unique per suggestion.
- `rationale` (string): Why it should go, in a sentence or two.
- `saved_workout_id` (string, required): A saved workout id from list_saved_workouts.

### `list_proposals` (~170 tokens)

List suggested workouts

The workouts suggested through this connection, newest first, and what became of each: pending, approved, rejected, or expired (unanswered for a week, or past its day). action says which kind each was: plan (a session on a day), save (a named workout to keep) or remove (a saved one taken away). For an approved one, approved_exercises is what the person approved and edited says whether they changed it; workout_ids are the workouts it was run as, and get_workout has what was actually done.

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.
- `limit` (integer): How many, newest first. Default 50.
- `status` (string)

### `withdraw_proposal` (~97 tokens)

Withdraw a suggested workout

Take back a workout this connection suggested that the person has not answered yet: it leaves their list in the app. One they approved, rejected or that expired stays as it is. The id is from propose_workout or list_proposals.

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.
- `id` (string, required): The suggestion's id.

### `propose_meal` (~307 tokens)

Suggest a meal

Suggest a meal for the person to approve in the Metrics Nest app. This only leaves a suggestion: nothing is logged until they approve it and then log it from their phone, where they can change it on the plate first; no log entry is ever created, changed or deleted here. Give each food a name and, where you can, its grams and its calories and macros for that portion; leave out any figure you do not know rather than guessing. Make up a new idempotency_key for each suggestion and send the same one only when retrying this exact call. Works only where the person allowed this connection to suggest (get_profile says can_propose). list_meal_proposals shows what became of each suggestion.

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.
- `idempotency_key` (string, required): Unique per suggestion; the same key again returns the first suggestion instead of a duplicate.
- `items` (array, required): The foods on the plate.
- `planned_for` (string, required): The day it is meant for, in the account time zone: today up to 28 days ahead.
- `rationale` (string): Why this meal, in a few sentences the person reads before approving.
- `slot` (string): Which meal of the day it is for.
- `title` (string, required): What the meal is, as the person will see it: "Chicken rice bowl".

### `list_meal_proposals` (~141 tokens)

List suggested meals

The meals suggested through this connection, newest first, and what became of each: pending, approved, rejected, or expired (unanswered for a week, or past its day). log_ids are the food entries it was eaten as — query_logs has them, with meal_id set to the suggestion's id, and they say what was actually eaten, which may differ from what was suggested.

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.
- `limit` (integer): How many, newest first. Default 50.
- `status` (string)

### `withdraw_meal_proposal` (~101 tokens)

Withdraw a suggested meal

Take back a meal this connection suggested that the person has not answered yet: it leaves their list in the app. One they approved, rejected or that expired stays as it is. The id is from propose_meal or list_meal_proposals.

Input parameters:

- `client` (string): For a coach: a client id from list_clients, to read that client. Omitted: your own account.
- `id` (string, required): The suggestion's id.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-metricsnest-metrics-nest/api#diagnostics

## Score history

- 2026-11-21: 80
- 2026-11-20: 80
- 2026-11-19: 79
- 2026-11-18: 79
- 2026-11-17: 78
- 2026-11-16: 39

## Common questions

### What is the Metrics Nest MCP server?

Metrics Nest is an MCP server listed in the public MCP registry as app.metricsnest/metrics-nest. Ask Claude, ChatGPT or Cursor about your Apple Health data: workouts, sleep, food. Read-only. This page covers its hosted endpoint (https://api.metricsnest.app/mcp).

### Is the Metrics Nest MCP server safe to use?

Metrics Nest scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Metrics Nest MCP server expose?

Metrics Nest exposes 26 tools: get_profile, list_metrics, query_metrics, query_intraday, list_nights, and 21 more. Their descriptions and schemas cost roughly 3,990 tokens of context every time the server is loaded.

### Does the Metrics Nest MCP server require authentication?

Yes. Metrics Nest asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Metrics Nest MCP server still maintained?

Metrics Nest is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Metrics Nest MCP server?

VerifyMCP ran 13 checks on Metrics Nest, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.metricsnest.app/mcp
- Website: https://www.metricsnest.app/apple-health-ai
- Changelog RSS feed: https://verifymcp.io/servers/app-metricsnest-metrics-nest/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-metricsnest-metrics-nest/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-metricsnest-metrics-nest/api.json
- HTML version of this page: https://verifymcp.io/servers/app-metricsnest-metrics-nest/api
