JUMPER Health

com.jumper-healthPublished by jumper-health.comOfficial publisherv1.0.0Updated Oct 24, 2026

Read shared JUMPER Health records: blood pressure, oxygen, weight, temperature and fetal monitoring.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Remote JUMPER Health server that lets an assistant read shared health records such as blood pressure, oxygen, weight, temperature and fetal monitoring.

What you can do
  • Read shared JUMPER Health records, including blood pressure, oxygen saturation, weight and temperature readings.
  • Access fetal monitoring records that have been shared with the user.
  • No individual tools are documented, so the exact read operations and their parameters are not described in the available material.
When to use it
Useful when someone wants an assistant to look at their own or a shared JUMPER Health record and discuss measurements like blood pressure, oxygen, weight, temperature or fetal monitoring data.
Requirements
A remote MCP endpoint at care-mcp.jumper-health.com over streamable HTTP. OAuth authentication is required, so the user needs a JUMPER Health account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
The server handles sensitive personal health data, including fetal monitoring records, and access is granted through OAuth sign-in to a JUMPER Health account. Only connect if you trust the provider with that data and review which records are shared. The available material does not state whether any tools write, change or delete data.

Installation

In SourceWeft

  1. Open JUMPER Health 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.jumper-health%2Fjumper-health/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": {
    "jumper-health": {
      "type": "http",
      "url": "https://care-mcp.jumper-health.com/"
    }
  }
}

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. v1.0.0LatestSep 21, 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.