Health · Remote MCP server
Health Partner
Manage your Health Partner account, log food, water, workouts, body using agent.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.shrynshjn/health-partner- Version
- 1.0.0
- Status
- Active
- Category
- health
- Transport
- Streamable HTTP
- Published
- 2026-08-13
- Updated
- 2026-08-13
- Publisher
- shrynshjn (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/shrynshjn) · how
- Website
- healthpartner.shrynshjn.com/ai
- Repository
- github.com/shrynshjn/health_partner
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://healthpartner.shrynshjn.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Health Partner
Health Partner is a remote MCP server: there is nothing to install. Its endpoint is https://healthpartner.shrynshjn.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More health servers
| Server | Runs |
|---|---|
| Health Export MCPQuery 190 Apple Health metrics from any MCP agent: zero-dependency, read-only, local-first. | Local · stdio |
| Health GorillaQuery Health Gorilla FHIR patients, conditions, medications and lab results. | Remote · HTTPLive check: ✓ handshake |
| Health IntelHealthcare provider & compliance intel: NPPES lookup, OIG/SAM exclusion screening, FDA enforcement. | Remote · HTTPLive check: ✓ handshake |
| Health OSN-of-1 health experiments in your AI assistant: Oura/RescueTime data, protocols, workouts. | Remote · HTTPLive check: sign-in required |
| health-osLocal-first personal health record: labs, meds, wearables, food log, deterministic safety checks. | Local · stdio |
| health4aiQuery your Apple Health data from your own Supabase/Postgres via local MCP. | Local · stdio |
| Healthcare DataUS healthcare data for AI agents: CMS, FDA adverse events, CDC, NPPES NPI. Keyless, real samples. | Remote · HTTPLive check: ✓ handshake |
| Healthcare Fda Intelligence MCPScrape the FAA Aircraft Registry by N-number - aircraft make, model, year, owner name, address, airw. | Remote · HTTPLive check: ✗ no handshake |