Nefesh — Real Time Human State Awareness For AI
Give agents a live 0–100 stress score from fused biometric signals so replies and workflows can adapt to the human’s state.
Overview
Nefesh Human State is a MCP server for the Build phase that exposes a 0–100 stress score from fused biometric signals so AI agents can adapt in real time.
What is this MCP server?
- Fuses biometric signals into a single stress score from 0 to 100 for downstream AI logic
- Native MCP (streamable HTTP) plus A2A-oriented integration per server description
- Optional X-Nefesh-Key header or request_api_key tool when no key is configured
- Free tier messaging: 1,000 calls/month via nefesh.ai signup
- Open-source server repository on GitHub (nefesh-ai/nefesh-mcp-server)
- Stress score range: 0–100 per server description
- Free tier: 1,000 calls/month noted in manifest header docs
- Published server version: 4.0.0
What problem does it solve?
Agents treat every session the same even when the human is stressed, which makes coaching, onboarding, and support feel tone-deaf and unsafe to trust.
Who is it for?
Builders creating adaptive agents where biometric-aware pacing materially improves UX and you already handle consent and signal collection.
Skip if: Products without biometric input, clinical diagnostic claims, or teams unwilling to manage API keys and privacy compliance.
What do I get? / Deliverables
After registration and key setup, your agent can read a stress score and branch prompts, shortcuts, or escalation paths based on human state.
- Live stress score (0–100) available to agent tool calls
- Adaptive prompt or policy branches keyed off human-state readings
- Documented MCP remote configuration for team agents
Recommended MCP Servers
Journey fit
Canonical shelf is Build because you implement adaptive agent behavior as tooling once the product concept exists. Agent-tooling is where MCP and A2A endpoints are registered and stress-aware prompts or policies are wired in.
How it compares
Real-time human-state MCP plus A2A hooks, not a static system-prompt skill or generic sentiment classifier on chat text alone.
Common Questions / FAQ
Who is Nefesh Human State for?
Indie developers and small teams building agents that should change behavior when users show elevated stress from biometric fusion.
When should I use Nefesh Human State?
Use it while building agent-tooling when you need a numeric stress signal (0–100) to drive adaptive responses, and again when tuning launch or lifecycle flows.
How do I add Nefesh Human State to my agent?
Add the remote MCP URL https://mcp.nefesh.ai/mcp in your client, supply X-Nefesh-Key from https://nefesh.ai/signup or call request_api_key from the server, then use the stress tools in your agent workflow.