MCP PhenoAge Clock Server

Created By
199-biotechnologiesa year ago
MCP server for calculating biological age using the Morgan Levine PhenoAge clock
Overview

What is MCP PhenoAge Clock?

MCP PhenoAge Clock is a server application that calculates biological age using the Morgan Levine PhenoAge clock based on blood biomarkers, providing insights into health and aging.

How to use MCP PhenoAge Clock?

To use the MCP PhenoAge Clock, you can install it via NPX or NPM, or clone the repository from GitHub. After installation, you can integrate it with Claude Desktop for easy access.

Key features of MCP PhenoAge Clock?

  • Calculates biological age using blood biomarkers.
  • Provides mortality score and health interpretation.
  • Returns reference ranges and optimal values for biomarkers.

Use cases of MCP PhenoAge Clock?

  1. Estimating biological age for health assessments.
  2. Monitoring aging processes in clinical settings.
  3. Research applications in aging and healthspan studies.

FAQ from MCP PhenoAge Clock?

  • What biomarkers are required for the calculation?

The calculation requires age, albumin, creatinine, glucose, CRP, lymphocyte percentage, mean cell volume, red cell distribution width, alkaline phosphatase, and white blood cell count.

  • Is the tool for medical use?

No, it is for informational purposes only. Always consult healthcare providers for medical decisions.

  • How accurate is the biological age calculation?

The accuracy depends on the quality of the input biomarkers and adherence to measurement guidelines.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
199-biotechnologies
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

11 hours ago
Voyei

an hour ago