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

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

Available components

0 this week 75 Trust /100

Last scanned (9 hours ago)

Scores higher than 68% of PyPI servers

Category Testing and QA

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to MohibShaikh/hwcontract). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 31 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 494 tokens (~61/item across 8 items; 8 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 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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 Nov 26 0
    • Package version: 0.1.1 → 0.6.1 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 0
    • Stability: pass → 0.97 functional
  • 10 Nov 26 −10
    • Malware scan: pass → unverified ▼ security
    • Source repository: unverified → pass ▲ security
  • 9 Nov 26 −5
    • Provenance: pass → unverified ▼ security
  • 6 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 5 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
  • 4 Nov 26 +16
    • Malware scan: unverified → pass ▲ 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 Nov 2026 · Analysed pypi/hwcontract@0.6.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 pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo MohibShaikh/hwcontract
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/MohibShaikh/hwcontract/.github/workflows/workflow.yml@refs/tags/v0.6.1
Rekor log index 3354288361
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:e91ec41b12222e069b207f33456375f10fd64f6628a6bf24e43c42105393fa60

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool 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 · 8 exposed · ~450 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 ~52

Judge observations against a timing contract -> PASS/MARGINAL/FAIL/MISSING. 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.

list_contracts ~29

List bundled contract templates, names, kinds, installed paths, and capture adapter requirements. No hardware.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

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

io.github.MohibShaikh/hwcontract exposes 8 tools: list_contracts, judge_contract, capture_ws2812, check_ws2812, check_dshot, and 3 more. Their descriptions and schemas cost roughly 450 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 November 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.

What did VerifyMCP test on the io.github.MohibShaikh/hwcontract MCP server?

VerifyMCP ran 15 checks on io.github.MohibShaikh/hwcontract, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.MohibShaikh/hwcontract: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.