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/AntVsl/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/antvsl/oura_mcp/oura-mcp)<a href="https://agentmods.dev/mcp/antvsl/oura_mcp/oura-mcp"><img src="https://agentmods.dev/badge/mcp/antvsl/oura_mcp/oura-mcp/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/antvsl/oura_mcp/oura-mcp"><img src="https://agentmods.dev/badge/mcp/antvsl/oura_mcp/oura-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
oura-mcp 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
{
"oura-mcp": {
"command": "uvx",
"args": [
"my-oura-mcp"
],
"env": {
"OURA_CLIENT_ID": "",
"OURA_CLIENT_SECRET": "",
"OURA_REDIRECT_URI": "http://localhost:8765/callback",
"OURA_API_MODE": "sandbox",
"OURA_TZ": "UTC",
"OURA_TOKEN_STORE": ".oura/tokens.json",
"OURA_PUBLIC_URL": "",
"OURA_OAUTH_ALLOWED_REDIRECT_ORIGINS": ""
}
}
}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 · 18 lines scan A d1d010fe8353
oura-mcp is an MCP server published in the GitHub repository AntVsl/oura_mcp (0 stars, last pushed 11d 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
vitamind
MCP server for solar vitamin D: when the sun where you are can actually make vitamin D, for your skin type. Real solar geometry and live UV data. Runs locally from the vitamind-mcp npm package.
supstack
Evidence-based supplement research, dosing, safety, and interactions as agent-callable tools. Runs locally from the @supstack/cli npm package.
vitamind
Know when the sun can make vitamin D where you are, for your skin type. Live UV data. Remote server at getvitamind.app.
vari-mcp
6 hydration calculators for LLMs: water intake, dehydration, pregnancy, CKD, athlete, energy. Runs locally from the @getvari/mcp npm package.
whoop-mcp
Privacy-first, unofficial WHOOP MCP server for AI health, sleep, recovery, and performance agents. Runs locally from the whoop-mcp-unofficial npm package. Needs 8 environment variables to run.
ouramcp
Privacy-first, unofficial Oura MCP server for AI health, sleep, activity and heart-rate agents. Runs locally from the oura-mcp-unofficial npm package. Needs 8 environment variables to run.