Uphealth Signal
NPM · @UPHEALTH/MCP-SERVER · 2 COMPONENTS · SCANNED AUG 3
The adaptive health-messaging engine for apps and agents. Federally-sourced. Not medical advice.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (121 of 123), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (121 of 123), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 11 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability65
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 926 tokens (~132/item across 7 items; 5 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @uphealth/mcp-server
claude mcp add us-uphealth-mcp -- npx -y @uphealth/mcp-server
codex mcp add us-uphealth-mcp -- npx -y @uphealth/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"us-uphealth-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@uphealth/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add us-uphealth-mcp --command npx --arg -y --arg @uphealth/mcp-server
mcp_servers:
us-uphealth-mcp:
command: "npx"
args: ["-y", "@uphealth/mcp-server"] {
"mcpServers": {
"us-uphealth-mcp": {
"command": "npx",
"args": [
"-y",
"@uphealth/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +60
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- MCP protocol: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → fair ▲ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
- 1 Aug 26 −20
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +9
- Malware scan: pass → unverified ▼ security
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −27
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 27 Jul 26 45
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/@uphealth/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 121 packages
121 packages in the resolved dependency tree · 121 deprecated · 35 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
create_patient_stream ~347
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).
| Name | Type | Req | Description |
|---|---|---|---|
| attributes | object | — | De-identified patient context. v1 accepts free-form jsonb; future templates will enforce schemas. |
| audience_tags | array | — | Subset of the 14-tag B5/B6 schema. See list_sandbox_topics for sample topic labels. |
| delivery_mode | string | — | v1 is Display-only; Deliver-mode unlocks at Per-Episode tier after BAA. |
| feedback_timeout_days | integer | — | — |
| idempotency_key | string | — | Optional. Stripe-style create idempotency: a retried create with the same key returns the ORIGINAL stream instead of minting (and billing) a second one. Forwarded as the Idempotency-Key request heade… |
| template_id | string | yes | One of the live Signal templates. Read the signal://catalog resource for each template's required audience_tags + patient_context. On a production key a clinical template 422s if its required tags/co… |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | yes | Legal/disclosure block returned on every 2xx (A1 §6.7). |
| first_cue | object | yes | A cued message plus its per-cue receptivity score and audience-safety verdict. |
| next_cue_eligible_at | string|null | — | — |
| rate_limit | object | — | Discovery monthly cue-cap headroom. Absent on non-Discovery tiers (no cap). |
| state | string | yes | — |
| stream_id | integer | yes | Persist this — every later cue/read references it. |
No examples provided.
get_next_cued_message ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| feedback | object | yes | — |
| stream_id | integer | yes | The stream_id returned by create_patient_stream. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | yes | Legal/disclosure block returned on every 2xx (A1 §6.7). |
| idempotent | boolean | — | true when this is the cached result of a repeated idempotency_key. |
| message | string | — | — |
| next_cue | object | — | A cued message plus its per-cue receptivity score and audience-safety verdict. |
| normalized_action | string|null | — | null when the submitted response_action was a recognized value; otherwise the acknowledge-class value the well-formed-but-unrecognized action was folded to (forward-compat tolerance). Always present… |
| rate_limit | object | — | Discovery monthly cue-cap headroom. Absent on non-Discovery tiers (no cap). |
| sandbox_exhausted | boolean | — | Present + true when the sandbox subset is exhausted; no next_cue then. |
| state | string | yes | — |
| stream_id | integer | yes | — |
No examples provided.
list_sandbox_topics ~75
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | yes | Legal/disclosure block returned on every 2xx (A1 §6.7). |
| template_id_for_sandbox | string | — | — |
| topic_labels | array | yes | — |
No examples provided.
lookup_health_fact ~157
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
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | A health question or topic, e.g. "high blood pressure", "sleep", or "type 2 diabetes". |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | yes | "Source: <agency> via Uphealth". |
| disclaimer | string | yes | — |
| fact | object | yes | The single already-public federal message — a fact, list, or tip (see kind). |
| topic | string | — | The matched topic's title. |
| upgrade | object | yes | The free-key upsell — adaptive sequencing lives behind a Discovery key. |
No examples provided.
read_stream_state ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| stream_id | integer | yes | The stream_id returned by create_patient_stream. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | yes | Legal/disclosure block returned on every 2xx (A1 §6.7). |
| current_cue | object|null | — | — |
| events_count | integer | — | — |
| next_cue_eligible | boolean | — | — |
| rate_limit | object | — | Discovery monthly cue-cap headroom. Absent on non-Discovery tiers (no cap). |
| state | string | yes | — |
| stream_id | integer | yes | — |
| template_id | string | — | — |
No examples provided.