Uphealth MCP server
Which servers in the official MCP registry are Uphealth's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-20
- Registry nameus.uphealth/mcpverified in the MCP registry
The registry name sits under uphealth.us. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-20
- Tools5
- Server calls itselfuphealth-mcp
- Server version1.1.7
- Protocol version2025-06-18
On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 50 ms.
- Its tools do every use case we checked: request the next health message for a patient; look up cited federal health facts from an AI assistant.
- Checked on 2 of the 7 days it takes to judge reliability.
Once connected
- For "look up cited federal health facts from an AI assistant", the likely first call is lookup_health_fact.
- create_patient_stream change data without a sign-in: anyone with the address can call them.
- Parameters are untyped or undescribed in 2 of 5 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
- What an agent can do with it2 of 2 use cases
- Use15 npm downloads a week
- Answeredmeasuring2 of the 7 daily checks it takes to print a share
- Median first answer53 ms
- Space in an agent's context≈ 1,271 tokensthe definitions of all its tools (5), which an agent carries on every turn
- Tool definitionsA · 93 of 100
- Typed results5 of 5 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 2 of 5
What an agent can do with it
- can do · request the next health message for a patient
- not sure · send employees a quarterly health guide
- can do · look up cited federal health facts from an AI assistant
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
- Tools that change data, on a server that answers without a sign-in: create_patient_stream
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
lookup_health_factZero 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…
create_patient_streamCreate 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…
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. REFUSES WITHOUT PRIOR-MESSAGE FEEDBACK (the moat): the engine will not advance a stream…
read_stream_stateRead 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…
list_sandbox_topicsList 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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"uphealth": {
"type": "http",
"url": "https://mcp.uphealth.us/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http uphealth https://mcp.uphealth.us/mcpclaude.ai, ChatGPT and other clients: add https://mcp.uphealth.us/mcp as a custom connector in the settings.
Also shipped through: npm
OpenAPI spec
6 paths, read 2026-10-20. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.