Health · Remote MCP server

Uphealth Signal

The adaptive health-messaging engine for apps and agents. Federally-sourced. Not medical advice.

Visit Uphealth Signal's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
us.uphealth/mcp
Version
1.1.7
Status
Active
Category
health
Transport
Streamable HTTP, stdio (local process)
Package
npm
Published
2026-09-03
Updated
2026-09-03
Publisher
us.uphealth
Namespace
Namespace verified by the MCP Registry via the domain uphealth.us · how
Website
uphealth.us/docs/mcp-quickstart
Repository
github.com/ericinsf/uphealth (folder mcp-server)
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://mcp.uphealth.us/mcpAuthorization (secret)

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 200)
Handshake
uphealth-mcp 1.1.7 · protocol 2025-06-18
Tools discovered
5: lookup_health_fact, create_patient_stream, get_next_cued_message, read_stream_state, list_sandbox_topics
Checked on
2026-10-05

How the live check works

Packages

RegistryPackageVersionTransportEnvironment variables
npm@uphealth/mcp-server1.1.7stdioUPHEALTH_API_KEY (secret)

How to connect Uphealth Signal

Uphealth Signal is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.uphealth.us/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.

The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.

It can also run locally from a Node.js package published to the npm registry: @uphealth/mcp-server version 1.1.7. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @uphealth/mcp-server@1.1.7. It reads the environment variable UPHEALTH_API_KEY (secret); set it in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@uphealth/mcp-server@1.1.7"
      ],
      "env": {
        "UPHEALTH_API_KEY": "<secret>"
      }
    }
  }
}

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

All 381 →
ServerRunsEndpoint or package
Truthstack MCPSupplement-drug interaction safety API for AI agents with FDA adverse event data.Local · stdionpm: truthstack-mcp
Uk Pest ManagementUK pest, disease, and weed management - symptom diagnosis, IPM, approved products.Remote · HTTPLive check: ✗ no handshakemcp.ansvar.eu
UK Public Services & Health MCP Server from MCPBundlesAccess CQC care ratings, NHS health services, and food hygiene data across the UK.Remote & Local · HTTP, stdioLive check: sign-in requiredmcp.mcpbundles.com
Uk Vet MedicinesUK veterinary medicines - VMD database, withdrawal periods, cascade rules.Remote · HTTPLive check: ✗ no handshakemcp.ansvar.eu
Us Regulations MCPUS compliance: HIPAA, CCPA, SOX, GLBA, FERPA, COPPA, FDA, EPA, FFIEC, NYDFS + 4 state privacy laws.Local · stdionpm: @ansvar/us-regulations-mcp
US Safety RecallsNHTSA vehicle recalls and FDA food/drug recalls. 4 tools.Remote · HTTPLive check: ✗ no handshakeus-safety-recalls-mcp.apify.actor
Uscore Profile Gap LintFinds the FHIR R4 resources still pinned to US Core 3.1.1 or 5.0.1, and the USCDI v3 Patient element.Local · stdionpm: @readystack/uscore-profile-gap-lint
VA Healthcare FacilitiesVA facility locations, services, wait times, and satisfaction scores.Remote · HTTPLive check: ✓ handshakemcp.olyport.com