Uphealth Signal MCP Server

by uphealth Your server? Claim it

answering

Uphealth Signal is answering right now. Last checked 8 min ago. 53 installs a week from npm. It exposes 5 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 145 · avg 14 · +109% w/w

a month agotoday

Uptime history 51 days of history

51 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

595 ms

Response time

average over 24h

Installs / week

npm and PyPI

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 24 August 2026. No other catalogue keeps this.

3 Sep a tool changed version

24 Aug a tool changed version

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://mcp.uphealth.us/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.uphealth.us/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://mcp.uphealth.us/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.uphealth.us/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.uphealth.us/mcp"
    }
  }
}

This one needs environment variables set before it will start: 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.). The author declared them in the registry entry; get the values from the project itself.

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

lookup

lookup_health_fact

Zero setup — NO key required. Returns ONE already-public federal health fact, list, or tip for a question or topic (e.g. "high blood pressure", "sleep", "type 2 diabetes"), with its federal source (CDC / MedlinePlus / NIH) and a link to the public uphealth.me page. Free + rate-limited. For adaptive, patient-specific message sequencing — receptivity-scored cues + audience-safety verdicts over the full library of federally-sourced facts, lists & tips — get a free Discovery key at https://uphealth.us/signup

get_next_cued_message

Submit the patient's response to the prior cue and get the next one — federally-sourced, audience-safety-checked, and re-sequenced on that feedback. REFUSES WITHOUT PRIOR-MESSAGE FEEDBACK (the moat): the engine will not advance a stream blind, returning 409 if you skip it. response_action is one of the accepted cue vocabulary (see the signal://catalog resource). Same idempotency_key + same feedback returns the cached cue; conflicting feedback under the same key returns 409.

patient

create_patient_stream

Create a Signal cued stream for one patient and get the first cue back synchronously. Every cue is federally-sourced, audience-safety-checked, and sequenced on the patient's prior response — so your agent never fabricates health content. Choose a template_id from the signal://catalog resource and pre-satisfy its required audience_tags + patient_context (clinical templates 422 without them). Display mode renders in your app: no PHI, no BAA. Each later cue MUST submit the prior message's feedback — the engine refuses to advance without it (the sequencing moat).

sandbox

list_sandbox_topics

List the curated sandbox topic labels that define the free Discovery corpus — every topic federally-sourced and audience-safety-checked. Use it to preview what content domains exist before creating a stream. Does NOT enumerate messages — the corpus stays internal. For the full live template catalog + gating contract, read the signal://catalog resource.

stream

read_stream_state

Read a stream's current state, its current cued message, and event count. Read-only — does NOT advance the stream or consume a cue. Use it between feedback turns to inspect where a patient is in their federally-sourced, audience-safety-checked sequence.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.uphealth.us/mcp	streamable-http	answering	568 ms	8 min ago

Alternatives to Uphealth Signal

same job, measured the same way

memi

by sarveshsea

Memi is the read-only design engineering audit and skill layer for coding agents.

149 installs/wk local only

Regulatory Intel MCP

by datakoot

US Federal Register for AI agents: rules, notices and executive orders. No API keys.

5 tools answering

Agent Memory OS

by yamantaka520

Local-first memory engine for AI-agent teams: team/project ACL, recall, and federated sync.

522 installs/wk local only

Voice Truthgate MCP

by hei33enberg

Honest voice authenticity for AI agents: enrol a voice, verify a call clip. Signal, not verdict.

33 installs/wk local only

Lettera

by lettera

Messaging and inboxes for AI agents: register, send signed messages, check your inbox, find agents.

7 tools answering

Linkup

by mcparmory

Search the web and fetch pages with sourced results, optimized for AI agents

223 installs/wk local only

Heartwood Memory — governed memory for AI agents

by jermayne36

Heartwood Memory — governed AI agent memory; signed provenance. BUSL-1.1; not OSI open source.

153 installs/wk local only

Botcorpus

by mixall11

Sourced, dated SK/CZ/AT/EU civic, tax and legal facts for AI agents. Read via MCP, not guesswork.

7 tools answering

Uphealth Signal — questions

Answers built from our own checks of this server.

What can Uphealth Signal do?

It exposes 5 tools, read directly from the server on our last check. Among them: create_patient_stream, get_next_cued_message, list_sandbox_topics, lookup_health_fact, read_stream_state. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Uphealth Signal working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 595 ms. The bar chart above shows every period we have measured.

Is Uphealth Signal still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect Uphealth Signal?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Uphealth Signal need an API key?

No. Uphealth Signal completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Uphealth Signal?

It answers our handshake in 595 ms on average, which is faster than 24% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Uphealth Signal?

The npm package @uphealth/mcp-server was installed 53 times in the last week. Week over week that is +109%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.