mcp-oura

MCPcommunity
v0.4.0io.github.proscar87UnknownUpdated 8d agoGitHub

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

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
8d agoLast update
Reads these credentials
  • OURA_CLIENT_SECRETOAuth appoptional

    client_secret of your Oura application. Only needed when running `oura-mcp --authorize` and when refreshing the token.

  • OURA_CREDENTIALSAPI keyoptional

    Where the OAuth2 credentials file lives. Defaults to ~/.config/oura-mcp/credentials.json, mode 600.

  • OURA_PATAPI keyoptional

    Oura Personal Access Token. Only if you already had one: Oura stopped issuing them in December 2025.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.proscar87
LicenseUnknown
Version0.4.0
Sourcemcp-registry
GitHubproscar87/oura-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface3 tools · none privileged
Security scan✓ Cleanv0.3.3 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 11, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

3 tools · none privileged
Statically extracted from the published packagev0.3.3 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

oura_collectionsNo description published

This tool published no description. Forge does not invent one.

oura_queryNo description published

This tool published no description. Forge does not invent one.

oura_checkNo description published

This tool published no description. Forge does not invent one.

0 of 3 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

3 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.