# Juno Open Health Tools Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Juno Open Health Tools

Organize your health notes into appointment prep materials without storing or diagnosing.

- Record: https://musedirectory.ai/connector/juno-open-health-tools
- Category: Health
- Developer: MarshallBear1
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 1443ms, checked 2026-09-28T08:15:59Z
- Endpoint: https://juno-health-tools.vercel.app/api/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-09-24T03:01:20Z)
- Source: Found in the official MCP Registry (io.github.MarshallBear1/juno-open-health-tools) https://registry.modelcontextprotocol.io/v0/servers?search=io.github.MarshallBear1%2Fjuno-open-health-tools

Turns your own health observations into structured appointment briefs. Organizes symptoms by timing and impact, builds timelines from your notes, and prepares concise summaries of goals, changes, and questions for your doctor. No diagnosis or medical advice.

Example request: "Help me organize my notes about my migraines into a timeline and summary to bring to my neurologist appointment."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Juno Open Health Tools to help me. It is a free service with an MCP server at https://juno-health-tools.vercel.app/api/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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.
- 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_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_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_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.

Screening checks:
- MCP handshake: pass (Answered in 270ms)
- Domain against threat feeds (Cloudflare security DNS): pass (juno-health-tools.vercel.app not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (5 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)