Juno Open Health Tools

by MarshallBear1 · remote · no sign-in to list tools · v1.1.0 · published by GitHub user MarshallBear1

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

Changes · 4

Compare Registry entry

5 tools: 4 change things and 1 only read.

Scanned Oct 21, 2026

Deletes or cancels0Claude Code: deny
Can't be undone0Claude Code: ask
Changes things4Claude Code: ask: see these tools
Only reads1Claude Code: allow: see these tools

5 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Findings

Matches of fixed checks, with the text they matched.

5 info

Infofind_symptom_words
The input schema at properties.consentConfirmed.description mentions "credentials".
Matched text
inputSchema.properties.consentConfirmed.description: "...al-record identifiers, contact details, credentials, or provider documents."
What this check looks for
Infobuild_health_timeline
The input schema at properties.consentConfirmed.description mentions "credentials".
Matched text
inputSchema.properties.consentConfirmed.description: "...al-record identifiers, contact details, credentials, or provider documents."
What this check looks for
Infoprepare_appointment_brief
The input schema at properties.consentConfirmed.description mentions "credentials".
Matched text
inputSchema.properties.consentConfirmed.description: "...al-record identifiers, contact details, credentials, or provider documents."
What this check looks for
Inforeflect_on_flare
The input schema at properties.consentConfirmed.description mentions "credentials".
Matched text
inputSchema.properties.consentConfirmed.description: "...al-record identifiers, contact details, credentials, or provider documents."
What this check looks for
Inforender_appointment_brief
The input schema at properties.consentConfirmed.description mentions "credentials".
Matched text
inputSchema.properties.consentConfirmed.description: "...al-record identifiers, contact details, credentials, or provider documents."
What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 4Creates or changes something that can be changed back.Claude Code: ask

build_health_timelineSorts non-identifying, user-authored observations into a factual chronology while preserving supplied dates and uncertainty.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
  The input schema at properties.consentConfirmed.description mentions "credentials".
  Matched text
  inputSchema.properties.consentConfirmed.description: "...al-record identifiers, contact details, credentials, or provider documents."
  What this check looks for
Description, as the server wrote it
Sorts non-identifying, user-authored observations into a factual chronology while preserving supplied dates and uncertainty. Requires explicit consent for transient processing. PHI and diagnosis are outside its scope.
Annotations the server declares
- title: Build health timeline
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
prepare_appointment_briefStructures non-identifying goals, changes, impacts, user-stated medicines and questions into an appointment brief.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
  The input schema at properties.consentConfirmed.description mentions "credentials".
  Matched text
  inputSchema.properties.consentConfirmed.description: "...al-record identifiers, contact details, credentials, or provider documents."
  What this check looks for
Description, as the server wrote it
Structures non-identifying goals, changes, impacts, user-stated medicines and questions into an appointment brief. Requires explicit consent for transient processing. PHI, diagnosis and treatment advice are outside its scope.
Annotations the server declares
- title: Prepare appointment brief
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
reflect_on_flareStructures non-identifying before, during and recovery observations, presenting suspected patterns as questions rather than causes.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
  The input schema at properties.consentConfirmed.description mentions "credentials".
  Matched text
  inputSchema.properties.consentConfirmed.description: "...al-record identifiers, contact details, credentials, or provider documents."
  What this check looks for
Description, as the server wrote it
Structures non-identifying before, during and recovery observations, presenting suspected patterns as questions rather than causes. Requires explicit consent for transient processing. PHI is outside its scope.
Annotations the server declares
- title: Reflect on a flare
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
render_appointment_briefRenders a supplied, complete, non-identifying appointment brief as an accessible card.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
  The input schema at properties.consentConfirmed.description mentions "credentials".
  Matched text
  inputSchema.properties.consentConfirmed.description: "...al-record identifiers, contact details, credentials, or provider documents."
  What this check looks for
Description, as the server wrote it
Renders a supplied, complete, non-identifying appointment brief as an accessible card. Requires explicit consent for transient processing. Preserves the supplied fields and disclaimer; PHI is outside its scope.
Annotations the server declares
- title: Render appointment brief
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false

Only reads 1Looks things up and changes nothing.Claude Code: allow

find_symptom_wordsOrganises a non-identifying, user-authored sensation description into neutral sensation, timing, pattern and impact vocabulary.1 finding
Why it is in this group
- The name "find_symptom_words" says "find": a word for reading.
Findings
- Info
  The input schema at properties.consentConfirmed.description mentions "credentials".
  Matched text
  inputSchema.properties.consentConfirmed.description: "...al-record identifiers, contact details, credentials, or provider documents."
  What this check looks for
Description, as the server wrote it
Organises a non-identifying, user-authored sensation description into neutral sensation, timing, pattern and impact vocabulary. Requires explicit consent for transient processing. PHI and diagnostic inference are outside its scope.
Annotations the server declares
- title: Find symptom words
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__juno-open-health-tools__find_symptom_words"
    ],
    "ask": [
      "mcp__juno-open-health-tools__build_health_timeline",
      "mcp__juno-open-health-tools__prepare_appointment_brief",
      "mcp__juno-open-health-tools__reflect_on_flare",
      "mcp__juno-open-health-tools__render_appointment_brief"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as juno-open-health-tools. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.github.MarshallBear1/juno-open-health-tools/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

4 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:17 UTC.

For agents: Markdown · JSON · report this listing