io.usefulapi/oura
REMOTE · OURA.USEFULAPI.IO · SCANNED OCT 3
Read sleep, readiness, activity, stress, heart rate and workouts from the Oura Ring.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1057 tokens (~105/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/oura MCP server?
io.usefulapi/oura is a hosted endpoint at https://oura.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · oura.usefulapi.io
claude mcp add --transport http io-usefulapi-oura 'https://oura.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-oura": {
"url": "https://oura.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-oura": {
"type": "http",
"url": "https://oura.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-oura] url = "https://oura.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-oura": {
"type": "remote",
"url": "https://oura.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-oura --url 'https://oura.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-oura:
url: "https://oura.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-oura": {
"Transport": "http",
"Url": "https://oura.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-oura -t streamable-http -u 'https://oura.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-oura": {
"type": "http",
"url": "https://oura.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Oct 26 +1
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 +54
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: 100 functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 29 Sept 26 18
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Oct 2026 · Probed https://oura.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of oura.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://oura.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://oura.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://oura.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://oura.usefulapi.io/mcp |
| Authorisation server | https://oura.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://oura.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://oura.usefulapi.io/mcp | HTTPS enforced | 301 | https://oura.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
oura_create_webhook_subscription Create a webhook subscription ~135
Register a webhook so Oura notifies your callback URL when data changes. Oura verifies the URL before activating it, and the subscription EXPIRES — renew it with oura_renew_webhook_subscription. Oura: POST /v2/webhook/subscription.
| Name | Type | Req | Description |
|---|---|---|---|
| callback_url | string | yes | The HTTPS URL Oura should call. |
| data_type | string | yes | Which collection to watch, e.g. daily_sleep or workout. |
| event_type | string | yes | Which change to be notified about. |
| verification_token | string | yes | A secret Oura echoes back so you can verify the callback. |
No output schema declared.
No examples provided.
oura_delete_webhook_subscription Delete a webhook subscription ~47
Remove a webhook subscription. Notifications stop immediately. Oura: DELETE /v2/webhook/subscription/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | string | yes | The subscription to delete. |
No output schema declared.
No examples provided.
oura_get_document Get one document ~101
Fetch a single document by id from one collection. Ids come from oura_list_documents. Oura: GET /v2/usercollection/{collection}/{document_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Which collection the document belongs to. |
| document_id | string | yes | The document's id. |
| sandbox | boolean | – | Read Oura's synthetic sandbox data instead of the wearer's real data. Use this to learn a response shape without a ring. |
No output schema declared.
No examples provided.
oura_get_heartrate Get heart-rate samples ~180
Fetch individual heart-rate samples over a DATETIME range. This collection is sampled continuously, so it uses start_datetime/end_datetime rather than dates, and can return a great many points — narrow the window or pass latest. Oura: GET /v2/usercollection/heartrate.
| Name | Type | Req | Description |
|---|---|---|---|
| end_datetime | string | – | ISO-8601 end. |
| latest | boolean | – | Return only the most recent sample. |
| next_token | string | – | Cursor from the previous page's next_token. Omit for the first page. |
| sandbox | boolean | – | Read Oura's synthetic sandbox data instead of the wearer's real data. Use this to learn a response shape without a ring. |
| start_datetime | string | – | ISO-8601 start, e.g. 2026-08-01T00:00:00Z. |
No output schema declared.
No examples provided.
oura_get_personal_info Get personal info ~74
Fetch the wearer's profile — age, weight, height, biological sex and email. Oura: GET /v2/usercollection/personal_info.
| Name | Type | Req | Description |
|---|---|---|---|
| sandbox | boolean | – | Read Oura's synthetic sandbox data instead of the wearer's real data. Use this to learn a response shape without a ring. |
No output schema declared.
No examples provided.
oura_get_ring_battery_level Get ring battery level ~137
Fetch ring battery readings over a DATETIME range, or just the latest. Oura: GET /v2/usercollection/ring_battery_level.
| Name | Type | Req | Description |
|---|---|---|---|
| end_datetime | string | – | ISO-8601 end. |
| latest | boolean | – | Return only the most recent reading. |
| next_token | string | – | Cursor from the previous page's next_token. Omit for the first page. |
| sandbox | boolean | – | Read Oura's synthetic sandbox data instead of the wearer's real data. Use this to learn a response shape without a ring. |
| start_datetime | string | – | ISO-8601 start. |
No output schema declared.
No examples provided.
oura_get_webhook_subscription Get one webhook subscription ~53
Fetch a single webhook subscription with its callback URL, event type and expiry. Oura: GET /v2/webhook/subscription/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | string | yes | The subscription's id. |
No output schema declared.
No examples provided.
oura_list_documents List documents from a collection ~228
List documents from one Oura collection over a date range. This is the main read: pick `collection` for what you want — daily_sleep and sleep for sleep, daily_readiness for recovery, daily_activity for movement, daily_stress and daily_resilience for load, workout and session for exercise, daily_spo2, daily_cardiovascular_age and vO2_max for cardiovascular measures, tag and enhanced_tag for the wearer's own annotations, rest_mode_period and ring_configuration for device state. Oura: GET /v2/usercollection/{collection}.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Which document collection to read. |
| end_date | string | – | End of the range, YYYY-MM-DD. |
| next_token | string | – | Cursor from the previous page's next_token. Omit for the first page. |
| sandbox | boolean | – | Read Oura's synthetic sandbox data instead of the wearer's real data. Use this to learn a response shape without a ring. |
| start_date | string | – | Start of the range, YYYY-MM-DD. Defaults to a recent window. |
No output schema declared.
No examples provided.
oura_list_webhook_subscriptions List webhook subscriptions ~34
List the webhook subscriptions registered for the application. Oura: GET /v2/webhook/subscription.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
oura_renew_webhook_subscription Renew a webhook subscription ~68
Extend a webhook subscription's expiry. Oura subscriptions lapse if not renewed, so this is the tool that keeps a live integration alive. Oura: PUT /v2/webhook/subscription/renew/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | string | yes | The subscription to renew. |
No output schema declared.
No examples provided.
What is the io.usefulapi/oura MCP server?
io.usefulapi/oura is an MCP server listed in the public MCP registry as io.usefulapi/oura. Read sleep, readiness, activity, stress, heart rate and workouts from the Oura Ring. This page covers its hosted endpoint (https://oura.usefulapi.io/mcp).
Is the io.usefulapi/oura MCP server safe to use?
io.usefulapi/oura scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.usefulapi/oura MCP server expose?
io.usefulapi/oura exposes 10 tools: oura_get_personal_info, oura_list_documents, oura_get_document, oura_get_heartrate, oura_get_ring_battery_level, and 5 more. Their descriptions and schemas cost roughly 1,057 tokens of context every time the server is loaded.
Does the io.usefulapi/oura MCP server require authentication?
Yes. io.usefulapi/oura asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/oura MCP server still maintained?
io.usefulapi/oura is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.