Hardware-in-the-loop verification gate for coding agents on embedded firmware: rebuild, flash over ST-Link (STM32CubeProgrammer), then require the board to prove which build is running — UART boot ban
Power your agent
Install from the publisher. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
No packaged release in the registry yet. Follow the repository README.
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
README is not crawled yet. Open the repository
Hardware-in-the-loop verification gate for coding agents on embedded firmware: rebuild, flash over ST-Link (STM32CubeProgrammer), then require the board to prove which build is running — UART boot banner carrying the git sha, a 64-byte SWD RAM signature, and console probes asserting on register readbacks (timer CCR, ADC). 8 MCP tools: doctor/build/flash/verify/probe/board_info/console. .
Overview
Hardware-in-the-loop verification gate for coding agents on embedded firmware: rebuild, flash over ST-Link (STM32CubeProgrammer), then require the board to prove which build is running — UART boot banner carrying the git sha, a 64-byte SWD RAM signature, and console probes asserting on register readbacks (timer CCR, ADC). 8 MCP tools: doctor/build/flash/verify/probe/board_info/console. .
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Flashgate runs locally over stdio.
Last checked 2026-11-18. Hardware-in-the-loop verification gate for coding agents on embedded firmware: rebuild, flash over ST-Link (STM32CubeProgrammer), then require the board to prove which build is running — UART boot banner carrying the git sha, a 64-byte SWD RAM signature, and console probes asserting on register readbacks (timer CCR, ADC). 8 MCP tools: doctor/build/flash/verify/probe/board_info/console. .