Vendor: Cyan Eclipse Technologies · Platforms: MCP over stdio
Certification scope
CERTIFIED(simulator) — Eclipse Bazaar Test Bench 2026-10-25, run 2 (standing): 31 pass of 31 checks. Run 1 PARTIAL (30/31) retained append-only: its sole failure was a bench-assertion defect in H10 (compared full error dicts incl. the caller-echoed tool name), not a product defect. Scope: SIMULATOR ONLY — P0 is ROS 2 + Gazebo + UR-class arm sim, in-process; NO hardware claim of any class is made. Liability counsel gates P1 real motion only. N-CHECK: NOVELTY_PROVEN — rename census 6/22 = 27% (<80%); the mandate-and-bridge mechanism exists in no incumbent (Boston Dynamics ships dispatch in Orbit; nobody ships the signed authority layer).
What it does
- Physical task authority exists only inside a Herald-signed mandate pinning agent × robot serials × human-authored task-template hashes × workspace envelope × speed/force ceilings × occupancy class × time window
- Enforcement sits at a site bridge that is the only routed path to the robot — the envelope is checked before motion, an expired mandate stops the task, and a human e-stop lands in the terminal HUMAN_OVERRIDE state
- Every session — tasks, refusals, gaps, envelope exits, human overrides — is sealed into a Blackbox-form evidence pack verifiable offline (Tether Proof), with a static conformance checker (Tether Gauge) for mandates and templates before any robot moves
- No T2 direct-motion surface exists in v0/v1; closed platforms (Tesla Optimus and peers) are published wait positions, never a logo wall; a mandate never substitutes for a site risk assessment
- 22 tools across agent, operator and verifier surfaces; the hostile-agent suite (H1–H16) passes in full against the simulator site
Tools
fleet_discoversession_opentask_templates_listtask_dispatchtask_statustask_aborttelemetry_readimage_readsession_closemandate_registermandate_revoketemplate_registertemplate_revokesite_freeze_setsession_reattestpack_verifypack_renderpack_comparegauge_check_mandategauge_check_templategauge_check_pairgauge_limits_list
Problems it addresses
- An agent needs to move a real robot and I need the authority bounded, signed and revocable — not a prompt
- When something goes wrong on the floor I need a sealed evidence pack, not a vendor log
- I run Spot or a UR arm and need governance + evidence across vendors, not another dispatch layer
Not tested
- Real hardware of any class.
- Real vendor SDKs (Spot / Unitree / UR-RTDE).
- Real e-stop / lease hardware.
- Isaac Sim.
- Multi-robot sessions.
- Hosted / multi-site operation.
- T2 direct motion (refused by design, §3).
- Closed platforms: Tesla Optimus, Figure, Apptronik, Atlas, NEO (no surface exists, §4.1).
- Orbit dispatch (vendor's, not ours, §4.2).
Bench scorecard: test-bench/results/eclipse-tether-mcp-2026-10-25-2.json
Evaluation-intake listing
This listing records the tool's place in the Bazaar's evaluation
and monitoring pipeline, with the evidence gathered so far printed above — verdict, scope,
and not-tested items included. It is not sold on this site, and its presence in the catalog
is not a claim beyond that evidence. The service behind every verdict is the bench:
what a bench run buys →