zkVerify
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@zkVerify Verify the balance of 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on Ethereum"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
zkVerify
Trustless blockchain verification over x402 with Merkle proofs + ECDSA signing
Why?
When an AI agent pays for blockchain data via x402, how does it know the data is authentic? It doesn't. 99% of x402 transactions are at risk (arXiv, July 2026 — 31 vulnerabilities found).
zkVerify solves this: every API response includes a Merkle proof + ECDSA signature. The agent can verify independently — zero trust required.
Related MCP server: Tilde x402 MCP Server
Endpoints
Endpoint | Price | Returns |
| $0.02 | Account balance + Merkle proof + signature |
| $0.02 | Contract code hash + signature |
| Free | Service status + signer address |
| Free | x402 discovery (Bazaar) |
Supported Chains
Base (L2 — fallback to eth_getBalance)
Ethereum (L1 — full eth_getProof / EIP-1186)
Polygon
How It Works
Agent sends
GET /verify/balance/0xABC...?chain=ethereumzkVerify returns HTTP 402 Payment Required
Agent pays $0.02 USDC on Base via x402
zkVerify: a. Fetches
eth_getProoffrom RPC b. Verifies Merkle Patricia Proof against stateRoot c. Signs the result with ECDSA d. Returns:{ balance, blockNumber, stateRoot, merkleProof, signature }Agent verifies: a. Signature (recoverAddress) b. Merkle proof locally (optional) c. stateRoot against block header (optional)
Agent now has 100% verified on-chain data — no trust needed
Quick Start
For AI Agents (via x402)
curl https://zkverify-production.up.railway.app/verify/balance/0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045?chain=ethereum
# Returns: balance, Merkle proof (9 nodes), ECDSA signature, verified: trueSDK (Client-side verification)
import { fullVerify } from "zkverify";
const result = await fetch("https://zkverify-production.up.railway.app/verify/balance/0xABC...?chain=ethereum").then(r => r.json());
console.log(result.fullyVerified); // true = verified 100%MCP Server
zkVerify includes an MCP server with 3 tools for Claude/Cursor:
{
"mcpServers": {
"zkverify": {
"command": "npx",
"args": ["-y", "zkverify-mcp"],
"env": {
"ZKVERIFY_URL": "https://zkverify-production.up.railway.app"
}
}
}
}Architecture
Merkle Patricia Proof: EIP-1186
eth_getProoffrom Ethereum L1ECDSA Signing: Every response signed with secp256k1
x402 Payment: $0.02 USDC on Base
Zero Trust: Agent needs no trusted oracle — just math
Costs
$0 startup cost
Free RPC (PublicNode, Alchemy free tier)
x402 facilitator: free for first 1,000 transactions/day
Margin: 99% (after $0.001 facilitator fee)
Patent (Pending)
Title: "System and method for providing cryptographically verifiable API responses using Merkle proofs and ECDSA signatures over HTTP payment protocols"
See patent/USPTO_PROVISIONAL.md
ZK Circuit (Level 2)
A simplified circom circuit (~202 constraints) proves that verification was performed correctly without revealing proof data.
License
MIT — free to use, modify, and distribute. Attribution appreciated.
Links
Built with ZKForge — the first x402 service providing cryptographically verifiable blockchain data.
Available Tools
3 toolsverify_balanceA
Verify any blockchain address balance with Merkle proof and ECDSA signature. Returns cryptographically verified balance data.
Inputs: address (required), chain.
verify_contractB
Verify if an address is a smart contract and get its code hash with ECDSA signature.
Inputs: address (required), chain.
verify_signatureA
Verify a zkVerify ECDSA signature on a previous response. Checks signer authenticity.
Inputs: response (required), expectedSigner (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool targets a distinct object: contract, signature, and balance. There is no ambiguity about which tool to use for a given verification task.
All tool names follow a consistent 'verify_' prefix followed by the object being verified. This creates a predictable pattern that is easy for agents to learn and recall.
Three tools is a well-scoped count for a specialized verification server. Each tool serves a clear purpose, and the set is neither too sparse nor bloated.
The server covers the core verification actions for contracts, signatures, and balances, which covers the most common needs. A minor gap is lack of transaction or proof verification, but the current surface is coherent and functional.
Related MCP Connectors
Pay-per-use weather, environment, finance, and on-chain intelligence tools for AI agents via x402.
Verifiable execution records for AI agents: signed receipts, tamper-evident archives and portable evidence bundles, exposed via MCP and REST, with paid verify and anchor calls settled over x402.
Verifiable crypto signals, recorded history and always-on monitoring for AI agents via x402 on Base.
AI agent gateway with web fetching, data extraction, crypto pricing, and x402 payments
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to access paid content by integrating cryptocurrency payments through the x402 protocol, allowing LLMs to verify payments and retrieve paid resources automatically.1-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to discover and pay for x402-enabled services using natural language, with multi-chain support for Solana and EVM payments.34 npm1MIT
- AlicenseAqualityDmaintenanceEnables AI agents to access crypto/web3 data across 5 chains with pay-per-call billing in USDC via x402, no API key required, and built-in spend caps.3664 npmMIT

EVIDIQ Notary MCPofficial
AlicenseNot gradedqualityBmaintenanceCryptographic receipt layer for AI inferences. Enables notarization and verification of AI outputs with on-chain proofs via x402 payment.1MIT