Skip to content
BLOKZ.dev

The Delegation Chain

Five hops — Human → Orchestrator → Sub-Agent → MCP Tool → Chain Call — and zero authentication in the baseline. Toggle No Auth, IBCT Compact, or IBCT Chained; tap any edge chip to see what its token proves, what it carries, and what it can't verify. Based on AIP arXiv:2603.24775.

diagram SVG AgentsSecurityWeb3 Jun 21, 2026
⬢ loading artifact…
The Delegation Chain — tap an edge chip to inspect its token · use mode tabs to switch between No Auth, IBCT Compact, and IBCT Chained open artifact ↗

View artifact source on GitHub ↗

Appears in

Who Authorized That? The Delegation Gap in AI Agent Tool Calls

A scan of ~2,000 MCP servers found zero with authentication. When an AI agent calls a tool, the tool has no idea who authorized it, with what scope, or whether a human was ever involved. IBCT tokens and the HDP IETF draft add an unforgeable answer — in 0.049 ms Rust verification.

8 min read ⬢ interactive

Type to search the archive.