# io.github.sriramnatrajhen/humsana-mcp (npm · @humsana/mcp-server)

Detect developer stress, focus, fatigue from typing. Block dangerous commands when tired.

- Trust score: 59/100 (low)
- Change this week: +13
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- npm · `@humsana/mcp-server`: 59/100 (this document), [markdown](https://verifymcp.io/servers/sriramnatrajhen-humsana-mcp/humsana-mcp-server.md), [page](https://verifymcp.io/servers/sriramnatrajhen-humsana-mcp/humsana-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@humsana/mcp-server`
- Version: `1.1.3`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Supply Chain Security**: 70/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.5.0, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (50 of 51), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 213 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 369 tokens (~92/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add sriramnatrajhen-humsana-mcp -- npx -y @humsana/mcp-server
```

### Codex

```bash
codex mcp add sriramnatrajhen-humsana-mcp -- npx -y @humsana/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sriramnatrajhen-humsana-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@humsana/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sriramnatrajhen-humsana-mcp --command npx --arg -y --arg @humsana/mcp-server
```

### Hermes

```yaml
mcp_servers:
  sriramnatrajhen-humsana-mcp:
    command: "npx"
    args: ["-y", "@humsana/mcp-server"]
```

### Other

```json
{
  "mcpServers": {
    "sriramnatrajhen-humsana-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@humsana/mcp-server"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 58, +36)

- [security regression] CVE-2025-66414 affects this package: high
- [security regression] Provenance: unverified → fail
- [security regression] Known CVEs: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] License: unverified → pass
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Schema quality: unverified → good
- [functional improvement] Dependency health: unverified → partial
- [functional] First check of Schema quality: unverified
- [functional] Licence: MIT

### 2026-07-31 (score 22, −24)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (4)

### `humsana_get_user_state` (~45 tokens)

Get the user's current behavioral state including stress level, focus level, fatigue, and response style recommendations. Use this at the start of conversations to adapt your communication style.

### `humsana_check_dangerous_command` (~74 tokens)

Check if a command is dangerous and whether the user is too fatigued to safely run it. Use this before helping with potentially destructive operations like rm -rf, DROP TABLE, git push --force, kubectl delete, terraform destroy, etc.

Input parameters:

- `command` (string, required): The command to check

### `humsana_safe_execute_command` (~112 tokens)

Execute a shell command with Humsana Cognitive Interlock protection. This is THE tool for running commands - it blocks dangerous commands when the user is fatigued, requires override confirmation for high-risk operations, and logs all safety events. Use this instead of any other shell/bash tool.

Input parameters:

- `command` (string, required): The shell command to execute
- `override_reason` (string): If the user said 'OVERRIDE SAFETY PROTOCOL: [reason]', pass their reason here to bypass the interlock

### `humsana_safe_write_file` (~138 tokens)

Write content to a file with Humsana Cognitive Interlock protection. This tool prevents AI from making large destructive rewrites when the user is fatigued. If AI tries to delete/rewrite >30 lines while user is tired, it blocks the write and saves to a review folder. Use this for ALL file write operations.

Input parameters:

- `content` (string, required): The content to write to the file
- `filepath` (string, required): The absolute path to the file to write
- `override_reason` (string): If the user said 'OVERRIDE SAFETY PROTOCOL: [reason]', pass their reason here to bypass the interlock

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/sriramnatrajhen-humsana-mcp/humsana-mcp-server#diagnostics

## Score history

- 2026-08-04: 59
- 2026-08-03: 59
- 2026-08-02: 58
- 2026-08-01: 22
- 2026-07-31: 22
- 2026-07-30: 46
- 2026-07-28: 46
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/@humsana/mcp-server
- Socket report: https://socket.dev/npm/package/@humsana/mcp-server
- Repository: https://github.com/sriramnatrajhen/humsana-mcp
- Changelog RSS feed: https://verifymcp.io/servers/sriramnatrajhen-humsana-mcp/humsana-mcp-server/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/sriramnatrajhen-humsana-mcp/humsana-mcp-server/changelog.json
- HTML version of this page: https://verifymcp.io/servers/sriramnatrajhen-humsana-mcp/humsana-mcp-server