hwcontract
Related Servers
Alternatives to hwcontract
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for Agentic Hardware-in-the-Loop testing, enabling AI agents to probe, flash, reset, and validate embedded firmware on real hardware via bounded MCP tools.1,560 PyPI17Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server that lets an AI agent operate a bench oscilloscope over LAN/SCPI to observe physical pin behavior, bridging RTL simulation and hardware testing.3MIT

multivon-mcpofficial
AlicenseAqualityAmaintenanceMCP server that gives AI coding agents direct access to evaluation tools.23Apache 2.0- AlicenseAqualityDmaintenanceAn MCP server that enables coding agents to autonomously test, evaluate, and tune other MCP servers by acting as a proxy and providing linting, trace recording, evaluation, comparison, and reporting tools.7MIT
- AlicenseBqualityBmaintenanceAn MCP server that enforces fail-closed deterministic checks, independent refute-first review, and tamper-evident hash-chained receipts for AI agent outputs before claiming completion.43MIT
- FlicenseNot gradedqualityBmaintenanceMCP server that enables AI agents to programmatically run tests, query results, and receive intelligent recommendations about test execution strategy.-
TDQS
Scored across 6 tools
Tools are mostly distinct: check_* does live capture+judge, judge_* does offline judging, and capture_ws2812 is capture-only. However, judge_contract and judge_serial could be confused for serial logs, and capture_ws2812 vs check_ws2812 requires careful reading.
Naming mixes three verb prefixes (judge_, check_, capture_) and inconsistently references protocols (ws2812, dshot, serial) vs the generic 'contract'. The pattern is readable but not fully consistent.
Six tools are well-scoped for hardware contract testing: one generic judge, one capture, and four protocol-specific live/offline checks. This is within the ideal 3-15 range and each tool serves a distinct purpose.
The core workflow of capture and judge is covered for WS2812, serial, and DShot (via live check). Missing a DShot capture-only tool and a dedicated judge_dshot, but judge_contract fills the gap, so only minor dead ends exist.