Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/sushrutb17/doop-showcaseWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/sushrutb17/doop-showcase/whoop-local)<a href="https://agentmods.dev/mcp/sushrutb17/doop-showcase/whoop-local"><img src="https://agentmods.dev/badge/mcp/sushrutb17/doop-showcase/whoop-local/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/sushrutb17/doop-showcase/whoop-local"><img src="https://agentmods.dev/badge/mcp/sushrutb17/doop-showcase/whoop-local.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
whoop-local scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "whoop-local": { "command": "uvx", "args": [ "whoop-local" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 8 lines scan A cb023f59c4fb
whoop-local is an MCP server published in the GitHub repository sushrutb17/doop-showcase (0 stars, last pushed 10d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
google-health-mcp
Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents. Runs locally from the google-health-mcp-unofficial npm package. Needs 8 environment variables to run.
wellness-nourish
Local-first nutrition MCP for AI agents: food, barcode, photo, intake, hydration, goals. Runs locally from the wellness-nourish npm package.
eight-sleep-mcp
Unofficial Eight Sleep MCP server: read sleep trends, temperature, alarms; gated pod control. Runs locally from the eight-sleep-mcp-unofficial npm package. Needs 8 environment variables to run.
wellness-cgm-mcp
Local-first CGM MCP for AI agents: Dexcom Developer API + FreeStyle Libre via LibreLink Up. Runs locally from the wellness-cgm-mcp npm package.
delx-living-body
Meta-MCP that auto-detects installed wellness connectors and composes them into one body data layer. Runs locally from the delx-living-body npm package. Needs 4 environment variables to run.
wellness-cycle-coach
Local-first cycle coach MCP for phase-aware nutrition and training context. Runs locally from the wellness-cycle-coach npm package.