Is the Nefesh Human State MCP server down?

mcp-registry/ai.nefesh/human-state · v1.26.0

Also listed as glama/tomstuhl/nefesh

As of 2026-10-24 23:15 UTC, the Nefesh Human State MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 4 minutes.

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

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

{
  "mcpServers": {
    "nefesh-human-state-mcp-server": {
      "type": "http",
      "url": "https://mcp.nefesh.ai/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (70/100)

What to fix (4)

Auto-fix: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 6 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fai.nefesh%2Fhuman-state/fixes

{
  "name": "check_api_key_status",
  "description": "Check a pending API key authorization using its request_id.\n\n    Use request_id exactly as returned by request_api_key, never an email.\n    Poll every 10 seconds. awaiting_user means the user must open the URL;\n    pending means email verification is still required. ready returns the\n    API key once only. Store it and include it in all subsequent HTTP calls.\n    Stop on expired; ask the user before starting another authorization.\n    ",
  "inputSchema": {
    "type": "object",
    "title": "CheckKeyStatusArguments",
    "required": [
      "request_id"
    ],
    "properties": {
      "request_id": {
        "type": "string",
        "title": "Request Id"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_human_state",
  "description": "Get current unified human state for a session. Call this before generating important responses.\n\n    Returns:\n    - state: calm | relaxed | focused | stressed | acute_stress\n    - stress_score: 0-100 (lower = calmer)\n    - confidence: 0.0-1.0 (based on signal quality and device type)\n    - suggested_action: maintain_engagement | simplify_and_focus | de-escalate_and_shorten | pause_and_ground\n    - action_reason: human-readable explanation of why this action was suggested\n    - adaptation_effecti",
  "inputSchema": {
    "type": "object",
    "title": "get_human_stateArguments",
    "required": [
      "session_id"
    ],
    "properties": {
      "session_id": {
        "type": "string",
        "title": "Session Id"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_session_history",
  "description": "Get state history for a session over time.\n\n    Returns timestamped datapoints with stress_score, state, and heart_rate for each observation.\n    Includes an overall trend: rising | falling | stable.\n\n    Use minutes parameter to control the lookback window (default: 5, max: 60).\n    Useful for detecting stress patterns during a conversation. Not a medical device.\n    ",
  "inputSchema": {
    "type": "object",
    "title": "get_session_historyArguments",
    "required": [
      "session_id"
    ],
    "properties": {
      "minutes": {
        "type": "integer",
        "title": "Minutes",
        "default": 5,
        "maximum": 60,
        "minimum": 1
      },
      "session_id": {
        "type": "string",
        "title": "Session Id"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.nefesh/human-state"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ai.nefesh/human-state"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~2,210 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 100.00% uptime over 30 days.

Largest tool definitions

• ingest ~1,145 tokens
• get_trigger_memory ~200 tokens
• get_human_state ~198 tokens
• check_api_key_status ~190 tokens
• get_session_history ~187 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.nefesh%2Fhuman-state.svg)](https://glimind.com/server/mcp-registry%2Fai.nefesh%2Fhuman-state?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fai.nefesh%2Fhuman-state?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.nefesh%2Fhuman-state.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.nefesh%2Fhuman-state.svg
   :target: https://glimind.com/server/mcp-registry%2Fai.nefesh%2Fhuman-state?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:7044e6aa1bab4e0d…, first seen 2026-10-17, included at leaf 1856 of 62,069. Version history · verify what your client received.

Tools (7)

• check_api_key_status
• delete_subject
• get_human_state
• get_session_history
• get_trigger_memory
• ingest
• request_api_key

Compare: most reliable security servers · most reliable database servers · most reliable other servers · most reliable data servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Nefesh Human State MCP server down right now?

As of 2026-10-24 23:15 UTC, the Nefesh Human State MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 4 minutes.

How many tools does Nefesh Human State MCP server provide?

Nefesh Human State MCP server advertises 7 tools, including check_api_key_status, delete_subject, get_human_state, get_session_history, get_trigger_memory.

How do I install Nefesh Human State MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.nefesh.ai/mcp

Is the Nefesh Human State MCP server safe to connect to an AI agent?

Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Nefesh Human State MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.