io.github.Goingparabolic/oak-longevity-mcp-server
NPM · OAK-LONGEVITY-MCP-SERVER
Longevity medicine MCP: medication dosing, labs, monitoring, drug interactions & intake screening
Available components
Last scanned (15 hours ago)
Scores higher than 66% 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
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 169 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1116 tokens (~124/item across 9 items; 9 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 +1
- Stability: 0.97 → pass security
- 18 Nov 26 −1
- Stability: pass → 0.97 functional
- 12 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 −2
- Stability: pass → 0.87 functional
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
- 26 Oct 26 +1
- Stability: 0.97 → 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 21 Nov 2026 · Analysed npm/oak-longevity-mcp-server@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
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 | 31 |
| 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 →
check_contraindications Screen Patient for Contraindications ~193
Given a medication and a patient profile (age, sex, conditions, current medications), screens against absolute and relative contraindications and known drug interactions and returns an overall verdict — PASS, FLAG (proceed with caution / address first), or REJECT (do not prescribe) — with the specific triggering findings and clinical notes. PREMIUM tier.
| Name | Type | Req | Description |
|---|---|---|---|
| age | number | – | Patient age in years. |
| conditions | array | – | Patient conditions / history (e.g. ["prostate cancer", "hematocrit 55%"]). A comma-separated string is also accepted. |
| currentMedications | array | – | Current medications (e.g. ["warfarin", "nitroglycerin"]). A comma-separated string is also accepted. |
| medication | string | yes | Medication name, id, or brand/alias to screen. |
| sex | string | – | Patient sex (e.g. "male", "female"). |
No output schema declared.
No examples provided.
check_drug_interactions Check Drug Interactions ~92
Given a list of medications (catalog drugs and/or outside agents like "warfarin", "nitrates", "insulin"), returns pairwise interaction warnings ranked by severity (contraindicated > major > moderate > minor), each with the mechanism/effect and management. PREMIUM tier.
| Name | Type | Req | Description |
|---|---|---|---|
| medications | array | yes | List of medications to check against each other. A comma-separated string is also accepted. |
No output schema declared.
No examples provided.
get_dosing_protocol Get Evidence-Based Dosing Protocol ~113
Given a medication (and optionally an indication), returns evidence-based dosing: route, starting dose, titration schedule, maintenance range, maximum, evidence grade, and clinical pearls. When an indication is supplied, returns the best-matching protocol; otherwise returns all indications for the medication. PREMIUM tier.
| Name | Type | Req | Description |
|---|---|---|---|
| indication | string | – | Optional indication to narrow the protocol (e.g. "weight management", "TRT", "longevity"). |
| medication | string | yes | Medication name, id, or brand/alias. |
No output schema declared.
No examples provided.
get_fda_status Get FDA / Compounding Regulatory Status ~96
Given a compound (name, id, or brand/alias), returns its current FDA approval status, DEA/Rx schedule, compounding pathway (503A/503B, shortage-list and bulk-substance considerations), FDA-approved uses, an off-label note, and reference pointers. Essential for compliant compounded-medication practice. FREE tier.
| Name | Type | Req | Description |
|---|---|---|---|
| compound | string | yes | Compound/medication name, id, or brand/alias. |
No output schema declared.
No examples provided.
get_medication_details Get Medication Details ~99
Given a medication name, id, or brand/alias (e.g. "tirzepatide", "Ozempic", "copper peptide"), returns its drug class, mechanism of action, available formulations, who it is for (candidate profile), who it is NOT for (at-a-glance cautions), and DEA/Rx schedule. FREE tier.
| Name | Type | Req | Description |
|---|---|---|---|
| medication | string | yes | Medication name, id, or brand/alias. |
No output schema declared.
No examples provided.
get_medication_list List Longevity Medications ~119
Returns the full catalog of longevity & metabolic medications, grouped by category (Weight Management, Peptide Therapy, Hormone Optimization, Longevity & Metabolic, Sexual Health, Immune & Inflammation, Hair Restoration, Dermatology). Each entry includes the medication id (used by other tools), display name, drug class, and DEA/Rx schedule. Optionally filter by a category id or name. FREE tier.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter (id like "peptide-therapy" or label like "Hormone Optimization"). |
No output schema declared.
No examples provided.
get_monitoring_plan Get Ongoing Monitoring Plan ~67
Given a medication, returns the ongoing monitoring requirements once therapy has started — what to check, at what interval, and the action/threshold for each. Use to build a follow-up schedule. PREMIUM tier.
| Name | Type | Req | Description |
|---|---|---|---|
| medication | string | yes | Medication name, id, or brand/alias. |
No output schema declared.
No examples provided.
get_required_labs Get Required Baseline Labs ~66
Given a medication, returns the recommended baseline labs/assessments to obtain BEFORE prescribing — grouped into panels with the clinical rationale for each. Use to build a pre-treatment workup. PREMIUM tier.
| Name | Type | Req | Description |
|---|---|---|---|
| medication | string | yes | Medication name, id, or brand/alias. |
No output schema declared.
No examples provided.
screen_patient_intake Screen Patient Intake → Suggested Pathways ~131
Given a patient’s symptoms and/or goals (free text or a list — e.g. "fatigue, low libido, want to lose weight"), suggests the most relevant longevity treatment pathways, each with first-line and adjunct medications, a suggested workup, and key things to avoid. Use to triage an intake. PREMIUM tier.
| Name | Type | Req | Description |
|---|---|---|---|
| goals | array | – | Optional explicit list of goals/symptoms. Combined with `symptoms` if both given. |
| symptoms | string | – | Patient symptoms and/or goals as free text (e.g. "tired, low sex drive, brain fog"). |
No output schema declared.
No examples provided.
How do I install the io.github.Goingparabolic/oak-longevity-mcp-server server?
io.github.Goingparabolic/oak-longevity-mcp-server runs locally as an npm package, launched with npx -y oak-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 · oak-longevity-mcp-server
claude mcp add goingparabolic-oak-longevity-mcp-server -- npx -y oak-longevity-mcp-server
What is the io.github.Goingparabolic/oak-longevity-mcp-server server?
io.github.Goingparabolic/oak-longevity-mcp-server is listed in the public MCP registry as io.github.Goingparabolic/oak-longevity-mcp-server. Longevity medicine MCP: medication dosing, labs, monitoring, drug interactions & intake screening. This page covers its npm package (oak-longevity-mcp-server).
Is the io.github.Goingparabolic/oak-longevity-mcp-server server safe to use?
io.github.Goingparabolic/oak-longevity-mcp-server scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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.Goingparabolic/oak-longevity-mcp-server server expose?
io.github.Goingparabolic/oak-longevity-mcp-server exposes 9 tools: get_medication_list, get_medication_details, get_fda_status, get_dosing_protocol, get_required_labs, and 4 more. Their descriptions and schemas cost roughly 976 tokens of context every time the server is loaded.
Is the io.github.Goingparabolic/oak-longevity-mcp-server server still maintained?
io.github.Goingparabolic/oak-longevity-mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 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.Goingparabolic/oak-longevity-mcp-server server under?
io.github.Goingparabolic/oak-longevity-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.Goingparabolic/oak-longevity-mcp-server server?
VerifyMCP ran 16 checks on io.github.Goingparabolic/oak-longevity-mcp-server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.