ZBS Index What actually exists in applied AI, with the source next to it

mcp server

verify

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

Description as published by the maintainer. Source

  • version 1.0.0
  • active

active — Registry entry last updated 2026-06-20.

What this server can do

2 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.

request_verification_challenge(chain, address, agent_id)
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}. Required: address.
verify_wallet_ownership(chain, nonce, address, agent_id, signature)
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. Required: address, signature, nonce.

Last successful function declaration observed on . Source: https://auth.xbarry.ai/api/mcp/verify. We list what the server declared; we do not call any of these functions.

Endpoint status observed on . Source: https://auth.xbarry.ai/api/mcp/verify.

Signals

These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.

Signal Value What it measures Window Observed Source
Latest published version 1.0.0 Latest version string the maintainer published to the registry. as of fetch Model Context Protocol
Registry record last updated 2026-06-20 When the registry record was last updated by its maintainer. point in time Model Context Protocol
First listed in the MCP Registry 2026-06-20 Date this server was first published to the official MCP Registry. Not a usage or quality measure. point in time Model Context Protocol
mcp tools declared 2 tools Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. as of probe auth.xbarry.ai
mcp endpoint status ok The server listed 2 functions when asked. as of probe auth.xbarry.ai

Where to get it

This record as data

Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.

GET /api/v1/entries/mcp_server.json

Sources

  1. Tools declared by the MCP server at https://auth.xbarry.ai/api/mcp/verify — auth.xbarry.ai, observed , trust tier 1.
  2. Official MCP Registry — Model Context Protocol, observed , trust tier 1.