Agent requests approval
The MCP gateway sends only an action summary and SHA-256 hash. Prompt context stays local.
Private alpha · Guided setup
Human approval for agent actions.
Review an agent action, approve it with a passkey, and release a proof for that exact action. Start with a guided, non-production trial.
120-second, single-use challenges Passkeys locked to goodroom.in No prompts or agent context retained
EXAMPLE · NOT A LIVE REQUEST
gr_8f2a91Non-production trial
Approve a local staging release
agent claude-code
tool staging-deploy
hash sha256:7d19c3a5...2e04
Physical presence required
Verify with your enrolled passkey
Passkey approval preview
Live requests expire after 120 seconds
Zero-trust by design
No silent execution.
Protected calls pause for passkey approval. Your tool wrapper must verify the proof before executing; GoodRoom does not sandbox an agent or protect unguarded tools.
You verify physically
Touch ID, Face ID, Windows Hello, or a hardware key signs a 120-second challenge.
Execution unlocks
The agent receives a short-lived, single-use proof bound to the approved action.
Built for agent runtimes
Start with one protected action.
Add the MCP server to Claude Code, Cursor, or any compatible runtime. Your agent can request approval without gaining access to biometric credentials.
- 120-second, single-use challenges
- Passkeys locked to goodroom.in
- No prompts or agent context retained
- Cryptographic proof for every approval
Terminal
$ git clone https://github.com/kairosgoodroom/goodroomverify.git
$ cd goodroomverify && npm install
$ npm run build -w @goodroom/contracts -w @goodroom/proof -w @goodroom/mcpCommon questions
Human approval, without ambiguity.
What is human approval for AI agents?
Human approval is a control that pauses a sensitive agent action until a person reviews and authorizes it. GoodRoom.verify binds that approval to the action with a short-lived cryptographic proof.
How does GoodRoom.verify secure MCP tool calls?
An MCP gateway submits an action summary and SHA-256 hash. The operator approves a 120-second challenge with a passkey, and the agent receives a single-use proof for only that action.
Does GoodRoom.verify store agent prompts?
No. Prompt context stays with the agent runtime. GoodRoom.verify handles the action summary, action hash, challenge, and approval proof needed for verification.
Which passkeys and agent runtimes are supported?
The approval flow is designed for Touch ID, Face ID, Windows Hello, and hardware security keys. The MCP integration works with compatible agent runtimes such as Claude Code and Cursor.