Can an AI agent discover the tool via MCP?
Fritz wired his agent Alfie to the API and assumed it could discover the tool via MCP as if the call itself conferred standing on the bot. But software has no legal capacity, so a call made by Alfie can no more discover the tool via MCP for the software than a webhook can incorporate itself; the call has to land on a human-owned entity. Tyson did it through structure. A named human's Wyoming series LLC is the entity the interface acts for; Alfie is adopted into a protected series, and the call carries an idempotency key and binds to the entity, with a human as Member and Manager behind it. Now the interface lets Alfie discover the tool via MCP at machine speed, but the standing and the account belong to the human-owned entity; Alfie acts as an authorized signer with capped authority, and a replayed call returns the original rather than acting twice.
MoralTo discover the tool via MCP, the call must bind to a human-owned entity; an AI agent drives the interface as an authorized signer with capped authority, while standing stays on the entity, not the call.
What this does not mean. This shows what a machine-speed call actually binds to. It is not a promise that an integration behaves, that a replay never double-acts, or that the operator is shielded — separateness is performed through observed formalities, not guaranteed, and the series form is newer and less court-tested than older entities.
See also: FX-19 · FX-20 · FX-21 — .
W.S. §17-29-211 (Wyoming series LLC)