An AI agent can reach AINumbers workflows through WebMCP in your browser, the remote MCP server, or Helm on your own machine. Teal dashed lines mark your device and gold marks an AINumbers server, so you can see where every step computes.
Compare where each step computes when an AI agent reaches AINumbers through WebMCP, the remote MCP server or Helm, and what each door means for your inputs.
| Door | Compute runs on | Your inputs reach AINumbers |
|---|---|---|
| WebMCP | Your browser tab. The page registers its tools and the agent in your browser calls them. | Never |
| Remote MCP, compute auto | Our Cloudflare Worker at mcp.ainumbers.co for gpu:false kernels. | Yes, processed transiently and never stored |
| Remote MCP, compute browser | Your browser tab through a prefilled delegation URL. gpu:true tools always take this path. | Only the call arguments, passed through to build the link and not stored |
| Remote MCP, self-hosted | The same worker deployed to your own Cloudflare account. | Never |
| Helm | helmd on your machine, reached on 127.0.0.1:4173. | Never |
In every door your AI host sees your prompt and the results it gets back. Which host you use is your choice, and a local model keeps that part on your machine too.
Six real ChainGraph workflows, two per door. WebMCP runs Web Bot Auth and C2PA verification chains. Remote MCP runs the Canton margin call and Tempo on-chain AML. Helm runs the agent identity pack and the AP2 payment receipt pack.
In the Tempo chain, art-10 is a gpu:true tool, so the worker hands it back to your browser. Tick compute: "browser" to send every remote MCP step there.
Every door returns an OpenChainGraph artifact with an execution_hash, so one Verification Desk checks all six offline.
Chains and steps come from chaingraph.json, Helm packs and .well-known/webmcp.json. Input values are synthetic and hashes are SHA-256 over the demo values, computed in this page. WebMCP is an early browser API (a Chrome flag or the origin trial), and its page registrations are still being hardened. The remote server records per-call metadata for abuse monitoring (tool name, a pseudonymous caller hash, success and latency) and never the inputs. Helm is in maintenance mode and installs with winget, Homebrew or npm.