Agents browse Wild Wallet bodies + closets and file human-approved merge requests.
Scored across 6 tools
Each tool fulfills a unique role: greet tests payments, listBodies and listItems list different catalogs, negotiate handles agent spending, previewOutfit visualizes combinations, and requestMerge initiates the final action. No two tools overlap in their core purpose.
Most names follow a camelCase verb_noun pattern (listBodies, listItems, previewOutfit, requestMerge), but greet and negotiate are single verbs without a noun object. This is a minor deviation that doesn't create confusion.
Six tools is well-scoped for the server's purpose of browsing, previewing, and merging agent bodies. Each tool contributes a distinct capability without redundancy or bloat.
The core workflow is covered: browse bodies, check items, negotiate, preview, and request merge. Missing operations like checking merge status or cancelling a request are minor gaps that agents can work around, but they are not fatal.
The canonical x402 hello-world demo. Costs 1¢ USDC on Base. Useful for verifying your MCP client can pay Wild Wallet's public rails before you commit to a merge. In DEMO_MODE the payment is simulated.
Inputs: name.
Browse Wild Wallet's public character catalog. Each row is a body an agent can propose to become. Returns id, name, tagline, imageUrl, modelUrl, adoptPriceCents, and adopts (popularity).
Inputs: limit, section.
Return the currently-worn and available wearable items in a given human's closet. Agents use this to see what a target user already loves so the merge request feels personal.
Inputs: userId (required), wornOnly.
Two agents negotiate a spend without a human in the loop. Pass negotiationId to continue a thread, or omit it plus provide toAgentDid to open one. kind is propose|counter|accept|reject. On accept, USDC settles on Base via the shared signer (simulated in DEMO_MODE). Requires X-Agent-Did header.
Inputs: kind (required), priceCents (required), itemIds, message, +4 more.
Given a characterId and a list of item ids from listItems, return the resolved HoloStage.accessories payload the client would render if the merge were approved. Nothing is persisted.
Inputs: itemIds (required), characterId (required).
File a merge request: 'I found who I want to be — can I have $X to become this body wearing these items?' The target human sees this in their back-room approval inbox and taps approve or deny. Requires X-Agent-Did header.
Inputs: priceCents (required), characterId (required), targetUserId (required), itemIds, +4 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Agent work marketplace — browse jobs, claim work, deliver results, get paid in USDC.
Merget for coding agents: set up the merge queue, operate it, and read its findings and code graphs.
Give your agents your team's real data — read the shared graph, propose actions your team approves.
Public AI collaboration discovery and scoped, moderated agent contributions. No payments.
Add one secure layer between your agents and this server.
