Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Juno Open Health Tools

REMOTE · JUNO-HEALTH-TOOLS.VERCEL.APP · SCANNED AUG 3

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

64 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability40
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 772 tokens (~128/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage77
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 19% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · juno-health-tools.vercel.app

# add to Claude Code
claude mcp add --transport http marshallbear1-juno-open-health-tools https://juno-health-tools.vercel.app/api/mcp
# ~/.codex/config.toml
[mcp_servers.marshallbear1-juno-open-health-tools]
url = "https://juno-health-tools.vercel.app/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "marshallbear1-juno-open-health-tools": {
      "type": "remote",
      "url": "https://juno-health-tools.vercel.app/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add marshallbear1-juno-open-health-tools --url https://juno-health-tools.vercel.app/api/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  marshallbear1-juno-open-health-tools:
    url: "https://juno-health-tools.vercel.app/api/mcp"
// mcp.json
{
  "mcpServers": {
    "marshallbear1-juno-open-health-tools": {
      "type": "http",
      "url": "https://juno-health-tools.vercel.app/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Aug 26 0
    • Stability: unverified → 0.03 functional
  • 1 Aug 26 63

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://juno-health-tools.vercel.app/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.vercel.app CN=WR1,O=Google Trust Services,C=US 28 Jun 2026 26 Sept 2026 RSA 2048 SHA256-RSA b1c2b607df94f28513779ae26fecf92f
SANs: *.vercel.app
CN=WR1,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7fd9e2c2d2048a0474b627a26d0868a7
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d
DNSSEC insecure

Validation of juno-health-tools.vercel.app. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
vercel.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://juno-health-tools.vercel.app/api/mcp Verified 200
http (plaintext) http://juno-health-tools.vercel.app/api/mcp HTTPS enforced 308 https://juno-health-tools.vercel.app/api/mcp
MCP tools — 5 exposed · ~647 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
build_health_timeline ~100

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.

NameTypeReqDescription
consentConfirmedbooleanyesSet to true only after the user explicitly agrees to transient processing of their non-identifying, user-authored health notes. Do not submit PHI, medical-record identifiers, contact details, credent…
observationsarrayyes
NameTypeReqDescription
changePointsarrayyes
disclaimerstringyes
timelinearrayyes

No examples provided.

find_symptom_words ~125

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.

NameTypeReqDescription
bodyAreastring
consentConfirmedbooleanyesSet to true only after the user explicitly agrees to transient processing of their non-identifying, user-authored health notes. Do not submit PHI, medical-record identifiers, contact details, credent…
descriptionstringyes
impactstring
timingstring
NameTypeReqDescription
disclaimerstringyes
originalDescriptionstringyes
promptsobjectyes
starterSentencestringyes

No examples provided.

prepare_appointment_brief ~144

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.

NameTypeReqDescription
changesarray
consentConfirmedbooleanyesSet to true only after the user explicitly agrees to transient processing of their non-identifying, user-authored health notes. Do not submit PHI, medical-record identifiers, contact details, credent…
detailsToBringarray
impactsarray
mainGoalstringyes
medicinesarray
questionsarray
NameTypeReqDescription
changesarrayyes
detailsToBringarrayyes
disclaimerstringyes
impactsarrayyes
mainGoalstringyes
medicinesarrayyes
questionsarrayyes

No examples provided.

reflect_on_flare ~128

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.

NameTypeReqDescription
baselineBeforearray
consentConfirmedbooleanyesSet to true only after the user explicitly agrees to transient processing of their non-identifying, user-authored health notes. Do not submit PHI, medical-record identifiers, contact details, credent…
duringarray
possiblePatternsarray
recoveryAfterarray
NameTypeReqDescription
baselineBeforearrayyes
disclaimerstringyes
duringarrayyes
possiblePatternsToObservearrayyes
recoveryAfterarrayyes

No examples provided.

render_appointment_brief ~150

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.

NameTypeReqDescription
changesarrayyes
consentConfirmedbooleanyesSet to true only after the user explicitly agrees to transient processing of their non-identifying, user-authored health notes. Do not submit PHI, medical-record identifiers, contact details, credent…
detailsToBringarrayyes
disclaimerstringyes
impactsarrayyes
mainGoalstringyes
medicinesarrayyes
questionsarrayyes
NameTypeReqDescription
changesarrayyes
detailsToBringarrayyes
disclaimerstringyes
impactsarrayyes
mainGoalstringyes
medicinesarrayyes
questionsarrayyes

No examples provided.