WristWise

ee.offsitePublished by offsite.eeOfficial publisherv0.1.1Updated Oct 24, 2026

Ask about your sleep, heart rate and wellness trends from your smartwatch.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

A remote MCP server that lets an assistant answer questions about your smartwatch sleep, heart rate and wellness trends.

What you can do
Answer questions about your sleep data from a smartwatch connection, such as patterns and trends over time. Discuss heart rate information and how it relates to your activity or rest. Explore broader wellness trends drawn from your wearable data. The manifest lists no individual tools, so the exact queries and outputs are not documented here.
When to use it
Useful if you wear a smartwatch and want to ask an assistant conversational questions about your sleep, heart rate or general wellness trends instead of reading dashboards yourself.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's address. OAuth authentication is required, so you need an account with the provider and must complete its sign-in flow. No environment variables or headers are declared.
Before you install
The server reads personal health data such as sleep and heart rate, which is sensitive; consider who can access the account and what the provider does with that data. OAuth grants the server access to your account, so review the scopes requested. It is not a medical device or a substitute for professional advice.

Installation

In SourceWeft

  1. Open WristWise in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ee.offsite%2Fwristwise/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "wristwise": {
      "type": "http",
      "url": "https://mcp-wristwise.offsite.ee/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.