Uphealth Signal
Server Details
The adaptive health-messaging engine for apps and agents. Federally-sourced. Not medical advice.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.5/5 across 5 of 5 tools scored.
Each tool targets a distinct operation: creating a stream, advancing with feedback, listing topics, looking up facts, and reading state. No overlapping purposes.
All tool names follow a verb_noun pattern, but verbs vary (create, get, list, lookup, read) without a unified convention, slightly reducing consistency.
5 tools is well-scoped for a focused health messaging service, covering the core workflow without excess.
Core read and advance operations are present, but missing tools for listing streams, managing templates, or deletion are minor gaps.
Available Tools
5 toolscreate_patient_streamInspect
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 | Required | Description | Default |
|---|---|---|---|
| attributes | No | De-identified patient context. v1 accepts free-form jsonb; future templates will enforce schemas. | |
| template_id | 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/context are missing — pre-satisfy them from the catalog. A free sandbox (Discovery) key always cues the curated sandbox corpus. | |
| audience_tags | No | Subset of the 14-tag B5/B6 schema. See list_sandbox_topics for sample topic labels. | |
| delivery_mode | No | v1 is Display-only; Deliver-mode unlocks at Per-Episode tier after BAA. | display |
| idempotency_key | No | 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 header. UUID v4 recommended. | |
| feedback_timeout_days | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| _meta | Yes | Legal/disclosure block returned on every 2xx (A1 §6.7). |
| state | Yes | |
| first_cue | Yes | A cued message plus its per-cue receptivity score and audience-safety verdict. |
| stream_id | Yes | Persist this — every later cue/read references it. |
| rate_limit | No | Discovery monthly cue-cap headroom. Absent on non-Discovery tiers (no cap). |
| next_cue_eligible_at | No |
get_next_cued_messageIdempotentInspect
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 | Required | Description | Default |
|---|---|---|---|
| feedback | Yes | ||
| stream_id | Yes | The stream_id returned by create_patient_stream. |
Output Schema
| Name | Required | Description |
|---|---|---|
| _meta | Yes | Legal/disclosure block returned on every 2xx (A1 §6.7). |
| state | Yes | |
| message | No | |
| next_cue | No | A cued message plus its per-cue receptivity score and audience-safety verdict. |
| stream_id | Yes | |
| idempotent | No | true when this is the cached result of a repeated idempotency_key. |
| rate_limit | No | Discovery monthly cue-cap headroom. Absent on non-Discovery tiers (no cap). |
| normalized_action | No | 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 on a cue result; absent on the exhausted-stream result. |
| sandbox_exhausted | No | Present + true when the sandbox subset is exhausted; no next_cue then. |
list_sandbox_topicsRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| _meta | Yes | Legal/disclosure block returned on every 2xx (A1 §6.7). |
| topic_labels | Yes | |
| template_id_for_sandbox | No |
lookup_health_factRead-onlyInspect
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 | Required | Description | Default |
|---|---|---|---|
| q | Yes | A health question or topic, e.g. "high blood pressure", "sleep", or "type 2 diabetes". |
Output Schema
| Name | Required | Description |
|---|---|---|
| fact | Yes | The single already-public federal message — a fact, list, or tip (see kind). |
| topic | No | The matched topic's title. |
| upgrade | Yes | The free-key upsell — adaptive sequencing lives behind a Discovery key. |
| disclaimer | Yes | |
| attribution | Yes | "Source: <agency> via Uphealth". |
read_stream_stateRead-onlyInspect
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 | Required | Description | Default |
|---|---|---|---|
| stream_id | Yes | The stream_id returned by create_patient_stream. |
Output Schema
| Name | Required | Description |
|---|---|---|
| _meta | Yes | Legal/disclosure block returned on every 2xx (A1 §6.7). |
| state | Yes | |
| stream_id | Yes | |
| rate_limit | No | Discovery monthly cue-cap headroom. Absent on non-Discovery tiers (no cap). |
| current_cue | No | |
| template_id | No | |
| events_count | No | |
| next_cue_eligible | No |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!