mcp server
Juno Open Health Tools
Consent-gated tools that turn user health notes into non-diagnostic appointment-prep materials.
Description as published by the maintainer. Source
- version 1.1.0
- active
active — Registry entry last updated 2026-08-01.
What this server can do
5 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
build_health_timeline(observations, consentConfirmed)- 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. Required: consentConfirmed, observations.
find_symptom_words(impact, timing, bodyArea, description, consentConfirmed)- 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. Required: consentConfirmed, description.
prepare_appointment_brief(changes, impacts, mainGoal, medicines, questions, detailsToBring, consentConfirmed)- 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. Required: consentConfirmed, mainGoal.
reflect_on_flare(during, recoveryAfter, baselineBefore, consentConfirmed, possiblePatterns)- 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. Required: consentConfirmed.
render_appointment_brief(changes, impacts, mainGoal, medicines, questions, disclaimer, detailsToBring, consentConfirmed)- 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. Required: mainGoal, changes, impacts, medicines, questions, detailsToBring, disclaimer, consentConfirmed.
Last successful function declaration observed on . Source: https://juno-health-tools.vercel.app/api/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://juno-health-tools.vercel.app/api/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-01 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-08-01 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 5 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | juno-health-tools.vercel.app | |
| mcp endpoint status | ok | The server listed 5 functions when asked. | as of probe | juno-health-tools.vercel.app |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json