# io.github.proscar87/oura-mcp (pypi · mcp-oura)

The Oura v2 API as an MCP server. Paginates, fixes the date range, warns when data is missing.

- Trust score: 54/100 (low)
- Change this week: −13
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-18

## Components

- pypi · `mcp-oura`: 54/100 (this document), [markdown](https://verifymcp.io/servers/proscar87-oura-mcp/mcp-oura.md), [page](https://verifymcp.io/servers/proscar87-oura-mcp/mcp-oura)

## Channel facts

- Registry: `pypi`
- Package: `mcp-oura`
- Version: `0.3.3`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-18.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 2 of 30 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 881 tokens (~220/item across 4 items; 3 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: the tool surface changed between 0.2.0 and 0.3.3: 3 tool removals, 0 breaking changes, 3 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### Claude

```bash
claude mcp add proscar87-oura-mcp -- uvx mcp-oura
```

### Codex

```bash
codex mcp add proscar87-oura-mcp -- uvx mcp-oura
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "proscar87-oura-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "mcp-oura"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add proscar87-oura-mcp --command uvx --arg mcp-oura
```

### Hermes

```yaml
mcp_servers:
  proscar87-oura-mcp:
    command: "uvx"
    args: ["mcp-oura"]
```

### Other

```json
{
  "mcpServers": {
    "proscar87-oura-mcp": {
      "command": "uvx",
      "args": [
        "mcp-oura"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-18 (score 54, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.3.2 → 0.3.3

### 2026-08-12 (score 69, +2)

- [functional improvement] Schema quality: 262 → 220
- [functional] First check of Schema quality: 100
- [functional] Schema quality: excellent → good
- [functional] Package version: 0.3.1 → 0.3.2

### 2026-08-11 (score 67, +15)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-10 (score 52, −8)

- [security regression] Stability: unverified → fail
- [security regression] Malware scan: pass → unverified
- [functional improvement] Schema quality: 287 → 256
- [functional] Schema quality: poor → excellent
- [functional] Package version: 0.2.0 → 0.3.1
- [functional] Package version: 0.2.0 → 0.3.0

### 2026-08-09 (score 60)

First indexed and scored.

## MCP tools (3)

### `oura_collections` (~43 tokens)

Oura collection catalog

The 19 Oura collections, what each one carries and which parameters it takes.

Use it before `oura_query` if you are unsure of the exact name.

### `oura_query` (~358 tokens)

Query an Oura collection

Fetches a COMPLETE Oura collection over the requested range.

Follows pagination to the end: Oura returns `next_token` and whoever doesn't
chase it receives the first page with nothing saying so. One local day of
\`heartrate` is 1,231 samples across 2 pages; a month, ~37,000.

The range is INCLUSIVE on both ends: equal `start` and `end` return that
day. Oura does not behave that way — some collections exclude the last day
and others don't, and `workout` is skewed to UTC — but that is corrected
here.

Date-range collections use YYYY-MM-DD. `heartrate` and `ring_battery_level`
use ISO 8601 with time. `personal_info` and `ring_configuration` take no
range.

Input parameters:

- `collection` (string, required): Exact name. See `oura_collections` if you are unsure.
- `day`: Shorthand for a single day: equivalent to start=end=day.
- `end`: YYYY-MM-DD, or ISO 8601 with time
- `fields`: Only these fields. Oura trims on its side, so less comes down: use it on long heartrate ranges. `day` and `id` always come back.
- `format` (string): `json` (default) or `csv`. CSV for large volumes: a month of heartrate is ~37,000 records and in JSON the keys repeat 37,000 times.
- `latest` (boolean): Only the most recent record. heartrate and ring_battery_level only; it needs no range.
- `start`: YYYY-MM-DD, or ISO 8601 with time

### `oura_check` (~63 tokens)

Self-check of the Oura connection

Self-check: is there a credential, and does Oura respond? Exposing nothing.

Returns neither the token nor any health value. It reports the token's
LENGTH, never the token: diagnostic messages are the ones most often copied
into chats and issues.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/proscar87-oura-mcp/mcp-oura#diagnostics

## Score history

- 2026-08-18: 54
- 2026-08-17: 69
- 2026-08-16: 69
- 2026-08-15: 69
- 2026-08-14: 69
- 2026-08-13: 69
- 2026-08-12: 69
- 2026-08-11: 67
- 2026-08-10: 52
- 2026-08-09: 60

## Links

- PyPI project: https://pypi.org/project/mcp-oura/
- Socket report: https://socket.dev/pypi/package/mcp-oura
- Repository: https://github.com/proscar87/oura-mcp
- Changelog RSS feed: https://verifymcp.io/servers/proscar87-oura-mcp/mcp-oura.xml
- Changelog JSON feed: https://verifymcp.io/servers/proscar87-oura-mcp/mcp-oura.json
- HTML version of this page: https://verifymcp.io/servers/proscar87-oura-mcp/mcp-oura