# verify MCP server

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

## Links
- Registry page: https://www.getdrio.com/mcp/ai-tachyo-verify

## Install
- Endpoint: https://auth.xbarry.ai/api/mcp/verify
- Auth: Not captured

## Setup notes
- Remote endpoint: https://auth.xbarry.ai/api/mcp/verify

## Tools
- 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}.
     Endpoint: https://auth.xbarry.ai/api/mcp/verify
- 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.
     Endpoint: https://auth.xbarry.ai/api/mcp/verify

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: ai.tachyo
- Version: 1.0.0
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Jun 20, 2026
- Source: https://registry.modelcontextprotocol.io