// MCP SERVER RECORD

Oura Ring

Unverified
NPM@yasuakiomokawa/oura-mcp
DRisk gradehigh blast radius
Catalogue entry updated 7 days ago
Auth postureNot probedno remote endpoint probed yet
Tools51 Destructive · 1 Execute · 3 Read
Worst categoryDestructivegrade tracks the peak, not the average
Capability mix
Destructive 1Execute 1Read 3
What it can reach
Ingests untrusted inputTouches secretsReaches networkRuns codeTouches filesChanges permissionsSends external commsPersistsDeletes dataMoves money
Tools 5
oura_clear_authDestructiveHighoura_authenticateExecuteHighoura_api_getReadLowoura_api_list_pathsReadLowoura_auth_statusReadLow
Change history
No changes recorded since first scan. Watched servers surface a diff within the hour.
Recommended policy
oura_clear_authdeny
oura_authenticaterequire approval
Read-only toolsallow
Full policy breakdown with enforcement rules →
// RUNNING THIS SERVER
DIRECT INSTALL npx -y @yasuakiomokawa/oura-mcp

Installed this way, nothing enforces the recommended policy above — calls run exactly as the agent makes them.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.