Verify

ai.tachyo/verify

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

healthy

status

tools exposed

1604ms

connect latency

698e029dc07a

schema fingerprint

Tools (2)

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 ver

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 age

Endpoint

https://auth.xbarry.ai/api/mcp/verify
Category: Other · Last checked: 2026-08-15T08:51:28Z

Monitor your own MCP server

Get alerted the moment yours goes down, a tool schema drifts, or an upstream silently breaks.

Get early access

How we measure →

What this means. This server responded to the MCP handshake and listed its tools without authentication. The schema fingerprint lets us flag if tool signatures silently change (schema drift) between checks.