Cyan Eclipse Stage MCP

Vendor: Cyan Eclipse Technologies · Platforms: MCP over stdio (HTTP transport on roadmap)

What it does

• Console Registry whose enrollment requires a dev-mode attestation flag: a retail-mode console is invisible even if its portal answers
• Device Portal-shaped tooling: device info, app list, metadata-only install simulation, remote input, screenshot capture, power control
• Remote input validated as a whole sequence against an allowlisted vocabulary before the first event is sent
• Screenshot SHA-256 parity across tool result, stored file and receipt
• Policy ladder: install and power are Tier 2; restart is Tier 3 behind a confirmation token
• Forbidden capability names (profile, credential, retail-exploit class) refused by name; tools/list is exactly the 8 bridge tools

Tools

Problems it addresses

• I build games with an agent and need them deployed to my own Dev Mode console
• Playtest input and screenshots should be scriptable, with receipts
• Retail-mode consoles must be unreachable by the tooling

Not tested

• A real Xbox in Developer Mode — v0.1's portal is a local Device Portal-shaped stub (stdlib http, fixtures) simulating one console. Parity with the real Xbox Device Portal (auth, exact payload shapes, the /api/app/packagemanager package pipeline, behavior when the console is off) is [verify] and untested; connecting the owner's console is an owner-gated step.
• Real package deployment — v0.1 installs are fixture-metadata records by design; the real binary upload/register/install path is unbuilt, and binary-shaped payloads are refused by name at the bridge and the stub.
• Live frame capture — v0.1's screenshot is the stub's fixture PNG; no real console frame has been captured.
• Steam Deck / PC handhelds and Apple TV / Android TV tracks — designed in the Procure concept doc's Stage module (fully open to developer-account paths); no adapter exists in v0.1.

Bench scorecard: test-bench/results/eclipse-stage-mcp-2026-10-25.json