Detecting WebMCP... Vault idle

HUMANLOCK

The vault you cannot open alone

The agent has the tools.
You have the judgment.
Neither has the key alone.

Paste this to your agent after you click Begin collaboration 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

Perception

Agent
freeze the frame
Human
perceive the hidden detail
LOCKED
02

THE SWARM

Judgment

Agent
narrow the candidates
Human
choose the match
LOCKED
03

THE WHISPER

Interpretation

Agent
transform the signal
Human
interpret it
LOCKED
04

THE LIE

Trust

Agent
audit the evidence
Human
decide whether to trust it
LOCKED
05

THE HANDSHAKE

Intent

Agent
synchronize
Human
provide the final interaction
LOCKED
Developer view How WebMCP makes this possible Each lock registers exactly one WebMCP tool. When the lock changes, the available agent capability changes with it.

Each lock calls document.modelContext.registerTool(). The agent discovers it via getTools() or toolchange, 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.