io.github.davidmosiah/delx-living-body
NPM · DELX-LIVING-BODY
Meta-MCP that auto-detects installed wellness connectors and composes them into one body data layer.
Available components
Last scanned (2 hours ago)
Scores higher than 68% 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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 51 of 127 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency48
- 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 67 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 365 tokens (~60/item across 6 items; 6 tools + 0 resources), lean.Pass
- 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 Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 29% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- Security disclosure: unverified → pass ▲ functional
- 23 Oct 26 0
- Security disclosure: pass → unverified ▼ functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
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/delx-living-body@0.3.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 →
Dependencies 127 packages
| Packages resolved | 127 |
|---|---|
| Deprecated | 1 |
| Stale | 50 |
| 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 →
living_body_ask Living Body — Ask ~168
Ask a wellness question; composes detected connectors in parallel and returns a synthesized answer + reasoning trace. Spawns subprocesses — requires explicit_user_intent.
| Name | Type | Req | Description |
|---|---|---|---|
| explicit_user_intent | boolean | yes | Required confirmation that the caller is acting on explicit user intent. living_body_ask spawns multiple wellness MCP subprocesses; agents must not call it speculatively. |
| privacy_mode | string | – | Passed down to child connectors. Defaults to 'structured'. 'raw' is only honored with explicit_user_intent and is discouraged for routine composition. |
| question | string | yes | Natural language question about training, recovery, sleep, nutrition or readiness. |
| response_format | string | – | – |
| sources | array | – | Restrict composition to a subset of detected connectors. Defaults to all detected. |
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | string | yes | – |
| data_snapshot | object | yes | – |
| generated_at | string | yes | – |
| reasoning | string | yes | – |
| recommendation | string | yes | – |
| sources_failed | array | yes | – |
| sources_used | array | yes | – |
No examples provided.
living_body_capabilities Living Body — Capabilities ~32
Self-description of this MCP, including the per-connector availability matrix.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| api_boundary | object | yes | – |
| auth_model | object | yes | – |
| contribution_paths | array | yes | – |
| creator | object | yes | – |
| links | object | yes | – |
| mcp_name | string | yes | – |
| per_connector_availability_matrix | array | yes | – |
| privacy_modes | array | yes | – |
| project | string | yes | – |
| recommended_agent_flow | array | yes | – |
| tools | array | yes | – |
| unofficial | boolean | yes | – |
No examples provided.
living_body_compose_context Living Body — Compose Context ~52
Return the normalized delx-wellness-context/v1 shape merged across all detected sources.
| Name | Type | Req | Description |
|---|---|---|---|
| privacy_mode | string | – | – |
| response_format | string | – | – |
| sources | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| body_battery | number | – | – |
| context_contract_version | string | yes | – |
| context_type | string | yes | – |
| cycle_phase | string | – | – |
| generated_at | string | yes | – |
| notes | array | yes | – |
| per_source | object | yes | – |
| recent_training_load | string | yes | – |
| recommended_handoff | object | – | – |
| recovery_score | number | – | – |
| sleep_score | number | – | – |
| source | string | yes | – |
| sources_failed | array | yes | – |
| sources_used | array | yes | – |
| strain_score | number | – | – |
No examples provided.
living_body_daily_brief Living Body — Daily Brief ~47
Synthetic daily briefing aggregating each detected connector's daily summary/context.
| Name | Type | Req | Description |
|---|---|---|---|
| privacy_mode | string | – | – |
| response_format | string | – | – |
| sources | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| brief_markdown | string | yes | – |
| data_snapshot | object | yes | – |
| generated_at | string | yes | – |
| highlights | array | yes | – |
| sources_failed | array | yes | – |
| sources_used | array | yes | – |
No examples provided.
living_body_health_check Living Body — Health Check (all known connectors) ~33
Returns status for every known connector — including missing ones — with install hints.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| connectors | array | yes | – |
| generated_at | string | yes | – |
| total_active | integer | yes | – |
| total_known | integer | yes | – |
| total_missing | integer | yes | – |
No examples provided.
living_body_status Living Body — Connector Detection ~33
Detect which Delx Wellness connectors are installed locally. Safe, no subprocess spawning.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| detected | array | yes | – |
| generated_at | string | yes | – |
| missing | array | yes | – |
| total_active | integer | yes | – |
| total_installed | integer | yes | – |
| total_known | integer | yes | – |
No examples provided.
How do I install the io.github.davidmosiah/delx-living-body MCP server?
io.github.davidmosiah/delx-living-body runs locally as an npm package, launched with npx -y delx-living-body. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · delx-living-body
claude mcp add davidmosiah-delx-living-body -- npx -y delx-living-body
What is the io.github.davidmosiah/delx-living-body MCP server?
io.github.davidmosiah/delx-living-body is an MCP server listed in the public MCP registry as io.github.davidmosiah/delx-living-body. Meta-MCP that auto-detects installed wellness connectors and composes them into one body data layer. This page covers its npm package (delx-living-body).
Is the io.github.davidmosiah/delx-living-body MCP server safe to use?
io.github.davidmosiah/delx-living-body scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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.davidmosiah/delx-living-body MCP server expose?
io.github.davidmosiah/delx-living-body exposes 6 tools: living_body_status, living_body_ask, living_body_daily_brief, living_body_compose_context, living_body_health_check, living_body_capabilities. Their descriptions and schemas cost roughly 365 tokens of context every time the server is loaded.
Is the io.github.davidmosiah/delx-living-body MCP server still maintained?
io.github.davidmosiah/delx-living-body 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.davidmosiah/delx-living-body MCP server under?
io.github.davidmosiah/delx-living-body declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.