Skip to content

MCP servers › app.metricsnest › metrics-nest

MCP server · registry snapshot 2026-11-17 · last tested 2026-11-17

metrics-nest MCP server

Registry name app.metricsnest/metrics-nest

by metricsnest.app · domain (the registry's namespace rule)Website ↗

Ask Claude, ChatGPT or Cursor about your Apple Health data: workouts, sleep, food. Read-only. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-17version 1.0.1streamable HTTP26 tools

Summary

app.metricsnest/metrics-nest is a remote MCP server listed in the official MCP registry at version 1.0.1, under the namespace of the domain metricsnest.app. On 2026-11-17 ProtocolProbe connected to it in read-only mode and read its inventory: 26 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
26
Last tested
2026-11-17

Tool list size

10,254 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (26 tools). Counted with Anthropic's token counter on 2026-11-17, from the tool list we read on 2026-11-17. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-17 (api.metricsnest.app), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.1).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-17
Mode
read-only (no tool calls)
Latest version
1.0.1, published 2026-11-16 (registry, as of the 2026-11-17 snapshot)
First listed version
2026-11-16 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, all on 2026-11-16; 2 in the 90 days before the 2026-11-17 snapshot.
Most recent 2 versions
  • 1.0.1 · 2026-11-16
  • 1.0.0 · 2026-11-16
(versions still listed in the registry only)
Registry data
snapshot 2026-11-17
Package and repository
checked 2026-11-17
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-16, listed on 2026-11-17 with version 1.0.1 (published 2026-11-16).

Source: the official MCP Registry list on 2026-11-16 and on 2026-11-17.

What it is

What does this server offer?

Observed inventory
26tools
0resources
0prompts

None of its 26 tools are described as changing anything. For 26 the reading was uncertain, so no mark is shown.

  • “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 syn…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • “Every metric there is a figure for, with its unit and the first and last day.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • query_metricson 6 other servers

    “Each day's figures as the Metrics Nest app shows them, or weekly or monthly buckets.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    7 inputs
    • metricstring“A metric name from list_metrics.”
    • fromstring“First day, inclusive.”
    • tostring“Last day, inclusive.”
    • granularitystring“day (default) returns each day; week and month one row per bucket: the average as numValue, and bucket.min, max, sum and count.”
    • cursorstring“The cursor from the previous page, to continue.”
    • limitinteger“Rows per page, 1 to 500.”
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • query_intraday

    “Hour-by-hour readings such as heart rate, kept 90 days.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs
    • metricstring“A metric name from list_metrics.”
    • datestring“One day.”
    • devicestring
    • cursorstring“The cursor from the previous page, to continue.”
    • limitinteger“Rows per page, 1 to 500.”
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • list_nights

    “One row per night, keyed by the morning it ended on: bed and wake times, and seconds asleep and in each stage.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    5 inputs
    • fromstring“First day, inclusive.”
    • tostring“Last day, inclusive.”
    • cursorstring“The cursor from the previous page, to continue.”
    • limitinteger“Rows per page, 1 to 500.”
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • get_night

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

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • wake_datestringrequired“The morning the night ended, YYYY-MM-DD.”
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • list_workoutson 2 other servers

    “Workouts with activity, start and end, duration, distance, energy, the heart rate summary and the note.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs
    • activitystring
    • fromstring“First day, inclusive.”
    • tostring“Last day, inclusive.”
    • cursorstring“The cursor from the previous page, to continue.”
    • limitinteger“Rows per page, 1 to 500.”
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • idstringrequired“The workout id from list_workouts.”
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    7 inputs
    • kindstring
    • part_of_daystring
    • fromstring“First day, inclusive.”
    • tostring“Last day, inclusive.”
    • cursorstring“The cursor from the previous page, to continue.”
    • limitinteger“Rows per page, 1 to 500.”
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • list_exerciseson 6 other servers

    “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 …”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • exercise_historyon 1 other server

    “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 mo…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 1 required
    • exercisestringrequired“An id or name from list_exercises.”
    • fromstring“First day, inclusive.”
    • tostring“Last day, inclusive.”
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • muscle_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 g…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • fromstring“First day, inclusive.”
    • tostring“Last day, inclusive.”
    • clientstring“For a coach: a client id from list_clients, to read that client.”
Show 14 more tools
  • “For a coach: the people who approved you as their coach, with what each lets you read and from when.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • “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 com…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • 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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 1 required
    • idstringrequired“A goal id from list_goals.”
    • fromstring“First day, inclusive.”
    • tostring“Last day, inclusive.”
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • list_badges

    “The badges earned in the app, with tier and the time each was earned.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • propose_workout

    “Suggest a workout for the person to approve in the Metrics Nest app.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    7 inputs, 4 required
    • idempotency_keystringrequired“Unique per suggestion; the same key again returns the first suggestion instead of a duplicate.”
    • titlestringrequired“What the session is, as the person will see it: "Upper body A".”
    • activitystring“strength (default), run, ride, hike, swim, row, yoga, hiit or other.”
    • planned_forstringrequired“The day it is meant for, in the account time zone: today up to 28 days ahead.”
    • rationalestring“Why this session, in a few sentences the person reads before approving.”
    • exercisesarrayrequired“In the order they are to be done.”
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • list_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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • 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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • 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).”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    6 inputs, 3 required
    • idempotency_keystringrequired“Unique per suggestion; the same key again returns the first suggestion instead of a duplicate.”
    • titlestringrequired“The name it will be saved under: "Leg day".”
    • activitystring“strength (default), run, ride, hike, swim, row, yoga, hiit or other.”
    • rationalestring“Why this workout, in a few sentences the person reads before approving.”
    • exercisesarrayrequired“In the order they are to be done.”
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • propose_removing_saved_workout

    “Suggest taking one of the person's saved workouts away.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    4 inputs, 2 required
    • idempotency_keystringrequired“Unique per suggestion.”
    • saved_workout_idstringrequired“A saved workout id from list_saved_workouts.”
    • rationalestring“Why it should go, in a sentence or two.”
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • list_proposalson 18 other servers

    “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).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • statusstring
    • limitinteger“How many, newest first.”
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • withdraw_proposalon 3 other servers

    “Take back a workout this connection suggested that the person has not answered yet: it leaves their list in the app.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • idstringrequired“The suggestion's id.”
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • propose_meal

    “Suggest a meal for the person to approve in the Metrics Nest app.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    7 inputs, 4 required
    • idempotency_keystringrequired“Unique per suggestion; the same key again returns the first suggestion instead of a duplicate.”
    • titlestringrequired“What the meal is, as the person will see it: "Chicken rice bowl".”
    • slotstring“Which meal of the day it is for.”
    • planned_forstringrequired“The day it is meant for, in the account time zone: today up to 28 days ahead.”
    • rationalestring“Why this meal, in a few sentences the person reads before approving.”
    • itemsarrayrequired“The foods on the plate.”
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • list_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).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • statusstring
    • limitinteger“How many, newest first.”
    • clientstring“For a coach: a client id from list_clients, to read that client.”
  • withdraw_meal_proposal

    “Take back a meal this connection suggested that the person has not answered yet: it leaves their list in the app.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • idstringrequired“The suggestion's id.”
    • clientstring“For a coach: a client id from list_clients, to read that client.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-17.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
93% of 86
Tools with a description
100% of 26
Typical description length
315 characters

The tool set

Counted from the listing

Tools
26
Size of the list
about 7,436 tokens for an agent to load (characters ÷ 4)
Naming
26 of 26 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 26 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-17 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://api.metricsnest.app/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "metrics-nest": {
      "url": "https://api.metricsnest.app/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "metrics-nest": {
      "type": "http",
      "url": "https://api.metricsnest.app/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"metrics-nest","type":"http","url":"https://api.metricsnest.app/mcp"}'
Claude Code
claude mcp add --transport http metrics-nest https://api.metricsnest.app/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "metrics-nest": {
      "type": "streamableHttp",
      "url": "https://api.metricsnest.app/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "metrics-nest": {
      "httpUrl": "https://api.metricsnest.app/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.metrics-nest]
url = "https://api.metricsnest.app/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "metrics-nest": {
      "url": "https://api.metricsnest.app/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://api.metricsnest.app/mcp --transport http
  • Optional settings the entry also lists (left out above): Authorization.
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-17. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-17. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-17. Source: read 2026-11-17.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-17. Source: read 2026-11-17.

Own host

  • security.txt. No security.txt at https://api.metricsnest.app/.well-known/ (HTTP 404, 2026-11-17). No security.txt at https://www.metricsnest.app/.well-known/ (HTTP 404, 2026-11-17). Source: api.metricsnest.app/.well-known/security.txt · read 2026-11-17.
  • A2A agent card. No A2A agent card at https://api.metricsnest.app/.well-known/ (HTTP 404, 2026-11-17). No A2A agent card at https://www.metricsnest.app/.well-known/ (HTTP 404, 2026-11-17). Source: api.metricsnest.app/.well-known/agent-card.json · read 2026-11-17.

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint api.metricsnest.app/mcpSession openedmatchesour test · 2026-11-17
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-17

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-17. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about app.metricsnest/metrics-nest

Answered from the data above

Who publishes app.metricsnest/metrics-nest?

The registry ties the namespace app.metricsnest to the domain metricsnest.app; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does app.metricsnest/metrics-nest need an API key or sign-in?

It opened a session without any credential on 2026-11-17. The registry entry declares no required credential; no declaration is not a guarantee.

Has app.metricsnest/metrics-nest been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (no operator permission)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-17
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-17, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 955 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 26 tools, 0 resources, 0 prompts.
  4. 4,778 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-17; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-11-17
MCP capability
tools
our test · 2026-11-17
Transport
streamable HTTP
registry · 2026-11-17
Required credentials
none declared
registry · 2026-11-17 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-17
Lifecycle status
registry · 2026-11-17
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-17

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “app.metricsnest/metrics-nest: MCP server record.” Data checked 2026-11-17. https://protocolprobe.com/mcp/servers/app.metricsnest/metrics-nest

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/app.metricsnest/metrics-nest)](https://protocolprobe.com/mcp/servers/app.metricsnest/metrics-nest)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology