request_api_keyLABSCO SUMMARY
It tells the agent whether its last move worked.
Reading a state is the easy half. From the second call in a session the response carries the previous action, the previous and current scores, and a plain boolean for whether stress actually fell — which is the piece an agent needs to change strategy rather than repeat itself. Video and audio stay on the device; the server takes derived signals, not recordings.
What it is
A hosted MCP server that takes sensor signals (heart rate, HRV, voice tone, expression, text sentiment) and returns a unified state with a machine-readable action the agent can follow. It is also reachable as an A2A agent for agent-to-agent use.
What you get
get_human_state— a stress state, a suggested action such as maintain, simplify, de-escalate or pause, and the closed-loop feedback fieldingest— send biometric signals and get the unified state back, with a subject id if you want trigger memoryget_trigger_memory— which topics are still causing stress and which have resolved over timeget_session_history— timestamped state history with a rising, falling or stable trendrequest_api_keyandcheck_api_key_status— the agent asks for your real email, you click the verification link, it collects the key itself- 6 tools in total; the two key-provisioning ones need no authentication
- The same capabilities as A2A skills for agent-to-agent calls
Requirements
An MCP client that speaks Streamable HTTP — point it at https://mcp.nefesh.ai/mcp. No local install. Authentication is an API key in the X-Nefesh-Key header, or the agent can self-provision one: connect with no key, ask it to request a key with your real email address, and click the verification link. The free tier covers 1,000 calls a month with all signal types and no credit card. MIT licensed.
Setup effort
Paste a URL with a key — add the endpoint to your client
USE CASES
Making an assistant back off when the user is under load
Read the state before a long reply and follow the suggested action instead of guessing at tone.
Closing the loop on your own adaptations
Call again after adjusting and read whether the score moved in the right direction before deciding what to do next.
Learning what actually sets someone off
Send signals with a subject id over time, then read the trigger profile for active versus resolved topics.
6 tools
Listed in project docs. Your client may show a different list.
check_api_key_statusget_human_stateingestget_trigger_memoryget_session_historyBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
INSTALLATION
Connect your client
Add the endpoint to your client.
Server setup
https://mcp.nefesh.ai/mcpMCP Clients
Cursor, Other MCP clients
{
"mcpServers": {
"nefesh": {
"url": "https://mcp.nefesh.ai/mcp",
"headers": {
"X-Nefesh-Key": "<YOUR_NEFESH_KEY>"
}
}
}
}Windsurf
{
"mcpServers": {
"nefesh": {
"serverUrl": "https://mcp.nefesh.ai/mcp",
"headers": {
"X-Nefesh-Key": "<YOUR_NEFESH_KEY>"
}
}
}
}VS Code
{
"servers": {
"nefesh": {
"type": "http",
"url": "https://mcp.nefesh.ai/mcp",
"headers": {
"X-Nefesh-Key": "<YOUR_API_KEY>"
}
}
}
}Zed
{
"context_servers": {
"nefesh": {
"url": "https://mcp.nefesh.ai/mcp",
"headers": {
"X-Nefesh-Key": "<YOUR_API_KEY>"
}
}
}
}Codex
[mcp_servers.nefesh]
url = "https://mcp.nefesh.ai/mcp"Continue
{
"mcpServers": [
{
"name": "nefesh",
"type": "streamable-http",
"url": "https://mcp.nefesh.ai/mcp"
}
]
}