All servers · Crypto & blockchain
ai.tachyo/verify
ai.tachyo/verify · v1.0.0
No registry update 90+ days
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | experimental, prompts, resources, tools |
| Tool definitions | 2 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
Cryptographic proof of wallet ownership in two steps, with no keys and no custody.
Connect
streamable-http · https://auth.xbarry.ai/api/mcp/verify
claude mcp add --transport http verify https://auth.xbarry.ai/api/mcp/verify{
"mcpServers": {
"verify": {
"url": "https://auth.xbarry.ai/api/mcp/verify"
}
}
}Tools as reported by the server
request_verification_challengeStep 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_owverify_wallet_ownershipStep 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 req
JSON · Text for agents · Registry updated 2026-06-20