Uphealth Signal MCP server

• create_patient_streamwrite actionFree

  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).

• get_next_cued_messagewrite actionFree

  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.

• list_sandbox_topicsFree

  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.

• lookup_health_factFree

  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

• read_stream_stateFree

  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.

• Code scan24 source files scanned25/25
• Live reliabilityremote reachable in 735ms20/20
• Tool poisoning5 tool descriptions checked15/15
• Auth qualityAPI key sent as a header8/15
• Maintenancerepository not readable: repo not found3/15
• Maintainer identityendpoint served from the registry-verified namespace domain8/10

Safety score

79/100

higher than 58% of 48,243 servers

Tools

5

the typical server has 7

Tools that change things

40%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

138 ms

faster than 77% of 30,027 servers

Downloads a week

30

more than 18% of 12,306 servers with a package

Uphealth Signal: common questions

Is Uphealth Signal MCP server safe?

Mostly: it is graded B (79/100). Read the Uphealth Signal safety report

How do I install Uphealth Signal?

It runs remotely at mcp.uphealth.us. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Uphealth Signal need an API key?

Yes. The registry entry asks for UPHEALTH_API_KEY, Authorization.

Is Uphealth Signal maintained?

The latest release is v1.1.7.

Is Uphealth Signal up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

How does Uphealth Signal compare with other MCP servers?

safety score 79/100 (higher than 58% of 48,243 servers); tools 5 (the typical server has 7); tools that change things 40% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.