Mmcp.market

Delx Living Body MCP server

by davidmosiah·io.github.davidmosiah/delx-living-body·v0.3.0

Meta-MCP that auto-detects installed wellness connectors and composes them into one body data layer.

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Delx Living Body yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Delx Living Body tools (6)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • living_body_ask

    Ask a wellness question; composes detected connectors in parallel and returns a synthesized answer + reasoning trace. Spawns subprocesses — requires explicit_user_intent.

  • living_body_capabilities

    Self-description of this MCP, including the per-connector availability matrix.

  • living_body_compose_context

    Return the normalized delx-wellness-context/v1 shape merged across all detected sources.

  • living_body_daily_brief

    Synthetic daily briefing aggregating each detected connector's daily summary/context.

  • living_body_health_check

    Returns status for every known connector — including missing ones — with install hints.

  • living_body_status

    Detect which Delx Wellness connectors are installed locally. Safe, no subprocess spawning.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan32 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 19 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the Delx Living Body repository's README, as published. We do not edit it. Read it on GitHub

delx-living-body

Meta-MCP that turns 15 wellness MCPs into one unified body data layer for AI agents.

Today, answering "should I train hard today?" forces an agent to orchestrate WHOOP recovery, Garmin Body Battery, Oura sleep, Nourish nutrition, and cycle phase across five separate MCP servers. That's brittle for users and confusing for the agent.

delx-living-body is one MCP server that:

  1. Auto-detects which of 15 Delx Wellness connectors you already have installed locally — no manual config
  2. Composes parallel calls to the right subset
  3. Synthesizes a natural-language answer plus a structured reasoning trace and per-source confidence — using rule-based reasoning, no LLM calls

Install it once. Get a unified body data layer. Works with whatever wellness MCPs you already have.

Compose matrix (which children have *_series vs summary-only): docs/compose-matrix.md. Pin drift: docs/pin-drift.md.

If it helps your agent workflow, star the repo. Stars make the single-entry Delx Wellness path easier for other AI builders to find.

HTTP (v2 stateless)

Default is stdio. Optional Streamable HTTP — no session id, JSON responses, loopback only:

npx -y delx-living-body --http
# GET  http://127.0.0.1:3030/health
# POST http://127.0.0.1:3030/mcp   (sessionless)

Env: LIVINGBODYMCPHOST, LIVINGBODYMCPPORT, LIVINGBODYMCP_TRANSPORT=http.

  • Try it now, no accounts — npx -y delx-living-body demo ("Should I train hard today?")
  • Run it in Claude · Cursor · ChatGPT · Hermes · OpenClaw — see agent setup examples
  • Local-first — delx-living-body never reads your tokens; children read their own creds (privacy)
  • Which connector should I use? — start at the Delx Wellness front door

The three flagship connectors this composes over: google-health-mcp (google-health-mcp-unofficial), garmin-mcp (garmin-mcp-unofficial), and wellness-nourish (wellness-nourish).

Install

npx -y delx-living-body

That's the whole install. No OAuth flow, no API keys — delx-living-body has no auth of its own. Each child connector handles its own credentials.

See the full agent demo → "Should I train hard today?" (no accounts needed)

npx -y delx-living-body demo

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

Runs npx -y delx-living-body on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add delx-living-body -- npx -y delx-living-body
Add to Cursor

Delx Living Body: common questions

Is Delx Living Body MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Delx Living Body safety report
How do I install Delx Living Body?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does Delx Living Body need an API key?
No secret keys are declared. It reads 4 settings from the environment.
Is Delx Living Body maintained?
The last commit was 19 days ago (2026-09-07). The latest release is v0.3.0.

More from davidmosiah →