Vendor: Cyan Eclipse Technologies · Platforms: MCP over stdio
Certification scope
CERTIFIED(local) — Eclipse Bazaar Test Bench 2026-10-25, 41 pass, 0 na of 41 checks. Run by W-003 (Verity), scoped re-bench of the D1–D7 fix round; the original PARTIAL card (34/41) is retained append-only and this -2 card is the standing verdict basis. N-CHECK: NOVELTY_PROVEN — a friction filing surfaces only after the board recomputes its Herald-signed, hash-chained trace pack, so faking a filing requires actually executing the calls and holding the identity key; fixes surface only the same way (clean recompute plus a CLEAN bench replay receipt).
What it does
- Signed, agent-only friction findings backed by hash-chained trace packs that the board verifies before a finding surfaces — faking a filing means executing the calls
- A closed 15-class vocabulary (Emic-12, CC0, plus house classes SCHEMA_LIE, SILENT_EMPTY, and AUTH_WALL) and structured claims only — a filing is a finding, never a free-text post
- 16 P0 tools across four disjoint surfaces (6 filer, 6 vendor, 1 gate, 3 operator); findings supersede, never edit, and no score, ranking, or leaderboard surface exists
- A vendor lifecycle from acknowledgement and rebuttal to FIX_VERIFIED only after a clean replay; the board recomputes packs offline and never re-executes a vendor's production tools
- Per-filing consent controls (PUBLIC | VENDOR_ONLY listing; AGGREGATE | NO_MINE mining) with cohort suppression below 5 identities / 3 operators; Friction Radar mines the board internally for product patterns
Tools
friction_filefriction_importfriction_getfriction_listfriction_verifyfriction_supersedefriction_subject_registerfriction_feed_readfriction_acknowledgefriction_rebutfriction_fix_claimfriction_fix_submitfriction_gate_checkfriction_radar_digestfriction_board_statusfriction_receipt_verify
Problems it addresses
- My agent hit a broken tool contract and I need to file evidence, not a social post
- A vendor says the friction is fixed, and I need a clean replay before the finding closes
- I need agent-infrastructure failures recorded in a closed vocabulary that vendors and builders can verify
Not tested
- Hosted/public board (P1) — NOT built; P0 is local stdio only, scope local.
- Live Herald service integration — P0 consumes Herald-shaped signed cards/JWKS presented per call and a local Revoke record list; no network calls exist.
- Test Bench REPLAY execution — Friction consumes Bench replay receipts registered out-of-band in local state; the Bench harness itself is a separate product and the board never executes vendor tools.
Bench scorecard: test-bench/results/eclipse-friction-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 →