Juno Open Health Tools MCP Server

by marshallbear1 Your server? Claim it

answering

Juno Open Health Tools is answering right now. Last checked 14 min ago. It exposes 5 tools. Last commit 22 Aug 2026.

Consent-gated tools that turn user health notes into non-diagnostic appointment-prep materials.

Uptime history 52 days of history · worst day 92%

52 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

252 ms

Response time

average over 24h

Stars

last commit 22 Aug 2026

Juno Open Health Tools missed 3 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add juno-open-health-tools --transport http https://juno-health-tools.vercel.app/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "juno-open-health-tools": {
      "url": "https://juno-health-tools.vercel.app/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.juno-open-health-tools]
url = "https://juno-health-tools.vercel.app/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "juno-open-health-tools": {
      "url": "https://juno-health-tools.vercel.app/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "juno-open-health-tools": {
      "url": "https://juno-health-tools.vercel.app/api/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

build

build_health_timeline

After explicit consent, sort only non-identifying, user-authored observations into a factual chronology while preserving uncertainty. Do not accept PHI or invent dates or diagnoses.

prepare

prepare_appointment_brief

After explicit consent, turn minimal non-identifying goals, changes, impact, user-stated medicines, and questions into a concise appointment brief. Do not accept PHI or provide medical advice.

reflect

reflect_on_flare

After explicit consent, structure only non-identifying, user-authored before, during, and after observations; turn suspected patterns into questions, not causal claims. Do not accept PHI.

render

render_appointment_brief

After the user's existing consent, render the non-identifying output of prepare_appointment_brief as an accessible card. Call prepare_appointment_brief first; do not add PHI.

symptom

find_symptom_words

After explicit consent, organise only the user's non-identifying description into neutral sensation, timing, pattern, and impact vocabulary. Do not accept PHI or infer a diagnosis or cause.

Endpoints

URL	Transport	State	Latency	Checked
https://juno-health-tools.vercel.app/api/mcp	streamable-http	answering	219 ms	14 min ago

Alternatives to Juno Open Health Tools

same job, measured the same way

QSimHealth

by qsimhealth

Healthcare staffing simulator — ED, walk-in clinic, and appointment office DES tools.

7 tools answering

Anythingmcp

by keysersoft

Self-hosted MCP gateway: turn any API, database or MCP server into AI connectors — no code.

4 tools answering

OLVM AIops

by aiops-tools

Governed OLVM / oVirt 4.5 ops — 17 MCP tools: inventory, health, capacity, diagnosis; audited.

local only

Specrun

by pavelpiha

MCP server that converts OpenAPI specs into tools which can query API endpoints

local only

Job Card

by theluckystrike

Job cards for trades and field service: hours and materials per job, open to invoiced.

11 tools answering

Codescene MCP Server

by codescene

An MCP server that provides CodeScene Code Health analysis tools.

711 installs/wk local only

Dsr MCP Server

by grupo-avispa

An MCP server that provides tools for interacting with Deep State Representation (DSR) graphs.

local only

Pullpush MCP

by pullpush

Connect any two APIs and keep them in sync — 48 MCP tools with shadow previews and diagnostics.

37 installs/wk answering

Juno Open Health Tools — questions

Answers built from our own checks of this server.

What can Juno Open Health Tools do?

It exposes 5 tools, read directly from the server on our last check. Among them: build_health_timeline, find_symptom_words, prepare_appointment_brief, reflect_on_flare, render_appointment_brief. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Juno Open Health Tools working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 252 ms. The bar chart above shows every period we have measured.

How do I connect Juno Open Health Tools?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Juno Open Health Tools need an API key?

No. Juno Open Health Tools completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Juno Open Health Tools?

It answers our handshake in 252 ms on average, which is faster than 66% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Juno Open Health Tools open source?

Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.