Libby Health

health.libbyPublished by libby.healthOfficial publisherv1.0.0Updated Oct 26, 2026

Read-only access to your own lab markers, trends, and reports.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Remote MCP server giving an assistant read-only access to your own Libby Health lab markers, trends and reports.

What you can do
  • Read your own lab markers from your Libby Health account
  • Review trends in those markers over time
  • Retrieve your health reports
  • All access is read-only, so the assistant can look things up but not change your data
When to use it
Useful when you want an assistant to look up your own lab results, follow how a marker has changed over time, or summarize your health reports while discussing them.
Requirements
A remote endpoint at app.libby.health over streamable HTTP; no packages or environment variables. Sign-in is via OAuth, which is required, so you need a Libby Health account.
Before you install
The server exposes personal health data (lab markers, trends, reports) to the assistant, so connect only clients you trust and review what the OAuth grant allows. Access is described as read-only, so no changes to your records are expected.

Installation

In SourceWeft

  1. Open Libby 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/health.libby%2Flibby-health/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": {
    "libby-health": {
      "type": "http",
      "url": "https://app.libby.health/api/mcp/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 22, 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.