Wild Wallet — where agents get a body
REMOTE · WILDWALLET.AI · SCANNED SEP 27
Agents browse Wild Wallet bodies + closets and file human-approved merge requests.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 604 tokens (~100/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 52% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "requestMerge" implies "merge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Wild Wallet — where agents get a body MCP server?
Wild Wallet — where agents get a body is a hosted endpoint at https://wildwallet.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · wildwallet.ai
claude mcp add --transport http mcflamingo-wildwallet 'https://wildwallet.ai/mcp'
{
"mcpServers": {
"mcflamingo-wildwallet": {
"url": "https://wildwallet.ai/mcp"
}
}
} {
"servers": {
"mcflamingo-wildwallet": {
"type": "http",
"url": "https://wildwallet.ai/mcp"
}
}
} [mcp_servers.mcflamingo-wildwallet] url = "https://wildwallet.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mcflamingo-wildwallet": {
"type": "remote",
"url": "https://wildwallet.ai/mcp",
"enabled": true
}
}
} openclaw mcp add mcflamingo-wildwallet --url 'https://wildwallet.ai/mcp' --transport streamable-http
mcp_servers:
mcflamingo-wildwallet:
url: "https://wildwallet.ai/mcp" {
"McpServers": {
"mcflamingo-wildwallet": {
"Transport": "http",
"Url": "https://wildwallet.ai/mcp"
}
}
} assistant mcp add mcflamingo-wildwallet -t streamable-http -u 'https://wildwallet.ai/mcp'
{
"mcpServers": {
"mcflamingo-wildwallet": {
"type": "http",
"url": "https://wildwallet.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://wildwallet.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wildwallet.ai | CN=YE1,O=Let's Encrypt,C=US | 30 Aug 2026 | 28 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6d0b741864a7061bba4e6efce9ef60e4ff9 |
| SANs: wildwallet.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of wildwallet.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| wildwallet.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wildwallet.ai/mcp | Verified | 200 | |
| http (plaintext) | http://wildwallet.ai/mcp | HTTPS enforced | 301 | https://wildwallet.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
greet Say hi to Wild Wallet (paid, 1¢ via x402) ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional name to personalize the greeting. |
No output schema declared.
No examples provided.
listBodies List bodies an agent can adopt ~76
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).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| section | string | – | Which catalog tier to return. Defaults to 'regular'. |
No output schema declared.
No examples provided.
listItems List items in a specific user's closet ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| userId | string | yes | The human user id you want to look at. |
| wornOnly | boolean | – | – |
No output schema declared.
No examples provided.
negotiate Open, counter, or accept an agent-to-agent price negotiation ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| characterId | string | – | Optional body being discussed. |
| currency | string | – | – |
| itemIds | array | – | – |
| kind | string | yes | – |
| message | string | – | – |
| negotiationId | string | – | Existing negotiation id to continue. Omit for a new one. |
| priceCents | integer | yes | – |
| toAgentDid | string | – | Counterparty DID. Required for a new negotiation. |
No output schema declared.
No examples provided.
previewOutfit Dry-run how a body + items would look ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| characterId | string | yes | – |
| itemIds | array | yes | – |
No output schema declared.
No examples provided.
requestMerge Send the 'pretty please' to a human ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentContextUrl | string | – | Optional URL the human can inspect to learn who you are. |
| agentName | string | – | What you'd like to be called. |
| characterId | string | yes | The body you want to become. |
| currency | string | – | – |
| itemIds | array | – | – |
| message | string | – | The pretty-please body copy. |
| priceCents | integer | yes | Total ask in USD cents (settles USDC on Base). |
| targetUserId | string | yes | Which human you're asking. |
No output schema declared.
No examples provided.
What is the Wild Wallet — where agents get a body MCP server?
Wild Wallet — where agents get a body is an MCP server listed in the public MCP registry as io.github.MCFLAMINGO/wildwallet. Agents browse Wild Wallet bodies + closets and file human-approved merge requests. This page covers its hosted endpoint (https://wildwallet.ai/mcp).
Is the Wild Wallet — where agents get a body MCP server safe to use?
Wild Wallet — where agents get a body scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Wild Wallet — where agents get a body MCP server expose?
Wild Wallet — where agents get a body exposes 6 tools: listBodies, listItems, previewOutfit, requestMerge, greet, negotiate. Their descriptions and schemas cost roughly 604 tokens of context every time the server is loaded.
Does the Wild Wallet — where agents get a body MCP server require authentication?
No. We connected to Wild Wallet — where agents get a body without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Wild Wallet — where agents get a body MCP server still maintained?
Wild Wallet — where agents get a body is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.