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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago