86trust / 100

Juno Open Health Tools

by juno-health-tools.vercel.app in Developer tools

MCP serverPassing, checked 9 h ago

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

https://juno-health-tools.vercel.app/api/mcp

Last 30 days

All checks passedSome failedAll failedNot checked
Uptime
100%
Response time
227 ms typical, 227 ms slowest 5%
Last check
9 h ago
Next check
any minute now

How to call it

Add it to any MCP client that supports remote servers.

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

5 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.

Security scan

  • No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTime
9 h agoPassed200227 ms