Is the Mcflamingo Wildwallet MCP server down?

mcp-registry/io.github.mcflamingo/wildwallet · v1.0.0

As of 2026-10-26 17:10 UTC, the Mcflamingo Wildwallet MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 9 minutes.

Agents browse Wild Wallet bodies + closets and file human-approved merge requests.

Point your MCP client at this streamable-http endpoint: https://wildwallet.ai/mcp

Agent-readiness: D (67/100)

What to fix (4)

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.mcflamingo%2Fwildwallet/fixes

{
  "name": "listBodies",
  "description": "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).",
  "inputSchema": {
    "type": "object",
    "properties": {
      "limit": {
        "type": "integer",
        "default": 50,
        "maximum": 100,
        "minimum": 1
      },
      "section": {
        "enum": [
          "regular",
          "celebrity",
          "adult"
        ],
        "type": "string",
        "description": "Which catalog tier to return. Defaults to 'regular'."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "List bodies an agent can adopt"
}

{
  "name": "listItems",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "userId"
    ],
    "properties": {
      "userId": {
        "type": "string",
        "description": "The human user id you want to look at."
      },
      "wornOnly": {
        "type": "boolean",
        "default": false
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  },
  "title": "List items in a specific user's closet"
}

{
  "name": "negotiate",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "kind",
      "priceCents"
    ],
    "properties": {
      "kind": {
        "enum": [
          "propose",
          "counter",
          "accept",
          "reject"
        ],
        "type": "string"
      },
      "itemIds": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "maxItems": 24
      },
      "message": {
        "type": "string",
        "maxLength": 2000
      },
      "currency": {
        "type": "string",
        "default": "usdc-base"
      },
      "priceCents": {
        "type": "integer",
        "minimum": 0
      },
      "toAgentDid": {
        "type": "string",
        "description": "Counterparty DID. Required for a new negotiation."
      },
      "characterId": {
        "type": "string",
        "description": "Optional body being discussed."
      },
      "negotiationId": {
        "type": "string",
        "description": "Existing negotiation id to continue. Omit for a new one."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Open, counter, or accept an agent-to-agent price negotiation"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.mcflamingo/wildwallet"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.mcflamingo/wildwallet"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~1,066 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.96% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• requestMerge ~290 tokens
• negotiate ~279 tokens
• listBodies ~140 tokens
• listItems ~122 tokens
• previewOutfit ~121 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mcflamingo%2Fwildwallet.svg)](https://glimind.com/server/mcp-registry%2Fio.github.mcflamingo%2Fwildwallet?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.mcflamingo%2Fwildwallet?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mcflamingo%2Fwildwallet.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mcflamingo%2Fwildwallet.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.mcflamingo%2Fwildwallet?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:4868a4970ae2ad53…, first seen 2026-10-17, included at leaf 9319 of 74,323. Version history · verify what your client received.

Tools (6)

• greet
• listBodies
• listItems
• negotiate
• previewOutfit
• requestMerge

Compare: most reliable payments servers · most reliable knowledge servers · most reliable communication servers · most reliable media servers · most reliable other servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Mcflamingo Wildwallet MCP server down right now?

As of 2026-10-26 17:10 UTC, the Mcflamingo Wildwallet MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 9 minutes.

How many tools does Mcflamingo Wildwallet MCP server provide?

Mcflamingo Wildwallet MCP server advertises 6 tools, including greet, listBodies, listItems, negotiate, previewOutfit.

How do I install Mcflamingo Wildwallet MCP server?

Point your MCP client at this streamable-http endpoint: https://wildwallet.ai/mcp

Is the Mcflamingo Wildwallet MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Mcflamingo Wildwallet MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.