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/davidmosiah/oura-mcpWrote 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/davidmosiah/oura-mcp/ouramcp)<a href="https://agentmods.dev/mcp/davidmosiah/oura-mcp/ouramcp"><img src="https://agentmods.dev/badge/mcp/davidmosiah/oura-mcp/ouramcp/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/davidmosiah/oura-mcp/ouramcp"><img src="https://agentmods.dev/badge/mcp/davidmosiah/oura-mcp/ouramcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ouramcp 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 10d 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
{
"ouramcp": {
"command": "npx",
"args": [
"-y",
"oura-mcp-unofficial"
],
"env": {
"OURA_CLIENT_ID": "",
"OURA_CLIENT_SECRET": "",
"OURA_REDIRECT_URI": "",
"OURA_TOKEN_PATH": "",
"OURA_PRIVACY_MODE": "",
"OURA_CACHE": "",
"OURA_CACHE_PATH": "",
"OURA_NO_CACHE": ""
}
}
}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.
- 10d ago First seen · 19 lines scan A 356728cedac6
ouramcp is an MCP server published in the GitHub repository davidmosiah/oura-mcp (2 stars, last pushed 2d ago), licensed MIT. 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
withingsmcp
Privacy-first, unofficial Withings MCP server for AI health, sleep, activity and heart-rate agents. Runs locally from the withings-mcp-unofficial npm package. Needs 8 environment variables to run.
fitness-tools
Deterministic fitness calculators — TDEE, adaptive TDEE, body fat, 1RM, macros — with consensus. Runs locally from the @almostjacked/fitness-tools-mcp npm package.
apple-health-mcp
Query and analyze Apple Health CSV exports using DuckDB. Runs locally from the @neiltron/apple-health-mcp npm package. Needs 3 environment variables to run.
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.
withings
MCP server for Withings health data — sleep, activity, heart, and body metrics. Remote server at withings-mcp.com.
google-health-fitbit-mcp
Privacy-first Google Health API MCP server for health, sleep, activity and HR agents. Runs locally from the google-health-fitbit-mcp npm package. Needs 8 environment variables to run.