Analytics
philongevity.com
Provides synthetic biomarker analysis and scoring using the PRISM engine.
ENDPOINT 1
https://philongevity.com/mcp
MCP server metadata
- Name
- phi-longevity
- Version
- 0.7.2
Phi Longevity PRISM — longevity-optimized analysis of biomarker panels. For research/education with SYNTHETIC or de-identified data only. Do NOT submit protected health information (PHI). This endpoint is stateless and does not store inputs.
Known tools 4
analyze_biomarkersAnalyze a SYNTHETIC biomarker panel with Phi Longevity's PRISM engine.
Inferred read-onlylist_supported_biomarkersList the biomarkers PRISM scores, with units and reference ranges, grouped by clinical pillar.
Inferred read-onlyget_methodologySummarize how the Phi Score works (5 clinical pillars + weights) and link to the full methodology.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.phi-longevity]
url = "https://philongevity.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"phi-longevity": {
"type": "http",
"url": "https://philongevity.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: phi-longevity
Remote MCP URL: https://philongevity.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"phi-longevity": {
"url": "https://philongevity.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"phi-longevity": {
"type": "http",
"url": "https://philongevity.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "phi-longevity",
"transport": "streamable-http",
"url": "https://philongevity.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.