io.github.aklodhi98/human-standards
NPM · @HUMANSTANDARDS/MCP-SERVER
Read-only Human Standards guidance for accessible, usable interface design.
Available components
Last scanned (14 hours ago)
Scores higher than 96% of npm servers
Category Design and Media
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
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to aklodhi98/humanstandards). View diagnostics → Pass
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 81 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 591 tokens (~118/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −1
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 20 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 19 Oct 26 +1
- Stability: 0.97 → pass security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 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.
- 13 Oct 26 −3
- Stability: pass → 0.80 functional
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 5 Nov 2026 · Analysed npm/@humanstandards/mcp-server@0.3.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | aklodhi98/humanstandards |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/aklodhi98/humanstandards/.github/workflows/publish-mcp.yml@refs/tags/mcp-v0.3.1 |
| Rekor log index | 2475636076 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:fcf0841b74c248bfe1eff7a428f810c7a56df0796dcb6b8611e085c86c422ca42624abbc9219e12b6d0cd4a57ae0ea49ff586d783d13d03ee25483478 |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
get_all_heuristics List usability heuristics ~40
Get a summary of all 10 Nielsen usability heuristics. Useful for understanding the full framework or identifying which heuristics might apply to a situation.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| heuristics | array | yes | – |
| source | string | yes | – |
No examples provided.
get_heuristic Get usability heuristic ~136
Get detailed information about a specific Nielsen usability heuristic (H1-H10). Returns the principle, description, key questions to ask, good examples, common violations, and related documentation.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Heuristic ID: H1 (Visibility of system status), H2 (Match between system and real world), H3 (User control and freedom), H4 (Consistency and standards), H5 (Error prevention), H6 (Recognition rather… |
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| examples | array | yes | – |
| id | string | yes | – |
| name | string | yes | – |
| principle | string | yes | – |
| questions | array | yes | – |
| related_docs | array | yes | – |
| source | string | yes | – |
| violations | array | yes | – |
No examples provided.
get_spatial_rhythm Get spatial rhythm guidance ~132
Get relationship-first spacing guidance for a whole interface or a form, settings section, card collection, editorial flow, or dashboard. Returns ordered spatial relationships, rhythm rules, responsive and density guidance, manual review questions, evidence boundaries, and token-resolution instructions. It deliberately does not prescribe a universal pixel unit. Call before implementation and during rendered review.
| Name | Type | Req | Description |
|---|---|---|---|
| density | string | – | Intended interface density. Density changes project-token resolution, not relationship order. |
| pattern | string | – | Optional composition pattern to return. Use all for the complete contract. |
| viewport | string | – | Viewport context for responsive rhythm guidance. |
| Name | Type | Req | Description |
|---|---|---|---|
| available_patterns | array | yes | – |
| evidence_boundary | object | yes | – |
| patterns | array | yes | – |
| principle | string | yes | – |
| principles | array | yes | – |
| references | array | yes | – |
| relationship_order | array | yes | – |
| selected_context | object | yes | – |
| source | string | yes | – |
| standard_id | string | yes | – |
| title | string | yes | – |
| token_resolution | object | yes | – |
No examples provided.
get_standard Read a Human Standard ~99
Read the actual Human Standards guidance at a path returned by search_standards. For long documents, the response lists available sections; pass section to retrieve one focused section without truncation.
| Name | Type | Req | Description |
|---|---|---|---|
| max_chars | integer | – | Maximum content characters to return. |
| path | string | yes | Document path returned by search_standards, such as /interaction-patterns/forms/. |
| section | string | – | Optional H2 or H3 section title from available_sections. |
| Name | Type | Req | Description |
|---|---|---|---|
| available_sections | array | yes | – |
| content | string | yes | – |
| description | string | yes | – |
| key_points | array | yes | – |
| path | string | yes | – |
| references | array | yes | – |
| requested_section | string|null | yes | – |
| title | string | yes | – |
| truncated | boolean | yes | – |
No examples provided.
search_standards Search Human Standards ~93
Search the full Human Standards library. Returns ranked documents, matched terms, and excerpts from the actual guidance. Use get_standard with a returned path to read the document or a named section.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of ranked results to return (1-10). |
| query | string | yes | Topic or task query (e.g., "forms error recovery", "cognitive load", "touch targets") |
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| result_count | integer | yes | – |
| results | array | yes | – |
No examples provided.
How do I install the io.github.aklodhi98/human-standards MCP server?
io.github.aklodhi98/human-standards runs locally as an npm package, launched with npx -y @humanstandards/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 · @humanstandards/mcp-server
claude mcp add aklodhi98-human-standards -- npx -y @humanstandards/mcp-server
What is the io.github.aklodhi98/human-standards MCP server?
io.github.aklodhi98/human-standards is an MCP server listed in the public MCP registry as io.github.aklodhi98/human-standards. Read-only Human Standards guidance for accessible, usable interface design. This page covers its npm package (@humanstandards/mcp-server).
Is the io.github.aklodhi98/human-standards MCP server safe to use?
io.github.aklodhi98/human-standards scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.aklodhi98/human-standards MCP server expose?
io.github.aklodhi98/human-standards exposes 5 tools: get_heuristic, get_all_heuristics, search_standards, get_standard, get_spatial_rhythm. Their descriptions and schemas cost roughly 500 tokens of context every time the server is loaded.
Is the io.github.aklodhi98/human-standards MCP server still maintained?
io.github.aklodhi98/human-standards is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.