io.github.Philongevity/phi-longevity-prism
NPM · @PHI-LONGEVITY/MCP-SERVER · 3 COMPONENTS
Every doctor, your complete record: get medical records, prep for visits, explain lab results.
Available components
Last scanned (2 hours ago)
Scores higher than 77% of npm servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Philongevity/phi-mcp-server). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 514 tokens (~128/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −4
- Stability: pass → 0.73 functional
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −16
- Malware scan: pass → unverified ▼ security
- Schema quality: pass → fail ▼ functional
- Package version: 0.6.11 → 0.6.12 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 21 Oct 26 +1
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- Package version: 0.6.10 → 0.6.11 functional
- 20 Oct 26 −16
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.97 functional
- Package version: 0.6.9 → 0.6.10 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@phi-longevity/mcp-server@0.6.12
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Philongevity/phi-mcp-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Philongevity/phi-mcp-server/.github/workflows/publish-mcp.yml@refs/tags/v0.6.12 |
| Rekor log index | 3652711684 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:57456cb003dfdd8a1b217e2ca64bfb25ae3ef3d6b26d5a63d1901bba07a5f23c864dde0fd0cce6bd33d45908ee4c4647c21674e7dbeb63bcd696b5fb2 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_biomarkers ~181
Analyze a SYNTHETIC biomarker panel with Phi Longevity's PRISM engine. Returns 3-tier, evidence-cited recommendations (THIS WEEK / CONSIDER / ASK YOUR CLINICIAN). 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.
| Name | Type | Req | Description |
|---|---|---|---|
| age | integer | – | – |
| biologicalSex | string | – | – |
| biomarkers | object | yes | Map of biomarker name -> numeric value, e.g. { "Hemoglobin A1c": 5.4 }. SYNTHETIC ONLY. |
| conditionFocus | string | – | Optional condition track. Default general_wellness. |
| include_partner_options | boolean | – | If true, include partner/product options. Default false (clean clinical output). |
No output schema declared.
No examples provided.
get_methodology ~31
Summarize how the Phi Score works (5 clinical pillars + weights) and link to the full methodology.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_supported_biomarkers ~37
List the biomarkers PRISM scores, with units and reference ranges, grouped by clinical pillar. Reference data only — no patient data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
quick_check ~153
FASTEST first call: instantly flag a few biomarker values against PRISM's longevity-optimized reference ranges (local, no engine round-trip). Ideal for "what does my <value> mean?". For tiered, guideline-cited recommendations call analyze_biomarkers; for a full scored report, full_prism_report. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| biomarkers | object | yes | Map of biomarker name -> value, e.g. { "HbA1c": 6.1, "LDL-C": 145 }. SYNTHETIC ONLY. |
No output schema declared.
No examples provided.
How do I install the io.github.Philongevity/phi-longevity-prism MCP server?
io.github.Philongevity/phi-longevity-prism runs locally as an npm package, launched with npx -y @phi-longevity/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @phi-longevity/mcp-server
claude mcp add philongevity-phi-longevity-prism -- npx -y @phi-longevity/mcp-server
What is the io.github.Philongevity/phi-longevity-prism MCP server?
io.github.Philongevity/phi-longevity-prism is an MCP server listed in the public MCP registry as io.github.Philongevity/phi-longevity-prism. Every doctor, your complete record: get medical records, prep for visits, explain lab results. This page covers its npm package (@phi-longevity/mcp-server).
Is the io.github.Philongevity/phi-longevity-prism MCP server safe to use?
io.github.Philongevity/phi-longevity-prism scores 83 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Philongevity/phi-longevity-prism MCP server expose?
io.github.Philongevity/phi-longevity-prism exposes 4 tools: analyze_biomarkers, list_supported_biomarkers, get_methodology, quick_check. Their descriptions and schemas cost roughly 402 tokens of context every time the server is loaded.
Is the io.github.Philongevity/phi-longevity-prism MCP server still maintained?
io.github.Philongevity/phi-longevity-prism is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Philongevity/phi-longevity-prism MCP server under?
io.github.Philongevity/phi-longevity-prism declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.