Uphealth Signal MCP Server

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

Local + remotestreamable-httpstdio

What is the Uphealth Signal MCP Server?

Uphealth Signal is an MCP integration. The adaptive health-messaging engine for apps and agents. Federally-sourced. Not medical advice.

Hosted connection

The registry lists a streamable-http connection at https://mcp.uphealth.us/mcp. The endpoint declares these request headers: Authorization.

Packages and local setup

The published npm package is @uphealth/mcp-server, version 1.1.7. Its declared MCP transport is stdio.

The package declares UPHEALTH_API_KEY: Optional. Runs keyless by default — lookup_health_fact needs no key. Get a free sandbox key (it begins up_sandbox_) from https://uphealth.us/signup to unlock the keyed patient-stream + cue tools..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 1.1.7 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related communication MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
UPHEALTH_API_KEYOptional. Runs keyless by default — lookup_health_fact needs no key. Get a free sandbox key (it begins up_sandbox_) from https://uphealth.us/signup to unlock the keyed patient-stream + cue tools.Optional