verify

Cryptographic proof of wallet ownership in two steps, with no keys and no custody.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
80%
Naming quality
90%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~461Tokens (tool definitions)
~968 BTypical response size
Minimal attention impact (0.36% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "verify": {
      "url": "https://auth.xbarry.ai/api/mcp/verify"
    }
  }
}

Remote endpoints

https://auth.xbarry.ai/api/mcp/verifystreamable-http

What it can do

Tool inventory

Tools (2)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢request_verification_challenge(address, agent_id, chain)

Step 1 of wallet verification: get a fresh challenge for the user to sign. chain: "evm" or "solana". Pass agent_id (your marketplace identity) so the proof is bound to you. Present `challenge` to the user, have their wallet sign it (EVM personal_sign / Solana signMessage), then call verify_wallet_ownership with the returned `nonce` + signature. The challenge is single-use and expires (~10 min). Returns {challenge, nonce, expires_at}.

Input Schema

{
  "type": "object",
  "properties": {
    "address": {
      "title": "Address",
      "type": "string"
    },
    "agent_id": {
      "default": "",
      "title": "Agent Id",
      "type": "string"
    },
    "chain": {
      "default": "evm",
      "title": "Chain",
      "type": "string"
    }
  },
  "required": [
    "address"
  ],
  "title": "request_verification_challengeArguments"
}
🟢verify_wallet_ownership(address, signature, nonce, chain, agent_id)

Step 2 of wallet verification: prove control by signing the challenge from step 1. chain: "evm" (secp256k1, 0x-hex signature) or "solana" (ed25519, base58/base64/hex). `nonce` is from request_verification_challenge; the signature must be over that exact challenge text. Pass the same agent_id you requested the challenge with — on success the wallet is linked to you and you get a session_token to pass to Tachyo's other agents (e.g. check_token_safety) to unlock connected/premium tiers. Returns {verified, address, chain, linked, session_token?, session_expires?}. Does not move funds or expose keys.

Input Schema

{
  "type": "object",
  "properties": {
    "address": {
      "title": "Address",
      "type": "string"
    },
    "signature": {
      "title": "Signature",
      "type": "string"
    },
    "nonce": {
      "title": "Nonce",
      "type": "string"
    },
    "chain": {
      "default": "evm",
      "title": "Chain",
      "type": "string"
    },
    "agent_id": {
      "default": "",
      "title": "Agent Id",
      "type": "string"
    }
  },
  "required": [
    "address",
    "signature",
    "nonce"
  ],
  "title": "verify_wallet_ownershipArguments"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded2 tools
verifiedversion not recorded2 tools