Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Nefesh — Real-Time Human State Awareness for AI

REMOTE · MCP.NEFESH.AI

Fuses biometric signals into a stress score (0-100) for AI adaptation. MCP + A2A native.

Available components

0 this week 75 Trust /100

Last scanned (22 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Recent critical change

Authorization (3 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1170 tokens (~167/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety88
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ingest" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
  • An AI judge read all 8 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Nov 26 +1
    • Stability: fail → pass ▲ security
  • 3 Oct 26 0
    • Authorization: unverified → fail ▼ critical
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 1.26.0 ▼ security
    • New tool “delete_subject”, which the server declares destructive security
    • Tool “check_api_key_status” rewrote its description, which is the text the model reads security
    • Tool “request_api_key” rewrote its description, which is the text the model reads security
    • “request_api_key” dropped the required parameter “email” ▼ functional
    • Destructive annotations: 0% → 50% ▲ functional
    • Schema quality: 195 → 167 ▲ functional
    • “ingest” added an optional parameter “ai_response” cosmetic
    • “ingest” added an optional parameter “user_message” cosmetic
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 2026 · Probed https://mcp.nefesh.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.nefesh.ai CN=YE2,O=Let's Encrypt,C=US 24 Sept 2026 23 Dec 2026 ECDSA 256 ECDSA-SHA384 50949ec73eb4ecdd901e0f309d38c2325b1
SANs: mcp.nefesh.ai
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.nefesh.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
nefesh.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.nefesh.ai/mcp Verified 200
http (plaintext) http://mcp.nefesh.ai/mcp HTTPS enforced 301 https://mcp.nefesh.ai/mcp
MCP tools · 7 exposed · ~1,128 tokens

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 →

Tool Tokens
check_api_key_status ~106

Check a pending API key authorization using its request_id. Use request_id exactly as returned by request_api_key, never an email. Poll every 10 seconds. awaiting_user means the user must open the URL; pending means email verification is still required. ready returns the API key once only. Store it and include it in all subsequent HTTP calls. Stop on expired; ask the user before starting another authorization.

NameTypeReqDescription
request_idstringyes–

No output schema declared.

No examples provided.

delete_subject ~44

Permanently delete all sessions and trigger memory for a subject. Irreversible. Only call when the user explicitly requests this deletion.

NameTypeReqDescription
subject_idstringyes–

No output schema declared.

No examples provided.

get_human_state ~224

Get current unified human state for a session. Call this before generating important responses. Returns: - state: calm | relaxed | focused | stressed | acute_stress - stress_score: 0-100 (lower = calmer) - confidence: 0.0-1.0 (based on signal quality and device type) - suggested_action: maintain_engagement | simplify_and_focus | de-escalate_and_shorten | pause_and_ground - action_reason: human-readable explanation of why this action was suggested - adaptation_effectiveness (on 2nd+ call): shows whether your previous suggested_action actually reduced stress — contains previous_action, stress_delta, and effective boolean. Use this to self-improve. Use suggested_action to adapt your response: calm/relaxed = full complexity, focused = shorter and structured, stressed = max 2 sentences, acute_stress = one grounding sentence only. Requires a prior ingest call to have data. Not a medical device.

NameTypeReqDescription
session_idstringyes–

No output schema declared.

No examples provided.

get_session_history ~101

Get state history for a session over time. Returns timestamped datapoints with stress_score, state, and heart_rate for each observation. Includes an overall trend: rising | falling | stable. Use minutes parameter to control the lookback window (default: 5, max: 60). Useful for detecting stress patterns during a conversation. Not a medical device.

NameTypeReqDescription
minutesinteger––
session_idstringyes–

No output schema declared.

No examples provided.

get_trigger_memory ~113

Retrieve psychological trigger profile for a subject. Returns which conversation topics consistently cause stress (active triggers) and which have been resolved over time. - active triggers: topics where stress was elevated across multiple sessions. Tread carefully. - resolved triggers: topics where stress has decreased. Safe to explore deeper. Each trigger includes observation_count, avg_score, peak_score, and last_seen. Requires prior ingest calls with the same subject_id. Not a medical device.

NameTypeReqDescription
subject_idstringyes–

No output schema declared.

No examples provided.

ingest ~417

Send biometric signals from any sensor, get unified state back. Required: session_id + timestamp (ISO 8601) + at least one signal. Send whatever you have — the API fuses all signals into one state. Common signals (highest impact): - heart_rate (bpm, 30-220) + rmssd (ms) — cardiovascular - tone: calm | tense | anxious | hostile — vocal - sentiment: -1.0 to 1.0 — textual - expression: relaxed | neutral | tense — visual For trigger memory (cross-session psychological tracking): - Include subject_id (consistent per user, hashed) Returns same fields as get_human_state plus signals_received list and topics_detected (if conversation text was included). source_device is optional but improves confidence scoring. Not a medical device.

NameTypeReqDescription
activity_level–––
ai_response–––
cognitive_load–––
confidence–––
eda–––
eeg_alpha_power–––
eeg_beta_power–––
eeg_theta_power–––
engagement–––
expression–––
gaze–––
glucose_mg_dl–––
glucose_mmol_l–––
glucose_trend–––
heart_rate–––
ibi_count–––
mean_ibi–––
pitch_variability–––
pnn50–––
posture–––
respiratory_rate–––
rmssd–––
sdnn–––
sentiment–––
session_idstringyes–
skin_temperature–––
sleep_stage–––
source_device–––
speech_rate–––
spo2–––
steps_last_minute–––
stress_score–––
subject_id–––
timestampstringyes–
tone–––
urgency–––
user_message–––

No output schema declared.

No examples provided.

request_api_key ~123

Start free API key authorization; no existing API key needed. Returns a verification_url. Ask the user to open that URL in their browser, enter their own email, then open the verification email and confirm access for their agent. This tool does not accept email addresses and does not send email. Do not choose, invent, or submit an email on the user's behalf. Poll check_api_key_status with the returned request_id at the supplied interval. Stop if the request expires. Never create new requests in a loop.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Nefesh — Real-Time Human State Awareness for AI MCP server?

Nefesh — Real-Time Human State Awareness for AI is a hosted endpoint at https://mcp.nefesh.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.nefesh.ai

# add to Claude Code
claude mcp add --transport http ai-nefesh-human-state 'https://mcp.nefesh.ai/mcp'
Common questions

What is the Nefesh — Real-Time Human State Awareness for AI MCP server?

Nefesh — Real-Time Human State Awareness for AI is an MCP server listed in the public MCP registry as ai.nefesh/human-state. Fuses biometric signals into a stress score (0-100) for AI adaptation. MCP + A2A native. This page covers its hosted endpoint (https://mcp.nefesh.ai/mcp).

Is the Nefesh — Real-Time Human State Awareness for AI MCP server safe to use?

Nefesh — Real-Time Human State Awareness for AI scores 75 out of 100 on VerifyMCP. 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 Nefesh — Real-Time Human State Awareness for AI MCP server expose?

Nefesh — Real-Time Human State Awareness for AI exposes 7 tools: get_human_state, ingest, get_trigger_memory, get_session_history, delete_subject, and 2 more. Their descriptions and schemas cost roughly 1,128 tokens of context every time the server is loaded.

Does the Nefesh — Real-Time Human State Awareness for AI MCP server require authentication?

No. We connected to Nefesh — Real-Time Human State Awareness for AI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Nefesh — Real-Time Human State Awareness for AI MCP server still maintained?

Nefesh — Real-Time Human State Awareness for AI is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Nefesh — Real-Time Human State Awareness for AI MCP server?

VerifyMCP ran 13 checks on Nefesh — Real-Time Human State Awareness for AI, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.