Juno (junocompanion.com), operated by SharedGenes, Inc., is a Y Combinator-backed (P26) consumer digital-health startup building an AI personal health assistant for the 1B+ people living with chronic illness. The Juno mobile app (iOS and Android) builds a longitudinal health profile through conversation, biometrics, and medical history to deliver personalized symptom guidance, automated symptom tracking by text or voice, trigger-pattern identification, and appointment-ready reports for clinicians. It supports conditions including fibromyalgia, long COVID, POTS, ME/CFS, EDS, endometriosis, lupus, and MS, and is informed by research from Oxford and UCL plus 1,000+ patient interviews. Founded in 2025 by Marshall Gould (CEO) and Isaac Tolley (CTO); HIPAA-aligned infrastructure with no health data sold. Juno also publishes Juno Open Health Tools, an MIT-licensed remote MCP server at https://juno-health-tools.vercel.app/api/mcp with five read-only, consent-gated tools that turn a user's non-identifying health notes into non-diagnostic appointment-preparation material; it is listed in the official MCP Registry and archived on Zenodo (DOI 10.5281/zenodo.21730086). Juno publishes no REST API or SDK.
Juno Chat is listed with 1 API on the APIs.io network. Tagged areas include Company, Digital Health, Chronic Illness, AI Health Assistant, and Symptom Tracking.
Juno Chat’s developer surface includes documentation, engineering blog, signup flow, and 19 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Health regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/juno-chat/"><img src="https://apis.io/badge/juno-chat/card.svg" alt="Juno Chat on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics+8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling+7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
11 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
Remote streamable-HTTP MCP server (serverInfo Juno Health Tools 1.1.0) with five read-only, consent-gated tools (find_symptom_words, build_health_timeline, prepare_appointment_b...
aid: juno-chat
name: Juno Chat
description: Juno (junocompanion.com), operated by SharedGenes, Inc., is a Y Combinator-backed (P26) consumer digital-health
startup building an AI personal health assistant for the 1B+ people living with chronic illness. The Juno mobile app (iOS
and Android) builds a longitudinal health profile through conversation, biometrics, and medical history to deliver personalized
symptom guidance, automated symptom tracking by text or voice, trigger-pattern identification, and appointment-ready reports
for clinicians. It supports conditions including fibromyalgia, long COVID, POTS, ME/CFS, EDS, endometriosis, lupus, and
MS, and is informed by research from Oxford and UCL plus 1,000+ patient interviews. Founded in 2025 by Marshall Gould (CEO)
and Isaac Tolley (CTO); HIPAA-aligned infrastructure with no health data sold. Juno also publishes Juno Open Health Tools,
an MIT-licensed remote MCP server at https://juno-health-tools.vercel.app/api/mcp with five read-only, consent-gated tools
that turn a user's non-identifying health notes into non-diagnostic appointment-preparation material; it is listed in the
official MCP Registry and archived on Zenodo (DOI 10.5281/zenodo.21730086). Juno publishes no REST API or SDK.
url: https://raw.githubusercontent.com/api-evangelist/juno-chat/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- y-combinator
x-tier: profiled
x-tier-reason: enrichment pass 2026-09-28 (modular-v1; was portfolio-lead)
x-legal-entity: SharedGenes, Inc.
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: false
label: Hosted service · you call their endpoint
confidence: medium
source:
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: unknown
onboarding: unknown
trial: false
try_now: false
public: false
label: Unknown
confidence: low
probe_state: unreadable
source:
- security
generated: '2026-11-06'
method: derived
image: https://junocompanion.com/favicon.png
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Digital Health
- Chronic Illness
- AI Health Assistant
- Symptom Tracking
- Consumer Health
- Mobile App
- Y Combinator
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: IntegrationEdges
url: integrations/juno-chat-integration-edges.yml
- type: LLMsTxt
url: llms/juno-chat-llms.txt
- type: ToolCrosswalk
url: mcp/juno-chat-tool-crosswalk.yml
- type: MCPServer
url: mcp/juno-chat-mcp.yml
- type: WellKnown
url: well-known/juno-chat-well-known.yml
- type: Hosts
url: hosts/juno-chat-hosts.yml
- type: Vendors
url: vendors/juno-chat-vendors.yml
- type: Newsroom
url: https://junocompanion.com/media
- type: Documentation
url: https://github.com/MarshallBear1/juno-open-health-tools/blob/main/app/README.md
- type: SourceCode
url: https://github.com/MarshallBear1/juno-open-health-tools
- type: GitHubRepository
url: https://github.com/MarshallBear1/juno-open-health-tools
- type: DOI
url: https://doi.org/10.5281/zenodo.21730086
- type: Website
url: https://junocompanion.com/
- type: Blog
url: https://junocompanion.com/blog
- type: PrivacyPolicy
url: https://junocompanion.com/privacy
- type: TermsOfService
url: https://junocompanion.com/terms
- type: SignUp
url: https://apps.apple.com/app/juno-chronic-illness-support/id6749455368
- type: SignUp
url: https://play.google.com/store/apps/details?id=com.junochat.app
- type: X
url: https://x.com/junocompanion
- type: LinkedIn
url: https://www.linkedin.com/company/junochat/
- type: Instagram
url: https://www.instagram.com/junocompanion/
- type: DomainSecurity
url: security/juno-chat-domain-security.yml
apis:
- aid: juno-chat:juno-open-health-tools-mcp-server
name: Juno Open Health Tools MCP Server
description: Remote streamable-HTTP MCP server (serverInfo Juno Health Tools 1.1.0) with five read-only, consent-gated tools
(find_symptom_words, build_health_timeline, prepare_appointment_brief, reflect_on_flare, render_appointment_brief) that
organise a user's non-identifying health notes into symptom vocabulary, timelines, flare reflections and an appointment
brief, plus one UI resource for the rendered brief. Each call requires consentConfirmed true; the server declines PHI
and does not diagnose. No credentials required. Listed in the official MCP Registry as io.github.MarshallBear1/juno-open-health-tools;
MIT-licensed source on GitHub.
humanURL: https://github.com/MarshallBear1/juno-open-health-tools
baseURL: https://juno-health-tools.vercel.app/api/mcp
tags:
- MCP
- Digital Health
- Symptom Tracking
properties:
- type: MCPServer
url: mcp/juno-chat-mcp.yml
- type: ToolCrosswalk
url: mcp/juno-chat-tool-crosswalk.yml
- type: Documentation
url: https://github.com/MarshallBear1/juno-open-health-tools/blob/main/app/README.md
- type: SourceCode
url: https://github.com/MarshallBear1/juno-open-health-tools
- type: GitHubRepository
url: https://github.com/MarshallBear1/juno-open-health-tools
- type: MCPRegistry
url: https://registry.modelcontextprotocol.io/v0/servers?search=io.github.MarshallBear1/juno-open-health-tools
- type: DOI
url: https://doi.org/10.5281/zenodo.21730086
x-correction-request:
requested: '2026-09-28'
source:
- https://github.com/api-evangelist/juno-chat/pull/1
request: 'Provider PR #1 (MarshallBear1, co-founder, 2026-08-02), verified live 2026-09-28: the profile''s ''does not currently
publish a public developer API'' is wrong. Add API ''Juno Open Health Tools MCP Server'', MCPServer https://juno-health-tools.vercel.app/api/mcp
(initialize OK, 5 tools: find_symptom_words, build_health_timeline, prepare_appointment_brief, reflect_on_flare, render_appointment_brief);
listed in the official MCP Registry as io.github.MarshallBear1/juno-open-health-tools. Documentation: the repo''s app/README.md;
SourceCode and GitHubRepository: the GitHub repo in the PR; DOI 10.5281/zenodo.21730086; SignUp: the Google Play listing
in the PR. Keep the existing sourced description (founders, conditions) -- do not take the PR''s shorter rewrite.'
applied: '2026-10-03'
applied_note: 'Hand-applied after the local re-profile ignored this block; re-verified live 2026-10-03. Applied: the "does
not currently publish a public developer API" sentence replaced with a sourced sentence on the MCP server (the founder/conditions
description is kept); MCP API entry rebuilt in properties form with baseURL https://juno-health-tools.vercel.app/api/mcp;
mcp/juno-chat-mcp.yml rebuilt from live initialize, tools/list (5 tools with descriptions, annotations, input schemas)
and resources/list (1 UI resource); tool crosswalk records all five as MCP-only; Documentation (app/README.md, replacing
a developers.instagram.com link that was not Juno documentation), SourceCode and GitHubRepository (MarshallBear1/juno-open-health-tools,
MIT), DOI 10.5281/zenodo.21730086 (registered; DataCite lists it as software version 1.3.0 by Gould and Tolley; zenodo.org
answers 403 to this crawler), SignUp (Google Play com.junochat.app, 200), MCPRegistry (active, 1.1.0). Not changed: hosts/,
vendors/ and well-known/ still list developers.instagram.com from the old Documentation pointer until the next pipeline
pass; x-coverage left as the pipeline wrote it.'
x-coverage:
state: unreadable
reason: no-machine-readable-spec
detail: The MCP server provides tool listings via JSON/event-stream but no OpenAPI or other machine‑readable contract is
published.
evidence:
- url: https://juno-health-tools.vercel.app/api/mcp
status: 200
checked: '2026-09-28'
x-enrichment:
date: '2026-09-28'
status: enriched
artifacts_added: 10
pass: modular-v1
engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local
Juno Chat API — frequently asked questions
Does Juno Chat have an API?
Yes. APIs.io lists 1 API from Juno Chat, including Juno Open Health Tools MCP Server.
Does Juno Chat have an MCP server?
Yes. APIs.io lists 1 MCP server for Juno Chat: Remote MCP server at juno-health-tools.vercel.app over streamable HTTP; 5 tools listed.
Is the Juno Chat API ready for AI agents?
Juno Chat has a Kin Score of 17.1 out of 100 (emerging) and an Agent Readiness score of 12.6 (agent-aware), scored by API Evangelist on 2026-11-06.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.