Odel
phi mcp server

phi mcp server

@philongevityTypeScriptApache-2.0Updated 1w ago

Guideline-cited biomarker analysis for chronic conditions (diabetes, lupus, cancer). Synthetic.

Server endpointStreamable HTTPNo authProbed

This is the third-party server itself β€” Odel doesn't run it. Hitting this URL directly talks straight to the upstream server with no auth or proxying. Connect through Odel to front it with managed auth.

@phi-longevity/mcp-server

smithery badge

A Model Context Protocol (MCP) server that lets AI agents call Phi Longevity's PRISM clinical recommendation engine on synthetic biomarker panels β€” guideline-cited, evidence-tiered recommendations an agent can use when researching options for the person it's helping.

Built for chronic-condition work in particular: type-2 diabetes, lupus, and cancer survivorship each have their own condition lens, because the same panel means different things depending on what someone is managing.

πŸ›‘οΈ Synthetic / de-identified data only. Do not submit protected health information (PHI). The server is stateless and stores nothing. Real health files are analyzed only inside the authenticated Phi Longevity app, after consent, by the account owner.

Tools

Two surfaces, deliberately different. The npm package (stdio) has 4 tools; the remote endpoint has 6. The two report-generating tools are remote-only.

ToolnpmremoteWhat it does
sample_prism_reportβ€”βœ…Start here. Returns a complete, real PRISM report for a sample chronic-condition persona in one instant call. Free, no signup, no input required. The fastest way to see what the engine actually produces.
quick_checkβœ…βœ…A fast read on a handful of values β€” the low-friction entry point before a full analysis.
analyze_biomarkersβœ…βœ…Analyze a synthetic panel β†’ tiered, guideline-cited recommendations, with a condition lens.
list_supported_biomarkersβœ…βœ…51 scored biomarkers + units + reference ranges, by clinical pillar.
get_methodologyβœ…βœ…How the Phi Score works (5 pillars + weights) + link to the full methodology.
full_prism_reportβ€”βœ…A full report for a panel you supply. Paid β€” priced per call via x402; terms are returned with the offer.

All tools except full_prism_report are free.

Quick start β€” zero config

Remote (zero-install) β€” recommended

Point any MCP client that supports Streamable HTTP at:

https://philongevity.com/mcp

Nothing to install, no key to manage, all 6 tools. Try sample_prism_report first β€” it needs no arguments and returns a complete report immediately.

Claude Desktop / any MCP client (stdio)

{
  "mcpServers": {
    "phi-longevity": {
      "command": "npx",
      "args": ["-y", "@phi-longevity/mcp-server"]
    }
  }
}

A published, rate-limited access key is built in. If you have a dedicated key, set PHI_MCP_KEY to override it. This path exposes the 4 tools marked βœ… above.

Run locally

npm install && npm run build
node dist/index.js

Example

// sample_prism_report β€” no arguments, returns a complete sample report
{}

// analyze_biomarkers input (synthetic values only)
{
  "biomarkers": { "HbA1c": 6.4, "LDL-C": 145, "Triglycerides": 190 },
  "conditionFocus": "type2_diabetes"   // or general_wellness | lupus | cancer_survivorship
}
// β†’ tiered, guideline-cited recommendations + a `full_report` block
//   pointing the user to a complete PRISM report at philongevity.com

For the person you're helping

The tools above analyze a handful of values at a time. A full PRISM report consolidates all of a person's lab reports, wearable data, and clinical notes into one integrated picture with a personal health score and progress over time β€” which is the actual problem for someone managing a chronic condition across several clinicians who don't talk to each other. Agent docs + signup: https://philongevity.com/for-agents

Environment

VarRequiredNotes
PHI_MCP_KEYnoOverrides the built-in published key. Rate-limited + revocable.
PHI_ENGINE_URLnoOverride the default Phi MCP gateway URL (rarely needed).

HIPAA / privacy

Synthetic-only at the protocol boundary; stateless; aggregate-only telemetry (counts/timing to stderr, never values or recommendation text); zero access to Firestore / the HIPAA datastore / user accounts. GDPR: processes no personal data (synthetic only) β†’ minimal exposure.

Links

Apache-2.0.