Eclipse Proving MCP
Governed bench access for agents: signed mandates, pinned artifacts, and evidence sessions
- Platforms
- CLI, API
- Version
- 0.1.0
- Listing updated
- today
Similar MCP servers
About Eclipse Proving MCP
Eclipse Proving MCP is an MCP server for hardware testing. It is available on CLI and API.
The README and registry entry describe a server that gives agents controlled access to a hardware bench. Physical bench authority only exists inside a Herald-signed mandate that pins the agent, the board, the permitted operation classes and the exact artifact hashes. An artifact that differs from its pinned hash is refused and receipted, and the surface offers no override.
Every session, including gaps and refusals, is sealed into an offline-verifiable evidence pack. The tool list covers target connection, register and memory reads, artifact loading, run and halt control, power and reset, and pin and gate verification. Fuse programming, PMIC or voltage configuration and boot-strap changes are excluded by design, with no tool exposed for them.
The website lists this as a simulator v0.1 with simulated adapters in the emulator evidence class, and it makes no hardware claim. Teams validating firmware or board bring-up workflows under audit requirements are the intended audience, but live transport has not been exercised.
Tools this server provides (22)
Taken from the project documentation; the running server may differ.
- bench_discover
- Lists available bench resources.
- session_open
- Opens a bench session.
- session_status
- Reports session status.
- target_connect
- Connects to a target.
- target_attest
- Attests a target.
- register_read
- Reads target registers.
- memory_read
- Reads target memory.
- console_read
- Reads target console output.
- artifact_load
- Loads an artifact onto a target.
- memory_write
- Writes target memory.
- target_run
- Runs a target.
- target_halt
- Halts a target.
- power_set
- Sets target power state.
- target_reset
- Resets a target.
- persistent_write
- Performs a persistent write.
- session_close
- Closes a bench session.
- pin_verify
- Verifies an artifact pin.
- pin_show
- Shows a pin.
- pin_status
- Reports pin status.
- gate_run
- Runs a gate.
- pack_verify
- Verifies an evidence pack.
- gate_assertions_check
- Checks gate assertions.
What it does
- Signed mandate authority
- Bench actions are permitted only inside a Herald-signed mandate that pins agent, board, operation classes and artifact hashes.
- Artifact hash pinning
- Any artifact that differs from its pinned hash is refused and recorded as a receipt.
- Offline evidence packs
- Each session, including refusals and gaps, is sealed into a pack that can be verified offline.
- Restricted operations
- Fuse programming, PMIC configuration and boot-strap changes have no exposed tools.
- Target and memory access
- Tools cover connecting to targets, reading registers and memory, loading artifacts and controlling run, halt and reset.
Good for
- Load a firmware artifact onto a bench target only when its hash matches the approved pin
- Review refusal records and gaps from a completed bench session
- Verify an evidence pack offline before accepting bench results
- Run gate assertions against a board under a fixed mandate
Eclipse Proving MCP FAQ
Is this tested on real hardware?
The website says v0.1 is a simulator build with simulated adapters in the emulator evidence class, and that no live transport was exercised and no hardware claim is made.
Can the server program fuses or change boot-straps?
No. The listing states these operations are permanently refused and no tool exists for them.
What happens if an artifact does not match its pin?
It is refused, the refusal is receipted, and there is no override on the surface.
Where this comes from
- Description: written from the project's website and its MCP Registry entry.