io.github.humanity4ai/project-human
NPM · @HUMANITY4AI/MCP-SERVERS · SCANNED SEP 24
9 humanity skills for AI agents — crisis detection, WCAG 2.2, empathy, cultural sensitivity
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 60 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1441 tokens (~160/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.humanity4ai/project-human MCP server?
io.github.humanity4ai/project-human runs locally as an npm package, launched with npx -y @humanity4ai/mcp-servers. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @humanity4ai/mcp-servers
claude mcp add humanity4ai-project-human -- npx -y @humanity4ai/mcp-servers
{
"mcpServers": {
"humanity4ai-project-human": {
"command": "npx",
"args": [
"-y",
"@humanity4ai/mcp-servers"
]
}
}
} {
"servers": {
"humanity4ai-project-human": {
"command": "npx",
"args": [
"-y",
"@humanity4ai/mcp-servers"
]
}
}
} codex mcp add humanity4ai-project-human -- npx -y @humanity4ai/mcp-servers
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"humanity4ai-project-human": {
"type": "local",
"command": [
"npx",
"-y",
"@humanity4ai/mcp-servers"
],
"enabled": true
}
}
} openclaw mcp add humanity4ai-project-human --command npx --arg -y --arg @humanity4ai/mcp-servers
mcp_servers:
humanity4ai-project-human:
command: "npx"
args: ["-y", "@humanity4ai/mcp-servers"] {
"McpServers": {
"humanity4ai-project-human": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@humanity4ai/mcp-servers"
]
}
}
} assistant mcp add humanity4ai-project-human -t stdio -c npx -a -y @humanity4ai/mcp-servers
{
"mcpServers": {
"humanity4ai-project-human": {
"command": "npx",
"args": [
"-y",
"@humanity4ai/mcp-servers"
]
}
}
} 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.
- 24 Sept 26 +13
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.83 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.
- 20 Sept 26 +1
- Security disclosure: unverified → pass ▲ functional
- 19 Sept 26 0
- Security disclosure: pass → unverified ▼ functional
- 17 Sept 26 −2
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 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.
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 24 Sept 2026 · Analysed npm/@humanity4ai/mcp-servers@1.0.6
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 →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
accessibility_audit ~142
Audit web pages for WCAG 2.2 compliance or set session WCAG level. Crawl mode: provide pages with URL+HTML for per-page scoring and ranking across all 86 success criteria. Session mode: returns the complete WCAG checklist for the requested level that the agent must enforce.
| Name | Type | Req | Description |
|---|---|---|---|
| level | string | – | WCAG conformance level |
| locale | string | – | BCP 47 locale code |
| mode | string | yes | crawl: score pages against all 86 WCAG 2.2 criteria. session: return WCAG checklist for this session. |
| pages | array | – | Array of crawled pages (required for crawl mode) |
No output schema declared.
No examples provided.
age_inclusive_design_check ~98
Audit a user flow or interface for age-inclusive design — covering children, adults, and older users. Returns recommendations to remove age-related barriers. Safety boundary: inclusive design guidance only.
| Name | Type | Req | Description |
|---|---|---|---|
| age_groups | array | – | Optional list of age groups to focus on (e.g. ['children', 'elderly', 'teenagers']) |
| flow_description | string | yes | Description of the user flow, interface, or product experience to audit |
No output schema declared.
No examples provided.
cognitive_accessibility_audit ~74
Audit content for cognitive accessibility — plain language, reading level, structure, and clarity. Returns actionable recommendations to reduce cognitive load. Safety boundary: design guidance only.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The text or UI content to audit |
| target_context | string | – | Optional context about the target audience or use case |
No output schema declared.
No examples provided.
cultural_context_check ~82
Check a message for cultural sensitivity issues for a given audience or region. Returns flags, concerns, and suggested alternatives with uncertainty disclosure. Safety boundary: context-sensitive recommendations with uncertainty disclosure.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | yes | Target audience description |
| message | string | yes | The message or content to check |
| region | string | – | Optional geographic region for more specific context |
No output schema declared.
No examples provided.
deescalation_plan ~73
Generate a structured de-escalation plan for a conflict or tense situation. Returns step-by-step guidance calibrated to the intensity of the conflict. Safety boundary: no coercive tactics.
| Name | Type | Req | Description |
|---|---|---|---|
| intensity | string | – | Intensity of the conflict |
| situation | string | yes | Description of the conflict or tense situation |
No output schema declared.
No examples provided.
empathetic_reframe ~77
Reframe a message with genuine empathy — acknowledging emotions, validating experience, and offering presence. Detects and replaces hollow empathy phrases with authentic alternatives. Safety boundary: no manipulation or deceptive empathy.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The message to reframe with empathy |
| tone | string | – | Desired tone of the empathetic reframe |
No output schema declared.
No examples provided.
neurodiversity_design_check ~91
Audit a UI description for neurodiversity-aware design — covering ADHD, autism, dyslexia, and sensory sensitivities. Returns targeted recommendations for inclusive design. Safety boundary: inclusive design guidance only.
| Name | Type | Req | Description |
|---|---|---|---|
| focus | array | – | Optional list of specific neurodiversity conditions to focus on |
| ui_description | string | yes | Description of the UI, interface, or interaction flow to audit |
No output schema declared.
No examples provided.
rewrite_depression_sensitive_content ~108
Audit or rewrite text to be sensitive to depression and mental health. Removes harmful language patterns and replaces them with supportive, non-stigmatising alternatives. Safety boundary: non-clinical UX/content guidance only.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Optional domain context (e.g. 'healthcare', 'social media') |
| mode | string | – | 'audit' returns issues found; 'rewrite' returns improved text |
| text | string | yes | The text content to audit or rewrite |
No output schema declared.
No examples provided.
supportive_reply ~148
Generate a supportive, non-clinical reply to a message from someone in distress. Supports general emotional support and grief-specific modes (presence, practical, reflection). Includes escalation guidance calibrated to the assessed risk level. Safety boundary: non-clinical support only; must escalate when risk is elevated.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | BCP 47 locale code for the response language |
| message | string | yes | The message from the person in distress |
| risk_level | string | yes | Assessed risk level: 'low' for general distress, 'medium' for concerning signals, 'high' for crisis |
| support_mode | string | – | Support mode: 'general' for default emotional support |
No output schema declared.
No examples provided.
What is the io.github.humanity4ai/project-human MCP server?
io.github.humanity4ai/project-human is an MCP server listed in the public MCP registry as io.github.humanity4ai/project-human. 9 humanity skills for AI agents, crisis detection, WCAG 2.2, empathy, cultural sensitivity. This page covers its npm package (@humanity4ai/mcp-servers).
Is the io.github.humanity4ai/project-human MCP server safe to use?
io.github.humanity4ai/project-human scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 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.humanity4ai/project-human MCP server expose?
io.github.humanity4ai/project-human exposes 9 tools: accessibility_audit, rewrite_depression_sensitive_content, supportive_reply, cognitive_accessibility_audit, cultural_context_check, and 4 more. Their descriptions and schemas cost roughly 893 tokens of context every time the server is loaded.
Is the io.github.humanity4ai/project-human MCP server still maintained?
io.github.humanity4ai/project-human is still listed as active in the MCP registry. We last reached this channel on 24 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.humanity4ai/project-human MCP server under?
io.github.humanity4ai/project-human declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.