verify

ai.tachyo/verifyVersion 1.0.0

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

Status

Responds157 msNov 14, 2026, 13:34 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 13:34 UTC
Latency: 157 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://auth.xbarry.ai/api/mcp/verifyResponds157 msNov 14, 2026, 13:34 UTC

No sign-in

Claude Code

claude mcp add --transport http verify https://auth.xbarry.ai/api/mcp/verify

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: verify
Remote MCP server URL: https://auth.xbarry.ai/api/mcp/verify

Cursor

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

VS Code

code --add-mcp '{"name":"verify","type":"http","url":"https://auth.xbarry.ai/api/mcp/verify"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

2 tools

Tools of verify
	Description		Read-only	Idempotent	Open world
`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}.	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}.	Not declared	Not declared	Not declared	Not declared
`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.	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.	Not declared	Not declared	Not declared	Not declared

Details

Registry status: Active
Published: Jun 20, 2026
Updated: Jun 20, 2026
Website: Not given
Repository: Not given
Categories (suggested): SecuritySuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing