Journey for Health

com.jforhPublished by jforh.comOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Remote MCP server that gives an assistant read-only access to glucose, meal and spike data a user chooses to share from Journey for Health.

What you can do
  • Read glucose readings the user has chosen to share from Journey for Health.
  • Read meal records linked to that shared data.
  • Read spike data derived from the shared glucose and meal history.
  • Access is read-only, so the assistant can review and discuss the data but not change it.
When to use it
Useful when someone wants an assistant to look at their own Journey for Health glucose, meal and spike records and discuss patterns, without exporting files by hand. Only relevant if the user has a Journey for Health account and is willing to share that data.
Requirements
A remote endpoint at api.jforh.com over streamable HTTP; no local package or runtime. OAuth authentication is required, so the user must sign in and authorize access. The user must choose which Journey for Health data to share.
Before you install
The server handles health data (glucose, meals, spikes), which is sensitive; sharing is controlled by the user but the assistant will see whatever is shared. Access is granted through OAuth, so review the scopes and permissions during sign-in. The description states access is read-only, but confirm this before relying on it.

Installation

In SourceWeft

  1. Open Journey for Health in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.jforh%2Fdiabetes/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "journey-for-health": {
      "type": "http",
      "url": "https://api.jforh.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 15, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.