PulsVy

com.pulsvyPublished by pulsvy.comOfficial publisherv0.1.0Updated Nov 5, 2026

Your Google Health data (Fitbit, Pixel Watch): sleep, HRV, readiness and biological age.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Remote MCP server that gives an assistant access to your Google Health data from Fitbit and Pixel Watch, including sleep, HRV, readiness and biological age.

What you can do
  • Read Google Health data from Fitbit and Pixel Watch devices.
  • Review sleep, HRV, readiness and biological age metrics.
  • No individual tools are listed, so the exact queries and outputs are not documented here.
When to use it
Useful when you want an assistant to look at your own wearable health metrics — sleep, heart-rate variability, readiness or biological age — and discuss or summarize them, for example in a personal health review.
Requirements
A remote MCP endpoint at pulsvy.com reached over streamable HTTP. OAuth sign-in is required, so you need a PulsVy account and a Google Health/Fitbit data source connected to it. No environment variables or headers are declared.
Before you install
The server reads sensitive personal health data from your Google Health/Fitbit account and sends it to a third-party service, so review its privacy and data-retention terms first. Access is granted through OAuth; check which scopes are requested and revoke access if you stop using it.

Installation

In SourceWeft

  1. Open PulsVy 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/com.pulsvy%2Fpulsvy/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": {
    "pulsvy": {
      "type": "http",
      "url": "https://pulsvy.com/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.0LatestNov 5, 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.