Skip to content

Uphealth Signal MCP server

us.uphealth/mcpuphealth.usstreamable-httpv1.1.7Scanned

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

5 tools: 2 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 2 write, 3 read.
  • Reads private data · 2
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Uphealth Signal MCP server can do

The Uphealth Signal MCP server is published by uphealth.us, a domain the MCP Registry verified. It has 5 tools. It can create or change data (2 tools: create_patient_stream and get_next_cued_message), but cannot delete data. 3 tools only read.

2 tools read private data (get_next_cued_message and read_stream_state); 3 tools bring in text other people can write (create_patient_stream, get_next_cued_message and read_stream_state).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.1.7.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 2Claude Code: ask
  • create_patient_streamCreate a Signal cued stream for one patient and get the first cue back synchronously.Reads text others writeNo findings

    Why it is in this group

    • The name "create_patient_stream" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Create patient stream
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • get_next_cued_messageSubmit the patient's response to the prior cue and get the next one — federally-sourced, audience-safety-checked, and re-sequenced on that feedback.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_next_cued_message" says "get": a word for reading.
    • The description's first verb is "submit": a word for a change.

    What it can reach

    • private-dataThe name "get_next_cued_message" says "get" and "message": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "get_next_cued_message" says "get" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Submit feedback, get next cued message
    • readOnlyHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • list_sandbox_topicsList the curated sandbox topic labels that define the free Discovery corpus — every topic federally-sourced and audience-safety-checked.No findings

    Why it is in this group

    • The name "list_sandbox_topics" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List sandbox topics
    • readOnlyHint: true
    • openWorldHint: false
  • lookup_health_factZero setup — NO key required.No findings

    Why it is in this group

    • The name "lookup_health_fact" says "lookup": a word for reading.
    Description, as the server wrote it
    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

    Annotations the server declares

    • title: Look up a public health fact, list, or tip (no key)
    • readOnlyHint: true
    • openWorldHint: false
  • read_stream_stateRead a stream's current state, its current cued message, and event count.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "read_stream_state" says "read": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "message": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "read" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Read stream state
    • readOnlyHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:20 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.uphealth.us/mcp: tools/list returned 5 tools to an anonymous client, including create_patient_stream (write), get_next_cued_message (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.1.7. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__uphealth__lookup_health_fact",
      "mcp__uphealth__read_stream_state",
      "mcp__uphealth__list_sandbox_topics"
    ],
    "ask": [
      "mcp__uphealth__create_patient_stream",
      "mcp__uphealth__get_next_cued_message"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as uphealth. Review it before you use it.

Capability tags behind 3 rules
  • mcp__uphealth__create_patient_stream untrusted-input
  • mcp__uphealth__get_next_cued_message private-data, untrusted-input
  • mcp__uphealth__read_stream_state private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/us.uphealth/mcp/verify?hash=8e6ff813c2f55913d2b8f7ca87433b776edf3c1e8c7cc36324ebdf6333bf71ca" | jq -e '.changed == false'

Pinned hash 8e6ff813c2f5, from Nov 18, 2026, 10:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/us.uphealth/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for us.uphealth/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/us.uphealth/mcp.svg)](https://radar.anlyon.com/servers/us.uphealth/mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:55 UTC.

Uphealth Signal MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Uphealth Signal MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Uphealth Signal MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Uphealth Signal MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Uphealth Signal MCP server have?

5 tools: 2 write, 3 read. create_patient_stream, get_next_cued_message, lookup_health_fact, read_stream_state and list_sandbox_topics.

Does the Uphealth Signal MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Uphealth Signal MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Uphealth Signal MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.