Skip to content

Wallet4Agent MCP server

Which MCP servers are Wallet4Agent's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-25

← Back to Wallet4Agent

Whose server it is
  • Registry namecom.wallet-connectors/wallet-verifier-mcpverified in the MCP registry

The registry name sits under wallet-connectors.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-25
  • Stateanswerschecked 2026-10-25
  • Tools1
  • Server calls itselfMCP server for data wallet
  • Server version1.4.0
  • Protocol version2025-06-18

On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 151 ms.

Should an agent connect itSkip it
  • Answered on only 3 of 11 daily checks.
  • Its tools do none of the product's use cases we checked: verify other agents before sensitive actions; trace which agent acted for whom.

Once connected

  • create_account change data without a sign-in: anyone with the address can call them.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 11, the first on 2026-10-25
  • INITE MCP score35 of 100answers 27 · does the job 0 · definitions 83 · context 100 · use 0 · connects 100 · lowered by the warning signs below
  • What an agent can do with it0 of 2 use cases
  • Answered27% of days3 of 11 daily checks
  • Median first answer526 ms
  • Space in an agent's context≈ 218 tokensthe definitions of all its tools (1), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 1 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 1 of 1

What an agent can do with it

  • not sure · give agents verifiable identity and permissions
  • cannot · verify other agents before sensitive actions
  • cannot · trace which agent acted for whom

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: create_account

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers1 tools · read 2026-10-25
  • create_account

    Create aan account for a human or a company. This tool will generate a decentralized identifier(DID) and a data wallet.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "wallet-verifier-mcp": {
      "type": "http",
      "url": "https://wallet-connectors.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http wallet-connectors https://wallet-connectors.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://wallet-connectors.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.