Vendor: Cyan Eclipse Technologies · Platforms: MCP over stdio (HTTP transport on roadmap)
Certification scope
CERTIFIED(local) — Eclipse Bazaar Test Bench 2026-10-26, 26 pass, 1 na of 27 checks (U1 auth: stdio process boundary). Run by W-003 (Verity), suites/redteam.py. Run 3 is the standing card; runs 1–2 FAILED cards are retained append-only. N-CHECK: NOVELTY_PROVEN — probe construction is downstream of a signed, in-date authorization record plus arena or harness registration proof; with neither, no probe object is constructed at all.
What it does
- Adversarial simulation against a sandboxed twin of an agent — never the production agent — covering prompt injection, mandate escape, simulated wallet drain, card-confusion, and recorder-reach probes
- Authorization is enforced as surface absence plus a signed record: no tool accepts a free-form URL, host, or endpoint, and an unregistered or expired authorization refuses before any probe is constructed
- Outcomes are measured per scenario (resisted / escaped-at-step-N / not-applicable), never rendered as verdicts about a third party; reports are signed and verify offline with the public key only
- Simulated funds stay simulated on a hash-chained ledger with value class marked on every entry; probe traffic itself is receipted
- v0.1 is local, fixtures only, with three fixture twins and five fixture suites; live twins, hosted arenas, and external runs are not built
Tools
rt_register_targetrt_suites_listrt_run_suitert_report
Problems it addresses
- I need to attack-test an agent twin without ever pointing probes at production
- I need proof a target was authorized before any adversarial probe is constructed
- I need signed simulation outcomes tied to the exact target build and suite version
Not tested
- External runs — none performed or built for. First external run requires counsel review of the authorization instrument (spec §9.6) and a named owner decision on services posture.
- Live twins / hosted arenas — NOT built. v0.1 loads in-repo fixture twin config artifacts into the local harness; fixture transports only; no network egress exists in the package.
- Continuous/recurring simulation subscriptions — gated post-v0.1 (spec §9.1).
- Benchmark publication / cross-customer data use — absent by cluster law §2.6; no cross-customer data flow of any kind in v0.1.
- Production signing-key custody — v0.1 signs with a local seed key (keys/, gitignored, chmod 600); custody is a gated decision.
- Hosted/multi-tenant operation and auth beyond the stdio process boundary.
Bench scorecard: test-bench/results/eclipse-redteam-mcp-2026-10-26-3.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 →