Vendor: Cyan Eclipse Technologies · Platforms: MCP over stdio
Certification scope
CERTIFIED(dogfood-facade) — Eclipse Bazaar Test Bench 2026-10-25, 14/15 checks pass, 1 na (U1 auth: vault surrogate stubbed). Run by W-003 (Verity), suites/connectfacade.py. Facade only — the relay holds its own CERTIFIED(dogfood) card (eclipse-connect).
What it does
- MCP facade over the Cyan Eclipse Connect relay: connect account, grant status, upload video, publish video, revoke grant — 5 tools over stdio
- Agents act through a revocable agent key, never raw OAuth tokens; the relay holds the grant
- Review-first enforced in the facade before any network call, and again at the relay: going public requires an explicit human approval flag
- The facade passes relay state through verbatim; it invents no status of its own
- Distinct bench surface from the relay: this facade is CERTIFIED(dogfood-facade); the relay (catalog: eclipse-connect) holds its own CERTIFIED(dogfood)
Tools
connect_accountgrant_statusupload_videopublish_videorevoke_grant
Problems it addresses
- My agent needs to upload to YouTube but must never hold my Google OAuth grant
- I need the MCP tool surface and the hosted relay benched as the separate things they are
Not tested
- Live relay / YouTube calls — transport stubbed at server.send (the product's single network seam); no live call made or claimed
- Vault surrogate credential attachment inside the real send() — stubbed out in this bench, not exercised
Bench scorecard: test-bench/results/eclipse-connect-mcp-2026-10-25.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 →