Cryptographic proof of wallet ownership in two steps, with no keys and no custody.
| Endpoint | https://auth.xbarry.ai/api/mcp/verify (streamable-http) |
|---|---|
| Registry version | 1.0.0 |
| Now | 2 tools · grade A (100) · pin ts_f7156b3dd2c74786f099b2999d5e2cc5 · protocol 2025-06-18 |
| First / last listed | 2026-10-27 01:15 UTC / 2026-10-27 01:15 UTC |
| Grade over time | 2026-10-27: A (100), 2 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: request_verification_challenge verify_wallet_ownership
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 expi params: address*, agent_id, chain |
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
se params: address*, signature*, nonce*, chain, agent_id |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.