mcpbeat Sign in

Verify MCP Server

by tachyo Your server? Claim it
answering

Verify is answering right now. Last checked 14 min ago. It exposes 2 tools.

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

Uptime history 47 days of history
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
295 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Verify every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add verify --transport http https://auth.xbarry.ai/api/mcp/verify
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "verify": {
      "url": "https://auth.xbarry.ai/api/mcp/verify"
    }
  }
}
~/.codex/config.toml
[mcp_servers.verify]
url = "https://auth.xbarry.ai/api/mcp/verify"
.cursor/mcp.json
{
  "mcpServers": {
    "verify": {
      "url": "https://auth.xbarry.ai/api/mcp/verify"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "verify": {
      "url": "https://auth.xbarry.ai/api/mcp/verify"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

request
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}.
verify
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.

Endpoints

URLTransportStateLatencyChecked
https://auth.xbarry.ai/api/mcp/verify streamable-http answering 191 ms 14 min ago

Alternatives to Verify

same job, measured the same way
ProofX - Content Protection for Creators
by razashariff

Protect and verify digital content with cryptographic signing and proof of ownership.

6 tools answering
Realopengroup
by realopengroup

Verify crypto wallets and generate proof of funds letters for buying real estate with crypto.

21 tools answering
Forcedreamai
by forcedreamai

Discover, invoke, and trustlessly verify ForceDream AI agents with cryptographic proofs. 17 tools.

128 installs/wk 21 tools answering
Hive Oracle
by srotzin

Agent-native price and event oracle with cryptographic source attestation

4 tools answering
ZeroKnowledge-Vault
by evozim

Zero-knowledge proof validator and cryptographic locker.

answering
Zkverify
by zkarchitect

Cryptographically verifiable blockchain data with Merkle proofs + ECDSA signing.

31 installs/wk local only
Hilt PayMe
by hilt

Wallet-approved SOL and Solana USDC payments to verified X handles, with zero custody.

answering
Peage MCP
by intrane

Give your agent a prepaid fiat wallet: pay any API per call in cents, no crypto, spend caps.

local only

Verify — questions

Answers built from our own checks of this server.

What can Verify do?
It exposes 2 tools, read directly from the server on our last check. Among them: request_verification_challenge, verify_wallet_ownership. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Verify working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 295 ms. The bar chart above shows every period we have measured.
How do I connect Verify?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Verify need an API key?
No. Verify completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Verify?
It answers our handshake in 295 ms on average, which is faster than 51% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.