io.github.sriramnatrajhen/humsana-mcp
NPM · @HUMSANA/MCP-SERVER · SCANNED SEP 26
Detect developer stress, focus, fatigue from typing. Block dangerous commands when tired.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security79
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.5.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 51 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency44
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 266 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 369 tokens (~92/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "humsana_safe_execute_command" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.sriramnatrajhen/humsana-mcp server?
io.github.sriramnatrajhen/humsana-mcp runs locally as an npm package, launched with npx -y @humsana/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @humsana/mcp-server
claude mcp add sriramnatrajhen-humsana-mcp -- npx -y @humsana/mcp-server
{
"mcpServers": {
"sriramnatrajhen-humsana-mcp": {
"command": "npx",
"args": [
"-y",
"@humsana/mcp-server"
]
}
}
} {
"servers": {
"sriramnatrajhen-humsana-mcp": {
"command": "npx",
"args": [
"-y",
"@humsana/mcp-server"
]
}
}
} codex mcp add sriramnatrajhen-humsana-mcp -- npx -y @humsana/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sriramnatrajhen-humsana-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@humsana/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add sriramnatrajhen-humsana-mcp --command npx --arg -y --arg @humsana/mcp-server
mcp_servers:
sriramnatrajhen-humsana-mcp:
command: "npx"
args: ["-y", "@humsana/mcp-server"] {
"McpServers": {
"sriramnatrajhen-humsana-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@humsana/mcp-server"
]
}
}
} assistant mcp add sriramnatrajhen-humsana-mcp -t stdio -c npx -a -y @humsana/mcp-server
{
"mcpServers": {
"sriramnatrajhen-humsana-mcp": {
"command": "npx",
"args": [
"-y",
"@humsana/mcp-server"
]
}
}
} 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.
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 24 Sept 26 −2
- Stability: pass → 0.80 functional
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
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 26 Sept 2026 · Analysed npm/@humsana/mcp-server@1.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-w48q-cv73-mx4w | CVE-2025-66414 | high | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 51 packages
| Packages resolved | 51 |
|---|---|
| Deprecated | 1 |
| Stale | 29 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
humsana_check_dangerous_command ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | The command to check |
No output schema declared.
No examples provided.
humsana_get_user_state ~45
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
humsana_safe_execute_command ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | The shell command to execute |
| override_reason | string | – | If the user said 'OVERRIDE SAFETY PROTOCOL: [reason]', pass their reason here to bypass the interlock |
No output schema declared.
No examples provided.
humsana_safe_write_file ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The content to write to the file |
| filepath | string | yes | 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 |
No output schema declared.
No examples provided.
What is the io.github.sriramnatrajhen/humsana-mcp server?
io.github.sriramnatrajhen/humsana-mcp is listed in the public MCP registry as io.github.sriramnatrajhen/humsana-mcp. Detect developer stress, focus, fatigue from typing. Block dangerous commands when tired. This page covers its npm package (@humsana/mcp-server).
Is the io.github.sriramnatrajhen/humsana-mcp server safe to use?
io.github.sriramnatrajhen/humsana-mcp scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 26 September 2026. It declares no install or post-install scripts. 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 io.github.sriramnatrajhen/humsana-mcp server expose?
io.github.sriramnatrajhen/humsana-mcp exposes 4 tools: humsana_get_user_state, humsana_check_dangerous_command, humsana_safe_execute_command, humsana_safe_write_file. Their descriptions and schemas cost roughly 369 tokens of context every time the server is loaded.
Is the io.github.sriramnatrajhen/humsana-mcp server still maintained?
io.github.sriramnatrajhen/humsana-mcp is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.sriramnatrajhen/humsana-mcp server under?
io.github.sriramnatrajhen/humsana-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.