ai.tachyo/verify

Official2 toolsLive

by tachyo

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

MCP Server: ai.tachyo/verify

The ai.tachyo/verify MCP server provides a workflow for cryptographic proof of wallet ownership in two steps. It is designed for no keys and no custody, focusing on verifying ownership without the server holding sensitive key material.

🛠️ Key Features

Cryptographic proof of wallet ownership
Two-step verification process
No keys
No custody

🚀 Use Cases

Verifying wallet ownership through a cryptographic challenge flow
Integrating wallet verification where key custody must be avoided

⚡ Developer Benefits

Uses a two-step process for ownership proof
Avoids key management by not requiring keys
Avoids custody by not storing or holding assets/keys

⚠️ Limitations

Tool count is limited to 2 tools, based on available metadata

Captured live from the server via tools/list.

request_verification_challenge

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}.

Parameters3

address	string	required
agent_id	string	optional
chain	string	optional

Raw 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

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.

Parameters5

address	string	required
signature	string	required
nonce	string	required
chain	string	optional
agent_id	string	optional

Raw 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"
}

Install

Tools (2)

request_verification_challengeverify_wallet_ownership

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://auth.xbarry.ai/api/mcp/verify

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "verify": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://auth.xbarry.ai/api/mcp/verify"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.