mcpbeat Sign in

Journey for Health MCP Server

answering

Journey for Health is answering right now. Last checked 1 min ago.

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

Uptime history 24 days of history
24 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
391 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Journey for Health every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add diabetes --transport http https://api.jforh.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.jforh.com/mcp
~/.codex/config.toml
[mcp_servers.diabetes]
url = "https://api.jforh.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "diabetes": {
      "url": "https://api.jforh.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "diabetes": {
      "type": "http",
      "url": "https://api.jforh.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://api.jforh.com/mcp streamable-http sign-in 234 ms 1 min ago

Alternatives to Journey for Health

same job, measured the same way
Agentguard47
by bmdhodl

Read-only MCP server for coding-agent traces, alerts, costs, usage, and budget health.

51 installs/wk local only
Marrow
by skeletonarmy

Marrow Health: your Apple Health data over MCP, from the free iOS app. Reads, and writes on demand.

370 installs/wk local only
Starbelo
by starbelo

Search real AI money-making use cases, AI tools and prompts from Starbelo. Free, read-only.

3 tools answering
Maplith Bridge
by maplith

Share a folder of data files read-only over MCP, and fill it from PostgreSQL under a read-only role.

57 installs/wk local only
Atlasburn
by atlasburn

Ask your AI cost, runway, and guardrails from your real AtlasBurn data — read-only.

answering
AI Form API
by sum-eet

Create forms, share the link and read responses as JSON or CSV from your AI agent.

answering
codeDB Lens
by codedb-io

Read-only health checks and data questions for SQL Server and PostgreSQL, with your saved profiles.

local only
Stymie Golf
by thatdudefreak

Read-only US golf course, scorecard, equipment, deal, and golf-trip data for AI agents.

12 tools answering

Journey for Health — questions

Answers built from our own checks of this server.

Why is there no tool list for Journey for Health?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Journey for Health working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 391 ms. The bar chart above shows every period we have measured.
How do I connect Journey for Health?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Journey for Health?
No API key is involved. Journey for Health answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Journey for Health?
It answers our handshake in 391 ms on average, which is faster than 33% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.