Detecting WebMCP... Vault idle
LOCKED --

The vault you cannot open alone

Five locks. Each one splits what you can see from what the agent can call. Human alone fails. Agent alone fails. Together, you open it.

Paste this to your agent after you click Enter vault List my WebMCP tools and help me open this vault. Start with THE BLUR: freeze_frame({ timestamp: 300 })

Click a call to copy it for your agent

01

THE BLUR

High-frame-rate flash, freeze to reveal

LOCKED
02

THE SWARM

Agent narrows lookalikes, you pick one

LOCKED
03

THE WHISPER

Agent renders spectrogram, you read it

LOCKED
04

THE LIE

Agent audits, you decide whom to trust

LOCKED
05

THE HANDSHAKE

50ms human and agent sync

LOCKED

How WebMCP makes this possible

Each lock registers one document.modelContext.registerTool() tool. The agent discovers it via getTools() or toolchange event, calls it with structured args, and the page mutates shared DOM state. Human and agent see the same vault. Neither can cheat: tools validate inputs and locks judge deterministically.

Click to copy a call for your agent

Judges: open this URL in the ChatGPT in-app browser, or Chrome Canary with chrome://flags/#enable-webmcp. On phones, tap to play audio (autoplay is blocked) and expect a coarser canvas than a desktop GPU. Shared certificate links (?code=&sig=) render without WebMCP.