Metrics Nest
REMOTE · API.METRICSNEST.APP
Ask Claude, ChatGPT or Cursor about your Apple Health data: workouts, sleep, food. Read-only.
Available components
Last scanned (16 hours ago)
Scores higher than 77% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
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. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +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.
- 18 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 +39
- Transport: unverified → pass ▲ security
- 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. security
- MCP protocol: unverified → pass ▲ functional
- 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 functional
- 16 Nov 26 39
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://api.metricsnest.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.metricsnest.app | CN=YR1,O=Let's Encrypt,C=US | 19 Oct 2026 | 17 Jan 2027 | RSA 2048 | SHA256-RSA | 5f7af409d013b0b0505590a4a20c2e275e9 |
| SANs: *.metricsnest.app, metricsnest.app | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.metricsnest.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| metricsnest.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="unauthorized", error_description="Authorization needed", resource_metadata="https://api.metricsnest.app/.well-known/oauth-protected-resource"
Bearer error="unauthorized", error_description="Authorization needed", resource_metadata="https://api.metricsnest.app/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Protected resource metadata
| Document | https://api.metricsnest.app/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.metricsnest.app/mcp |
| Authorisation server | https://pure-paper-48.authkit.app |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.metricsnest.app/mcp | Verified | 200 | |
| http (plaintext) | http://api.metricsnest.app/mcp | HTTPS enforced | 308 | https://api.metricsnest.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
exercise_history Exercise history ~231
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | For a coach: a client id from list_clients, to read that client. Omitted: your own account. |
| exercise | string | yes | An id or name from list_exercises. |
| from | string | – | First day, inclusive. Omitted: all history. |
| to | string | – | Last day, inclusive. |
No output schema declared.
No examples provided.
get_night Get a night ~69
One night in full, including the stage-by-stage hypnogram.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | For a coach: a client id from list_clients, to read that client. Omitted: your own account. |
| wake_date | string | yes | The morning the night ended, YYYY-MM-DD. |
No output schema declared.
No examples provided.
get_profile Profile ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | For a coach: a client id from list_clients, to read that client. Omitted: your own account. |
No output schema declared.
No examples provided.
get_workout Get a workout ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | For a coach: a client id from list_clients, to read that client. Omitted: your own account. |
| id | string | yes | The workout id from list_workouts. |
No output schema declared.
No examples provided.
goal_history Goal history ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | A goal id from list_goals. |
| to | string | – | Last day, inclusive. Omitted: today in the account time zone. |
No output schema declared.
No examples provided.
list_badges List badges ~59
The badges earned in the app, with tier and the time each was earned. Needs the goals category.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | For a coach: a client id from list_clients, to read that client. Omitted: your own account. |
No output schema declared.
No examples provided.
list_clients List clients ~57
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_exercise_catalog List the exercise catalog ~60
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_exercises List exercises ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | For a coach: a client id from list_clients, to read that client. Omitted: your own account. |
No output schema declared.
No examples provided.
list_goals List goals ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | For a coach: a client id from list_clients, to read that client. Omitted: your own account. |
No output schema declared.
No examples provided.
list_meal_proposals List suggested meals ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
list_metrics List metrics ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | For a coach: a client id from list_clients, to read that client. Omitted: your own account. |
No output schema declared.
No examples provided.
list_nights List nights ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_proposals List suggested workouts ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
list_saved_workouts List saved workouts ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | For a coach: a client id from list_clients, to read that client. Omitted: your own account. |
No output schema declared.
No examples provided.
list_workouts List workouts ~170
Workouts with activity, start and end, duration, distance, energy, the heart rate summary and the note. Sets and the route are on get_workout.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
muscle_sets Hard sets per muscle ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
propose_meal Suggest a meal ~307
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | For a coach: a client id from list_clients, to read that client. Omitted: your own account. |
| idempotency_key | string | yes | Unique per suggestion; the same key again returns the first suggestion instead of a duplicate. |
| items | array | yes | The foods on the plate. |
| planned_for | string | yes | 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 | yes | What the meal is, as the person will see it: "Chicken rice bowl". |
No output schema declared.
No examples provided.
propose_removing_saved_workout Suggest removing a saved workout ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | For a coach: a client id from list_clients, to read that client. Omitted: your own account. |
| idempotency_key | string | yes | Unique per suggestion. |
| rationale | string | – | Why it should go, in a sentence or two. |
| saved_workout_id | string | yes | A saved workout id from list_saved_workouts. |
No output schema declared.
No examples provided.
propose_saved_workout Suggest a saved workout ~250
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | In the order they are to be done. |
| idempotency_key | string | yes | 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 | yes | The name it will be saved under: "Leg day". |
No output schema declared.
No examples provided.
propose_workout Suggest a workout ~354
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | In the order they are to be done. |
| idempotency_key | string | yes | Unique per suggestion; the same key again returns the first suggestion instead of a duplicate. |
| planned_for | string | yes | 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 | yes | What the session is, as the person will see it: "Upper body A". |
No output schema declared.
No examples provided.
query_intraday Query hourly readings ~136
Hour-by-hour readings such as heart rate, kept 90 days. One row per metric, hour and device. Needs the intraday category.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
query_logs Query food, drink and weight logs ~207
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
query_metrics Query metrics ~353
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
withdraw_meal_proposal Withdraw a suggested meal ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | For a coach: a client id from list_clients, to read that client. Omitted: your own account. |
| id | string | yes | The suggestion's id. |
No output schema declared.
No examples provided.
withdraw_proposal Withdraw a suggested workout ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | For a coach: a client id from list_clients, to read that client. Omitted: your own account. |
| id | string | yes | The suggestion's id. |
No output schema declared.
No examples provided.
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.
remote · api.metricsnest.app
claude mcp add --transport http app-metricsnest-metrics-nest 'https://api.metricsnest.app/mcp'
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.