Humsana MCP server
io.github.sriramnatrajhen/humsana-mcp·v1.1.3Detect developer stress, focus, fatigue from typing. Block dangerous commands when tired.
0 stars44 downloads/wk
Reviews
Write oneNobody has reviewed Humsana yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Humsana tools (4, 2 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
humsana_check_dangerous_commandCheck 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.
humsana_get_user_stateGet 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_safe_execute_commandwrite actionExecute 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.
humsana_safe_write_filewrite actionWrite 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.
Public scan report
scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it
- Code scan3 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 62 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Humsana compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- Tools
- 4
- the typical server has 7
- Tools that change things
- 50%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 44
- more than 36% of 12,191 servers with a package
What its tools let an agent do: 2 read · 2 change
Install Humsana in Claude Code, Cursor or VS Code
Runs npx -y @humsana/mcp-server on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add humsana-mcp -- npx -y @humsana/mcp-server
What the publisher says
From the Humsana repository's README, as published. We do not edit it. Read it on GitHub
@humsana/mcp-server
Cognitive Security for AI-assisted development.
🛡️ "The breathalyzer for your terminal."
Humsana prevents you from running dangerous commands or accepting large AI code rewrites when you're fatigued. Think of it as an industrial safety interlock, but for your brain.
What It Does
Command Protection (safeexecutecommand)
AI Rewrite Protection (safewritefile)
Quick Start
1. Install the Daemon
pip install humsana-daemon
humsana startKeep this running in a terminal tab.
2. Install the MCP Server
npm install -g @humsana/mcp-server3. Configure Claude Desktop
Create/edit ~/Library/Application Support/Claude/claudedesktopconfig.json:
{
"mcpServers": {
"humsana": {
"command": "node",
"args": ["/path/to/humsana-mcp/dist/index.js"]
}
}
}4. Restart Claude Desktop
Quit (Cmd+Q) and reopen.
5. Test It
Ask Claude: "What's my current state?"
Execution Modes
Humsana starts in dry-run mode for safety. Commands are simulated, not executed.
Dry-Run Mode (Default)
✅ [DRY RUN] Safety check passed.
Command: `kubectl delete pods`
This command WOULD have been executed.
(Execution skipped: dry_run mode active)Switching to Live Mode
When you trust the system, enable real execution:
Step 1: Create/edit ~/.humsana/config.yaml:
# Change this from 'dry_run' to 'live'
execution_mode: live
# Optional: adjust thresholds
fatigue_threshold: 70
write_warn_threshold: 30
write_block_threshold: 50Step 2: Restart Claude Desktop (Cmd+Q, reopen)
Step 3: Test with a safe command first:
Run `echo "live mode working"`You should see actual output instead of "WOULD have been executed."
Configuration Reference
Create ~/.humsana/config.yaml:
# === EXECUTION MODE ===
# 'dry_run' (default) - Simulates commands, nothing executed
# 'live' - Actually executes commands and writes files
execution_mode: dry_run
# === FATIGUE THRESHOLDS ===
# Fatigue level (0-100) above which dangerous commands are blocked
fatigue_threshold: 70
# Lines removed to trigger warning (when fatigued)
write_warn_threshold: 30
# Lines removed to trigger hard block (when fatigued)
write_block_threshold: 50
# === CUSTOM PATTERNS ===
# Additional dangerous commands to block
deny_patterns:
- "aws ec2 terminate"
- "docker rm -f"
# === NOTIFICATIONS ===
# Webhook for Slack/PagerDuty (fires on safety overrides)
webhook_url: https://hooks.slack.com/services/XXX/YYY/ZZZOverride Protocol
When blocked, say:
OVERRIDE SAFETY PROTOCOL: [reason]Example:
OVERRIDE SAFETY PROTOCOL: P0 production outage, need to restart podsThis is logged to ~/.humsana/audit.json and sent to your webhook.
Tools Available
Files & Folders
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Humsana: common questions
- Is Humsana MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Humsana safety report
- How do I install Humsana?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Humsana need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Humsana maintained?
- The last commit was 96 days ago (2026-07-31). The latest release is v1.1.3.
- How does Humsana compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 50% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.