com.jforh/diabetes

Journey for Health

Is the Journey for Health MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-26.

Read-only glucose, meal and spike data the user chooses to share from Journey for Health.

needs auth probed 2026-11-15 · unchanged since 2026-10-26 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","id":0,"error":{"code":-32001,"message":"unauthorized"}}

Endpoint: https://api.jforh.com/mcp (streamable-http)
Host: api.jforh.com
Getting access: OAuth without dynamic client registration. Ask the publisher for a client id first; with it, a client can run the consent.
Authorization server api.jforh.com, PKCE S256, grants authorization_code.
Scopes glucose_summary meals spikes care_summary cgm_setup_status.
Read from the server's public OAuth metadata, without a token. Method.
Website: https://jforh.com/diabetes/connect-ai
Registry: active, updated 2026-10-15 · registry entry

More servers

Servers that mention diabetes or journey or health.

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.

Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.