
Humane Proxy
io.github.Vishisht16Published by GitHub account Vishisht16v0.6.0Updated Oct 24, 2026
AI safety middleware — detects self-harm and criminal intent in LLM prompts.
Overview
A local MCP server that lets an assistant screen messages for self-harm or criminal intent and review session risk and recent escalations.
- What you can do
- Check a message for safety, returning a category, score and triggers for self-harm or criminal intent detection, with optional session tracking and risk trajectory across a conversation. Look up the accumulated risk level for a given session. List recent escalations that were flagged, so an operator can review them. Detection runs as a cascade of keyword heuristics, optional semantic embeddings and an optional reasoning LLM stage.
- When to use it
- Useful when an assistant or agent handles user messages that may involve self-harm ideation or criminal intent and you want a pre-check with care responses and operator alerts. Best suited to deployments that already run the Humane Proxy pipeline and want an agent to query it.
- Requirements
- Runs as a local process, installed from PyPI with the mcp extra (for example via uvx). Optional API keys for the reasoning stage: GROQ_API_KEY for LlamaGuard or OPENAI_API_KEY for OpenAI-based reasoning. The embedding stage needs an extra install; the base install uses SQLite storage.
Installation
In SourceWeft
- Open Humane Proxy in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Lightweight, plug-and-play AI safety middleware that protects humans.
HumaneProxy sits between your users and any LLM. When someone expresses self-harm ideation or criminal intent, it intercepts the message, alerts you through your preferred channels, and responds with care — before the LLM ever sees it.
[PyPI] [Python] [Downloads] [License] [Tests] [Humane-Proxy MCP server] [MCP Marketplace]
What it does
- Self-harm detected → Blocked with international crisis resources. Operator notified.
- Criminal intent detected → Blocked or flagged. Operator notified.
- Safe → Forwarded to your LLM transparently.
Jailbreaks and prompt injections are deliberately not the concern of this tool — we focus exclusively on protecting human lives.
Quick Start
As a Python library
As an MCP server (Claude Desktop, Cursor, any agent)
This exposes 3 tools to your AI agent: check_message_safety, get_session_risk, and list_recent_escalations.
How it works
Every message runs through up to 3 cascading stages — each catches what the previous one can't, and clear-cut cases exit early:
Stage 2 catches what keywords miss ("Nobody would notice if I disappeared"); Stage 1's reducers keep "how do I kill a process in Linux" from ever being flagged. On top of the per-message pipeline, a per-session risk trajectory with exponential time-decay detects escalation across a conversation and boosts scores on sudden spikes.
Full details: Pipeline documentation.
Benchmarks
Evaluated on two public datasets — SimpleSafetyTests (100 clearly unsafe prompts) for recall, and XSTest (250 safe-but-alarming prompts like "how do I kill a Python process?") for false positives:
Turning on the free reasoning stage lifts recall to 92% at no cost to the false-positive rate. Fully reproducible with the shipped tooling — methodology, machine specs, and per-stage latency in BENCHMARKS.md.
When something is flagged
- Self-harm → the user receives an empathetic response with crisis helplines for 10+ countries (US 988, India iCall/Vandrevala, UK Samaritans, and more) — or your LLM answers with an injected care-context system prompt; your choice.
- Operators are alerted via Slack, Discord, PagerDuty, Teams, or SMTP email — rate-limited per session so a crisis doesn't become alert spam, while every event is still persisted to the audit log.
- Privacy by default — raw message text is never stored, only SHA-256 hashes;
DELETE /admin/sessions/{id}implements the right to erasure end-to-end.
Available On
Installation Extras
Documentation
License
Apache 2.0. See LICENSE.
Copyright 2026 Vishisht Mishra (@Vishisht16). Any attribution is appreciated.
See NOTICE for full attribution information.
Built for a safer world.
Source: README.md at commit f83368d
Tools
0Version history
1- v0.6.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts