veriql-mcp
Enables Bitcoin address risk checks before payment, including OFAC sanctions, Drain Watch, and freeze-related verdicts.
Enables token and wallet risk checks on BNB Chain, including risky approvals, honeypot/tax/mint/proxy flags, and launch-safety scoring.
Checks whether an address has been frozen by Circle using issuer contract data, contributing to payment and freeze-risk verdicts.
Enables Ethereum wallet approval scans, token risk checks, signature decoding, USDT send checks, and issuer freeze checks.
Enables Polygon wallet approval scans, token risk checks, signature decoding, and issuer freeze checks.
Enables Solana launch-safety and payee risk checks, including OFAC, Drain Watch, and freeze-related verdicts.
Checks Tether freeze status and USDT send risks on Tron and Ethereum, including frozen sender/recipient and Tether freeze-list data.
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., "@veriql-mcp check if this token is safe to buy: 0x6982508145454ce325ddbe47a25d4ec3d2311933"
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.
veriql-mcp
Crypto wallet and token risk checks as MCP tools, so an agent can ask "is this token safe to buy?" and get an answer with the math attached.
The checks are read-only: every signal comes from public on-chain data, and nothing you check is ever signed or moved. The only thing this server can sign is its own fee, and only if you give it a payment wallet (below): a USDC payment of $0.005 to $0.05 per call to Veriql, capped per call.
Install
Claude Desktop (claude_desktop_config.json), Claude Code, Cursor, or any MCP client:
{
"mcpServers": {
"veriql": {
"command": "npx",
"args": ["-y", "veriql-mcp"],
"env": { "VERIQL_WALLET_PRIVATE_KEY": "0x…" }
}
}
}Pay per call from a wallet, with no account and no key: put a little USDC on Base, Polygon, Arbitrum or Avalanche in a wallet used only for this (a few dollars is hundreds of calls) and give its private key as VERIQL_WALLET_PRIVATE_KEY. Each call pays over x402 and is refused before signing if it would cost more than VERIQL_MAX_USD_PER_CALL. Or use prepaid credits from veriql.app/api as VERIQL_API_KEY instead.
env | default | |
| EVM key of a dedicated payment wallet (USDC on Base, Polygon, Arbitrum or Avalanche) | |
|
| Refuse any single payment above this |
| Prepaid credits, instead of a wallet (a key wins if both are set) | |
|
| Point at another deployment |
Related MCP server: chainverdict
Tools
veriql_scan (address)
Risky token approvals for a public wallet across Ethereum, BNB Chain, Polygon, Arbitrum and Base. Returns a 0-100 Security Score with itemised drivers, every risky approval, and a best-effort USD value-at-risk.
veriql_token (address, chainId?)
Honeypot, punishing taxes, mintable supply, hidden owner and proxy risks, each as a plain-English flag. EVM chains plus Tron.
veriql_launch (address, chainId?)
A 0-100 launch-safety score with every penalty driver and the full metrics behind it. EVM chains plus Tron plus Solana.
veriql_payee (address)
Before you send money: OFAC sanctions, Drain Watch and a Tether or Circle freeze in one verdict, do_not_pay, no_known_risk or incomplete. Incomplete is not a clean result. EVM chains, Bitcoin, Solana and Tron.
veriql_signature (payload)
Before you sign: decodes an approve, Permit, Permit2, EIP-7702 delegation, transfer or revoke, checks who gains the power against OFAC and Drain Watch, and answers block, warn or allow. Anything it cannot decode is block.
veriql_send (from, to, amount?)
Before you send USDT on Tron or Ethereum, both questions in one call. Will it go through: a frozen sender, an unactivated Tron account, too little USDT, too little TRX or ETH for the fee, or a contract that refuses the transfer, read off the chain with the exact fee. Should it go there: the recipient checked against OFAC, Drain Watch and Tether's freeze list. Tether checks the sender, not the recipient, so USDT sent to a frozen address confirms and can never leave, and no simulation shows that. Answers do_not_send, will_fail, may_fail, goes_through or incomplete. Leave out amount to check the whole balance.
veriql_freeze (address)
Whether Tether or Circle froze an address, read off the issuer's contract, and whether it received USDT directly from an address Tether froze. EVM chains and Tron. Free, and needs no key.
Why the output is shaped like this
Agents are the worst possible audience for a bare number, because they cannot tell a measurement from a fallback. So:
Every score ships its drivers. You get the penalties and what each one is for, not just the total. The complete scoring methodology, every weight, is published at veriql.app/llms-full.txt.
An incomplete check says so. When a dimension could not be read, the result is marked incomplete and a clean verdict is withdrawn rather than reported at a capped number. A partial check that did find danger keeps the finding: incompleteness withdraws a clean verdict and never softens a dirty one.
Absence is never zero. A value nobody could establish comes back null. It is never substituted from another instrument, because borrowing a number across providers is how a tool reports a collapse that never happened.
Much of it is read from chain, not resold. Pool reserves (PumpSwap, Orca, Meteora), SPL mint authorities, transfer fees, permanent delegate, LP lock and holder concentration are our own reads, so a vendor outage degrades the answer honestly instead of silently.
Pay per call, with no account
The same endpoints speak x402: call with no key, get a 402 describing exactly what to pay, retry with the payment attached. USDC on Base, Solana, Polygon, Arbitrum or Avalanche, no signup and no human in the loop. Useful when an agent has a wallet but cannot complete a checkout.
Limits, stated plainly
A verdict is a structural risk assessment, not financial advice and not a prediction. It cannot tell you whether a price will go up. Holder concentration is an upper bound, because the largest token accounts can include AMM pool vaults and exchange wallets. A clean result means no known risks were found, which is not the same as safe.
MIT licensed. Built by the team behind Veriql.
Available Tools
11 toolsveriql_batch_screenVeriql batch address screenA
Screen up to 50 addresses in one call against OFAC SDN sanctions, Drain Watch and Tether and Circle freezes (EVM and Tron). For payout runs, token holder lists and sniper wallets. Each address gets do_not_pay, no_known_risk or incomplete; incomplete is not a clean result.
Inputs: addresses (required).
veriql_deployerVeriql token creator historyA
Who created this Solana pump.fun token (read from its bonding curve on chain) and what happened to that creator's other tokens Veriql scored: each one's verdict and any measured liquidity withdrawal or sell-off. History starts 2026-09-30; no record is unknown, never clean.
Inputs: address (required), limit.
veriql_freezeVeriql freeze checkA
Has Tether or Circle frozen this address, read straight off the issuer's contract, and did it receive USDT directly from an address Tether froze (exposure, not guilt). EVM and Tron. Free, no key needed.
Inputs: address (required).
veriql_launchVeriql launch-safety scoreB
A transparent 0-100 launch-safety score for a token/mint with itemised penalty drivers and full metrics. EVM chains + Tron + Solana.
Inputs: address (required), chainId.
veriql_payeeVeriql payee checkA
Before sending money to an address: is it OFAC-sanctioned, on Drain Watch, or frozen by Tether or Circle (funds sent there can never leave). Answers do_not_pay, no_known_risk or incomplete, and incomplete is not a clean result. EVM, Bitcoin, Solana, Tron.
Inputs: address (required).
veriql_preflightVeriql preflight (one call before send, swap or sign)A
Every check one transaction needs, in one call, on whatever you pass: the recipient screen (OFAC, Drain Watch, Tether and Circle freezes) on to, the USDT transfer simulation when from and to are both on Tron or both on Ethereum, the launch score on tokenAddress, and the signature decode on calldata or typedData. Answers ALLOW, WARN or BLOCK. BLOCK only on a fact that loses money; a low score alone is WARN.
Inputs: to, from, amount, chainId, +3 more.
veriql_scanVeriql wallet scanA
Scan a public wallet address for risky token approvals across 5 EVM chains (Ethereum, BNB Chain, Polygon, Arbitrum, Base). Returns a 0-100 Security Score with itemised drivers, every risky approval, and a best-effort USD value-at-risk.
Inputs: address (required).
veriql_sendVeriql USDT pre-send checkA
Before sending USDT on Tron or Ethereum: will this transfer go through (frozen sender, unactivated account, too little USDT, too little TRX or ETH for the fee, a contract that refuses it, read off the chain with the exact fee), and should it go there at all (recipient OFAC-sanctioned, on Drain Watch, or frozen by Tether, where USDT arrives and can never leave). Answers do_not_send, will_fail, may_fail, goes_through or incomplete, and incomplete is not a clean result.
Inputs: to (required), from (required), amount.
veriql_signatureVeriql signature checkA
Before signing: decodes an approve, Permit, Permit2, EIP-7702 delegation, transfer or revoke, checks who gains the power against OFAC and Drain Watch, and answers block, warn or allow. Anything it cannot decode is block.
Inputs: payload (required).
veriql_tokenVeriql token checkA
Check a token contract for honeypot, punishing taxes, mintable supply, hidden owner and proxy risks, each surfaced as a plain-English flag. EVM chains + Tron.
Inputs: address (required), chainId.
veriql_x402_seller_checkVeriql x402 seller checkA
Before paying an x402 endpoint: reads its 402 (version, networks, testnet or not, the real price when the asset is USDC) and screens every wallet it asks to be paid at against OFAC, Drain Watch and Tether and Circle freezes. Answers GO, CAUTION or STOP. GO does not mean the seller delivers.
Inputs: url, payTo.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Most tools target distinct checks, but veriql_preflight explicitly re-implements veriql_payee, veriql_send, veriql_launch and veriql_signature in a single call, leaving genuine ambiguity about when to use the composite versus the components. veriql_launch vs veriql_token (both score token safety) and veriql_freeze vs the freeze screening inside veriql_payee/veriql_batch_screen also overlap. Detailed descriptions mitigate this but boundaries are not crisp.
All tools use a consistent veriql_ prefix followed by a single short noun or noun phrase (scan, token, launch, payee, send, signature, freeze), which is predictable. The exception is veriql_x402_seller_check, a three-word outlier, and the set mixes noun names with verb-ish names, but overall it reads as one coherent family.
11 tools is squarely in the well-scoped range for a crypto safety screening server, and each tool covers a recognizably different surface (approvals, token risk, launch, recipient, transfer, signature, batch, x402, deployer history, freeze). No padding is apparent given the breadth of chains and pre-transaction checks.
The pre-transaction safety lifecycle is well covered from multiple entry points (single, batch, aggregator, x402), plus a freeze oracle and deployer history. The main gap is remediation: veriql_scan surfaces risky approvals but no tool builds or simulates a revoke transaction, and NFT/collection screening and Solana transfer simulation are absent, though agents can partially work around these.
Maintenance
Related MCP Connectors
Smart-contract risk reports for AI agents on 20 EVM chains, paid per call via x402 ($0.02 USDC).
Pre-transaction token risk checks for autonomous agents on six chains. Read-only; paid via x402.
Pre-trade token safety checks for AI agents on Solana and Base. x402 USDC per call, no key.
Pre-trade token risk scoring API for Base tokens, paid via x402.
Related MCP Servers
- FlicenseNot gradedqualityFmaintenanceProvides counterparty risk checks for any EVM address, returning malicious-history flags, tiered risk scoring, and plain-language summaries via x402 payment.-
- AlicenseNot gradedqualityBmaintenancePay-per-call checks an AI agent runs before it moves money: token safety verdicts and wallet risk profiles on Base, on-chain payment verification, IBAN/VAT/BIC/LEI/ISIN validation, and live TLS and email-spoofing posture for a domain. Paid in USDC over x402 with no API key or account; the free payment_info tool explains the pricing.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to check an EVM address on Base for risk (safe, caution, danger) before sending funds, with reasons, paid per call via x402 from the user's own wallet.794 npm1MIT
- AlicenseAqualityCmaintenanceEnables agents to run pre-signature security checks: identifying who can replace a Solana program's code or control an EVM contract's upgrades, surfacing dependency advisories for lockfiles, scanning public repos before release, and setting 30-day signed-webhook alerts on changes. Calls are paid per use in USDC over x402 from a wallet with per-call caps and a session budget.853 npmMIT