Remote MCP · Endpoint
Journey for Health MCP server
No — it is up, but it requires credentials. Journey for Health answered 20 minutes ago with an authentication challenge rather than a session.
Auth requiredLast checked 20 minutes ago
Server URL
https://api.jforh.com/mcp
The endpoint is answering and asked us for credentials. That is a working server, not an outage.
- Registry name
- com.jforh/diabetes
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 100% from 14 checks
- Described by its publisher as
- Read-only glucose, meal and spike data the user chooses to share from Journey for Health.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 20 minutes ago | Credentials required | — |
| 9 days ago | Credentials required | — |
| 9 days ago | Credentials required | — |
| 11 days ago | Credentials required | — |
| 12 days ago | Credentials required | — |
| 13 days ago | Credentials required | — |
| 14 days ago | Credentials required | — |
| 15 days ago | Credentials required | — |
| 16 days ago | Credentials required | — |
| 19 days ago | Credentials required | — |
| 21 days ago | Credentials required | — |
| 24 days ago | Credentials required | — |
| 26 days ago | Credentials required | — |
| 28 days ago | Credentials required | — |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with Journey for Health and makes no claim about it beyond what these checks measured.