Skip to content

Nefesh — Real-Time Human State Awareness for AI MCP server

ai.nefesh/human-statenefesh.aistreamable-httpv4.0.0Scanned

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

7 tools: 1 can delete or cancel things, 1 do something that can't be undone, 1 change things and 4 only read.

Tools: 1 delete, 1 irreversible, 1 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Nefesh — Real-Time Human State Awareness for AI MCP server can do

The Nefesh — Real-Time Human State Awareness for AI MCP server is published by nefesh.ai, a domain the MCP Registry verified. It has 7 tools. It can delete or cancel things (1 tool: delete_subject), do things that cannot be undone, such as sending, paying or publishing (ingest) and create or change data (1 tool: request_api_key). 4 tools only read.

1 tool can send data out of your system (ingest).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 4.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Deletes or cancels 1Claude Code: deny
  • delete_subjectPermanently delete all sessions and trigger memory for a subject.No findings

    Why it is in this group

    • The name "delete_subject" says "delete": a word for removing or ending something.
    • The description says "Permanently delete".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Permanently delete all sessions and trigger memory for a subject. Irreversible. Only call when the user explicitly requests this deletion.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
Can't be undone 1Claude Code: ask
  • ingestSend biometric signals from any sensor, get unified state back.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe description's first verb is "send": it sends or publishes something to other people.
    Description, as the server wrote it
    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.
Changes things 1Claude Code: ask
  • request_api_keyStart free API key authorization; no existing API key needed.No findings

    Why it is in this group

    • The name "request_api_key" says "request": a word for a change.
    Description, as the server wrote it
    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.
Only reads 4Show 4 read-only tools
  • check_api_key_statusCheck a pending API key authorization using its request_id.No findings

    Why it is in this group

    • The name "check_api_key_status" says "status": a word for reading.
    Description, as the server wrote it
    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.
  • get_human_stateGet current unified human state for a session.No findings

    Why it is in this group

    • The name "get_human_state" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_session_historyGet state history for a session over time.No findings

    Why it is in this group

    • The name "get_session_history" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_trigger_memoryRetrieve psychological trigger profile for a subject.No findings

    Why it is in this group

    • The name "get_trigger_memory" says "get": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:26 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.nefesh.ai/mcp: tools/list returned 7 tools to an anonymous client, including delete_subject (destructive), ingest (irreversible), request_api_key (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 4.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http human-state https://mcp.nefesh.ai/mcp
claude mcp add --transport http human-state https://mcp.nefesh.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__human-state__get_human_state",
      "mcp__human-state__get_trigger_memory",
      "mcp__human-state__get_session_history",
      "mcp__human-state__check_api_key_status"
    ],
    "ask": [
      "mcp__human-state__ingest",
      "mcp__human-state__request_api_key"
    ],
    "deny": [
      "mcp__human-state__delete_subject"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as human-state. Review it before you use it.

Capability tags behind 1 rule
  • mcp__human-state__ingest outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.nefesh/human-state/verify?hash=9b972e58569212733e2d5e4ffa5e29bba65c5445922cb962ef075aac448b3ccf" | jq -e '.changed == false'

Pinned hash 9b972e585692, from Nov 10, 2026, 03:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.nefesh/human-state/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.nefesh/human-state
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.nefesh/human-state.svg)](https://radar.anlyon.com/servers/ai.nefesh/human-state)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:42 UTC.

Nefesh — Real-Time Human State Awareness for AI MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

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

No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Nefesh — Real-Time Human State Awareness for AI MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: delete_subject.

Can the Nefesh — Real-Time Human State Awareness for AI MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: ingest.

What tools does the Nefesh — Real-Time Human State Awareness for AI MCP server have?

7 tools: 1 destructive, 1 irreversible, 1 write, 4 read. delete_subject, ingest, request_api_key, get_human_state, get_trigger_memory, get_session_history and check_api_key_status.

Does the Nefesh — Real-Time Human State Awareness for AI MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Nefesh — Real-Time Human State Awareness for AI MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): ingest.

Has the Nefesh — Real-Time Human State Awareness for AI MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.