Reviews
No review yet. Used Metrics Nest? Be the first to help others choose.What it does
Metrics Nest is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2h ago (live check)Hosted endpoint
https://api.metricsnest.app/mcpstreamable-http
In Claude Code: claude mcp add --transport http metrics-nest https://api.metricsnest.app/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"metrics-nest": {
"url": "https://api.metricsnest.app/mcp"
}
}
}Reliability
Re-tested about every 3 days · last check 2h agoObserved endpoint availability: the share of our conclusive checks that got an answer. A request for a key or sign-in counts as an answer (the server is up, its access is protected). Timeouts, unreachable endpoints, server errors and invalid MCP replies count as failures; rate-limited checks and checks during our own incidents are not counted. This is what we observed at each check, not continuous uptime: an outage between two checks may go unseen. The 90-day figure will appear once 90 days of checks exist (checks since 16 Nov 2026). How we measure
Tool changes
Tool tracking since 20 Nov 2026 · test history since 16 Nov 2026No tool added or removed since tracking started. 26 tools in the latest list.
Changes are confirmed by comparing complete tool lists only, read about every 3 days, and dated by the day we saw them. A renamed tool appears as one removal and one addition.
Live check
Electra Index connected to the hosted endpoint 2h agoONLINE Metrics Nest answered an MCP connection on 21 Nov 2026 and introduced itself as metricsnest 1 (MCP protocol 2025-06-18).
26 tools offered to AI assistants
get_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 thislist_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.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 wquery_intraday· Hour-by-hour readings such as heart rate, kept 90 days. One row per metric, hour and device. Needs the intraday category.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.get_night· One night in full, including the stage-by-stage hypnogram.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.get_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.query_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 daylist_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 perexercise_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 tmuscle_sets· 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 rec
Show 14 more
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· 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.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.list_badges· The badges earned in the app, with tier and the time each was earned. Needs the goals category.propose_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 dlist_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· 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.propose_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 firspropose_removing_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.list_proposals· 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 namwithdraw_proposal· 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.propose_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 crelist_meal_proposals· 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 mwithdraw_meal_proposal· 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.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Re-tested about every 3 days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Website | https://www.metricsnest.app/apple-health-ai | DECLARED | SRC-001 Official MCP Registry | 4d ago |
| Version | 1.0.1 | DECLARED | SRC-001 Official MCP Registry | 4d ago |
| Hosted endpoint | https://api.metricsnest.app/mcp | DECLARED | SRC-001 Official MCP Registry | 4d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 4d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 4d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 4d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 4d ago |
Change history
- VERSION16 Nov 20261.0.0 → 1.0.1
- NEW16 Nov 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Metrics Nest still online?
Free alerts · no account▲ 0Do you run Metrics Nest? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Metrics Nest
How do I connect Metrics Nest?
Use the hosted endpoint https://api.metricsnest.app/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Metrics Nest offer?
When Electra Index connected on 21 Nov 2026, it listed 26 tools: get_profile, list_metrics, query_metrics, query_intraday, list_nights, get_night, list_workouts, get_workout and more. The full list is in "Live check" above.
Is Metrics Nest online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 2h ago.