Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
L

Lion-1209/flashgate

Independent directory — not the official site. Details below come from the project's public repository.

flashgate answers one specific question: the firmware you just built — does

1 ★ measured · checked 2026-11-19

Before you install: command ownership unverified - shown for reference only · license MIT

First step (reference only, ownership unverified): pip install "flashgate[bench]" # optional extra -> device-connect-edge

★ 1·updated 2026-10-12
View on GitHub ↗Direct link · no redirect page

We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →

Star count
1 ★ · Lion-1209/flashgate · read from the GitHub search API · (checked 2026-11-19 20:00:48)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
Score
score 300 · 1 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository Lion-1209/flashgate;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.
README excerpt (English, untranslated) · Read the full README on GitHub →

# flashgate

Excerpted from the repository README (abridged)

flashgate answers one specific question: the firmware you just built — does
it actually run on the board?
It automates the whole chain: compile, flash over ST-Link, wait for the
board to report its own identity, then drive the actual feature over the
console and assert on hardware register readbacks. Any broken step ends
with a non-zero exit code and a reason.
build → flash over ST-Link → board boots → evidence → probes → exit code
A remote agent driving the bench over the network (Wi-Fi laptop → wired
bench, OpenOCD backend) — real output:
$ flashgate --board apollo-openocd.yaml verify --all-probes
[verify] apollo-h743: build -> flash -> boot banner -> probes
[build] OK in 1.3s, 0 warning(s)
[flash] Apollo.bin @ 0x08000000 via openocd:port=SWD
[flash] OK (written, verified, started)
FLASHGATE-BOOT board=apollo-h743 git=e87efd8-dirty build=2026-09-16T02:48:14Z rtos=FreeRTOS
[probe] led-demo: LED state-machine set/readback + PWM CCR sanity
step 1: led-demo> led0 breath
board: OK led0 state=BREATH
step 2: led-demo> led0?
board: OK led0 state=BREATH ccr=691 led0 breath
board: OK led0 state=OFF ← readback exposes the silent no-op
The same broken tree is blocked at most twice, then released with a loud
warning — the session can never wedge, and a failure is never silently
swallowed.
One verify at a time per bench: concurrent verifies (a user-level and a
session-level Stop hook firing on the same stop, or a manual run racing
the hook) serialize on an OS-owned lock file under the firmware's
.flashgate/ instead of fighting over the console serial port — the
second one waits (default 300 s, FLASHGATE_VERIFY_LOCK_WAIT), and a
timed-out wait is a truthful exit 6 ("bench busy"), never a misleading
serial error. Register the hook at ONE level only: in the common case
stacking now just costs a redundant second verify; on a very slow bench
it can still exhaust the hook's own subprocess timeout, so it is a
crutch, not a supported setup.
## Verification records
Every verify — passing or failing — leaves an evidence record at
/.flashgate/records/ - - .json: the
per-check verdicts (build/flash/boot/identity/probe:, with
skipped meaning never executed, never a silent absence), the raw
evidence behind them (banner line, SWD signature fields, console tails,
failing probe transcripts), the artifact sha256, and the exact
tree+profile+tool-version identity the verdict applies to. Every record
also carries a coverage block — the "what this PASS proves" statement:
what was verified, what was NOT (physical effects, everything outside
the listed probes, environmental conditions), plus the board profile's
own caveats (coverage.notes) — a green record never reads as "all
functionality passed". The MCP
verify tool returns the same record inline as data.record. Format:
docs/record-schema.md. Keep .flashgate/ in your
firmware repo's .gitignore (the shipped example does), or every record
write churns the fingerprint. A record that cannot be written is a
warning, never a changed exit code — and a crashed run still leaves one.
The newest ~500 records are kept (best-effort pruning). flashgate verify
--json prints this run's record as pure-ASCII JSON on stdout (human logs
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/lion-1209-flashgate/)
Source
awesome · https://github.com/Lion-1209/flashgate
Browse by field
MCP servers
Traction
1 ★
Listed by
3 independent sources
added
today

More MCP servers

All 6,555 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index