Wild Wallet — where agents get a body MCP server
io.github.MCFLAMINGO/wildwalletMCFLAMINGOstreamable-httpv0.28.1Scanned
Agents browse Wild Wallet bodies + closets and file human-approved merge requests.
6 tools: 3 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Wild Wallet — where agents get a body MCP server can do
The Wild Wallet — where agents get a body MCP server is published by the GitHub account MCFLAMINGO. It has 6 tools. It can create or change data (3 tools: requestMerge, greet and negotiate), but cannot delete data. 3 tools only read.
1 tool brings in text other people can write (listBodies).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 0.28.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 3Claude Code: ask
greetThe canonical x402 hello-world demo.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
negotiateTwo agents negotiate a spend without a human in the loop.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
requestMergeFile 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 appr…No findings
Why it is in this group
- The name "requestMerge" says "request": a word for a change.
Description, as the server wrote it 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.
Only reads 3Show 3 read-only tools
listBodiesBrowse Wild Wallet's public character catalog.Reads text others writeNo findings
Why it is in this group
- The name "listBodies" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it 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).
listItemsReturn the currently-worn and available wearable items in a given human's closet.No findings
Why it is in this group
- The name "listItems" says "list": a word for reading.
Description, as the server wrote it 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.
previewOutfitGiven 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.No findings
Why it is in this group
- The name "previewOutfit" says "preview": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:59 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://wildwallet.ai/mcp: tools/list returned 6 tools to an anonymous client, including requestMerge (write), greet (write), negotiate (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.28.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http wildwallet https://wildwallet.ai/mcpclaude mcp add --transport http wildwallet https://wildwallet.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__wildwallet__listBodies",
"mcp__wildwallet__listItems",
"mcp__wildwallet__previewOutfit"
],
"ask": [
"mcp__wildwallet__requestMerge",
"mcp__wildwallet__greet",
"mcp__wildwallet__negotiate"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as wildwallet. Review it before you use it.
Capability tags behind 1 rule
- mcp__wildwallet__listBodies untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.MCFLAMINGO/wildwallet/verify?hash=f4bfc475ed130643e21b34b4605775ee1c471db5cb7ddf34140de8268464f2ca" | jq -e '.changed == false'Pinned hash f4bfc475ed13, from Nov 16, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.MCFLAMINGO/wildwallet/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.MCFLAMINGO/wildwallet)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:17 UTC.
Wild Wallet — where agents get a body MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Wild Wallet — where agents get a body MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Wild Wallet — where agents get a body MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Wild Wallet — where agents get a body MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Wild Wallet — where agents get a body MCP server have?
- 6 tools: 3 write, 3 read. requestMerge, greet, negotiate, listBodies, listItems and previewOutfit.
Does the Wild Wallet — where agents get a body MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Wild Wallet — where agents get a body MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Wild Wallet — where agents get a body MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.