Hci Quality Mcp

io.github.priyankarkPublished by GitHub account priyankarkv0.1.0Updated Oct 24, 2026

Interface observations and explicit GOMS/KLM, Fitts, Hick–Hyman and cognitive walkthrough models.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Local MCP server that gives an assistant explicit HCI analysis models: GOMS/KLM, Fitts, Hick–Hyman and cognitive walkthrough, plus interface observations.

What you can do
  • Record and work with interface observations.
  • Apply GOMS and KLM task-time models to interaction sequences.
  • Compute Fitts's law pointing-time estimates.
  • Apply Hick–Hyman choice-reaction estimates.
  • Run cognitive walkthrough analysis of a task flow.
When to use it
Useful when evaluating a user interface or interaction design and you want structured, model-based estimates rather than informal critique — for example comparing input methods, estimating task completion time, or walking through a flow for usability problems.
Requirements
Runs as a local stdio process installed from the npm package hci-quality-mcp, so a Node.js runtime is needed. No authentication, environment variables or headers are declared.
Before you install
The manifest lists no tools, so the exact operations and any data they write are not documented here; review the package before installing. Outputs are model-based estimates and should not be treated as validated usability findings.

Installation

In SourceWeft

  1. Open Hci Quality Mcp in the dashboard and add it to a workspace.
  2. 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

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.