Delx Living Body
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| living_body_agent_manifestA | Machine-readable install and operating instructions for AI agents. Call first when onboarding. |
| living_body_connection_statusA | Ready/not-ready snapshot of local connector detection without calling vendor APIs or child data tools. |
| living_body_data_inventoryA | Static inventory of composed domains, known connectors, privacy modes and recommended first calls. No live child calls. |
| living_body_statusA | Detect which Delx Wellness connectors are installed locally. Safe, no subprocess spawning. |
| living_body_askA | Ask a wellness question; composes detected connectors in parallel and returns a synthesized answer + reasoning trace. Spawns subprocesses — requires explicit_user_intent. |
| living_body_daily_briefC | Synthetic daily briefing aggregating each detected connector's daily summary/context. |
| living_body_compose_contextC | Return the normalized delx-wellness-context/v1 shape merged across all detected sources. |
| living_body_health_checkA | Returns status for every known connector — including missing ones — with install hints. |
| living_body_capabilitiesA | Self-description of this MCP, including the per-connector availability matrix. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| living_body_data_inventory | Static inventory of composed domains, known connectors and recommended first calls. |
| living_body_agent_manifest | Machine-readable install and operating instructions for AI agents. |
| living_body_capabilities | Self-description and per-connector availability matrix. |
| living_body_connection_status | Live detection snapshot of installed wellness connectors (no child data tools). |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/delx-living-body'
If you have feedback or need assistance with the MCP directory API, please join our Discord server