Echo Show card · 1280 × 800

connecting…

Server and read token

Unsay server Defaults to this page’s own origin when it is served over http. Read token — Bearer, scope care.read.user This screen is an MCP host: initialize, resources/list, resources/read, resources/subscribe, then the SSE stream. It renders care:// only — a token carrying care.read.assistant would not change that, because the one thing this screen must never do is show Ray why he is being told to have someone nearby.

connecting

weight bearing

—

This is the screen, not a picture of one. It holds an MCP session against the running server and repaints when notifications/resources/updated arrives. The status chip on the device says which path is carrying the change — a native subscription, or the whats_changed tool, which is the fallback for a host that cannot subscribe. Both are built, and this page exercises whichever one is actually available.

With no server answering, the chip reads SEED · NOT LIVE and the screen shows the committed record from src/seed.ts with its pinned clock. It never invents a correction: no strike-through and no amber dot can appear unless a real revision arrived.

Any origin can point this page at a server. The Unsay server answers the preflight and allows the MCP headers, and that grants nothing: every request carries its own Bearer token, and there is no cookie for another origin to borrow. Everything above is live.

Press F for presentation mode — the page chrome disappears and the device fills the display, which is what the demo video films. Open the clinician screen in another window and publish a revision to watch this one retract.