Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.MohibShaikh/hwcontract

PYPI · HWCONTRACT · SCANNED SEP 21

Judge hardware timing/serial against a contract: pass/marginal/fail (WS2812, DShot, logs)

Available components

+15 this week 79 Trust /100
Trust breakdown (7 categories)

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 459 tokens (~65/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the io.github.MohibShaikh/hwcontract MCP server?

io.github.MohibShaikh/hwcontract runs locally as a PyPI package, launched with uvx hwcontract. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · hwcontract

# add to Claude Code
claude mcp add mohibshaikh-hwcontract -- uvx hwcontract
// .cursor/mcp.json
{
  "mcpServers": {
    "mohibshaikh-hwcontract": {
      "command": "uvx",
      "args": [
        "hwcontract"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mohibshaikh-hwcontract": {
      "command": "uvx",
      "args": [
        "hwcontract"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add mohibshaikh-hwcontract -- uvx hwcontract
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mohibshaikh-hwcontract": {
      "type": "local",
      "command": [
        "uvx",
        "hwcontract"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mohibshaikh-hwcontract --command uvx --arg hwcontract
# ~/.hermes/config.yaml
mcp_servers:
  mohibshaikh-hwcontract:
    command: "uvx"
    args: ["hwcontract"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mohibshaikh-hwcontract": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "hwcontract"
      ]
    }
  }
}
# add to Vellum
assistant mcp add mohibshaikh-hwcontract -t stdio -c uvx -a hwcontract
// mcp.json
{
  "mcpServers": {
    "mohibshaikh-hwcontract": {
      "command": "uvx",
      "args": [
        "hwcontract"
      ]
    }
  }
}
Changelog

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.

  • 21 Sept 26 0
    • Package version: 0.1.1 → 0.4.2 functional
  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 −2
    • Stability: pass → 0.87 functional
  • 18 Sept 26 0
    • Stability: 0.97 → pass security
  • 17 Sept 26 0
    • Stability: pass → 0.97 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +16
    • Malware scan: unverified → pass security
  • 14 Sept 26 −15
    • Malware scan: pass → unverified security
Diagnostics

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 21 Sept 2026 · Analysed pypi/hwcontract@0.4.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 1 package
Packages resolved 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~418 tokens

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 →

Tool Tokens
capture_ws2812 ~64

Capture the WS2812 data line via sigrok and return measured pulse-width observations (T0H/T1H/...).

NameTypeReqDescription
channelstring
driverstring
sampleratenumber
samplesnumber

No output schema declared.

No examples provided.

check_dshot ~64

Capture a live DShot600 ESC signal AND judge it against a contract in one call.

NameTypeReqDescription
channelstring
contract_pathstringyes
driverstring
sampleratenumber
samplesnumber

No output schema declared.

No examples provided.

check_serial ~58

Read a serial port for N seconds AND judge its log against a contract's expect/forbid patterns.

NameTypeReqDescription
baudnumber
contract_pathstringyes
portstringyes
secondsnumber

No output schema declared.

No examples provided.

check_ws2812 ~72

Capture a live WS2812 signal AND judge it against a contract in one call. The one-shot an agent reaches for.

NameTypeReqDescription
channelstring
contract_pathstringyes
driverstring
sampleratenumber
samplesnumber

No output schema declared.

No examples provided.

judge_contract ~49

Judge observations against a contract -> pass/marginal/fail. No hardware; use for replay or when an adapter already captured.

NameTypeReqDescription
contract_pathstringyes
observationsarrayyes

No output schema declared.

No examples provided.

judge_events ~63

Judge decoded hardware events against an events contract's temporal assertions (when/require/within, forbid/while/before). Events: [{source, type, start_ns, end_ns, fields}].

NameTypeReqDescription
contract_pathstringyes
eventsarrayyes

No output schema declared.

No examples provided.

judge_serial ~48

Judge a captured serial log against expect/forbid patterns. No hardware; use for replay or logs another tool already captured.

NameTypeReqDescription
contract_pathstringyes
logstringyes

No output schema declared.

No examples provided.

Common questions

What is the io.github.MohibShaikh/hwcontract MCP server?

io.github.MohibShaikh/hwcontract is an MCP server listed in the public MCP registry as io.github.MohibShaikh/hwcontract. Judge hardware timing/serial against a contract: pass/marginal/fail (WS2812, DShot, logs). This page covers its PyPI package (hwcontract).

Is the io.github.MohibShaikh/hwcontract MCP server safe to use?

io.github.MohibShaikh/hwcontract scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. 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.MohibShaikh/hwcontract MCP server expose?

io.github.MohibShaikh/hwcontract exposes 7 tools: judge_contract, capture_ws2812, check_ws2812, check_dshot, judge_serial, and 2 more. Their descriptions and schemas cost roughly 418 tokens of context every time the server is loaded.

Is the io.github.MohibShaikh/hwcontract MCP server still maintained?

io.github.MohibShaikh/hwcontract is still listed as active in the MCP registry. We last reached this channel on 21 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.MohibShaikh/hwcontract MCP server under?

io.github.MohibShaikh/hwcontract declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.