Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Chain Check (x402)

REMOTE · CHAINCHECK-API.NETLIFY.APP

x402-paid on-chain tools: wallet report, contract scan, token risk, gas, address labels (USDC/Base)

65 Trust /100

Last scanned (1 hour ago)

Scores higher than 45% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 550 tokens (~91/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 73% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 3 Nov 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://chaincheck-api.netlify.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.netlify.app,O=Netlify\, Inc,L=San Francisco,ST=California,C=US CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US 16 Feb 2026 19 Mar 2027 ECDSA 256 SHA256-RSA cd5d0afb0611b5bd9d692535c0ca7c4
SANs: *.netlify.app, netlify.app
CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 30 Mar 2021 29 Mar 2031 RSA 2048 SHA256-RSA cf5bd062b5602f47ab8502c23ccf066

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of chaincheck-api.netlify.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
netlify.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://chaincheck-api.netlify.app/mcp Verified 200
http (plaintext) http://chaincheck-api.netlify.app/mcp HTTPS enforced 301 https://chaincheck-api.netlify.app/mcp
MCP tools · 6 exposed · ~510 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
address_label ~85

ENS <-> address resolution and malicious-address flags (phishing, scam, sanctions, mixer). Paid $0.01 USDC on Base via x402.

NameTypeReqDescription
qstringyesaddress or ENS name
x402_paymentstring–Optional x402 v2 payment payload (value of PAYMENT-SIGNATURE header, base64). Omit to receive payment terms.

No output schema declared.

No examples provided.

contract_scan ~111

Smart-contract risk scan: proxy/admin, owner, mint, blacklist, pause, fee-change, trading toggle flags. Paid $0.02 USDC on Base via x402.

NameTypeReqDescription
addressstringyes–
chainstringyesethereum|base|arbitrum|optimism|polygon|bsc|avalanche
x402_paymentstring–Optional x402 v2 payment payload (value of PAYMENT-SIGNATURE header, base64). Omit to receive payment terms.

No output schema declared.

No examples provided.

gas_snapshot ~74

Live gas on 7 EVM chains with USD cost of transfer/swap and cheapest chain. Paid $0.005 USDC on Base via x402.

NameTypeReqDescription
x402_paymentstring–Optional x402 v2 payment payload (value of PAYMENT-SIGNATURE header, base64). Omit to receive payment terms.

No output schema declared.

No examples provided.

pricing ~28

Free. Lists Chain Check tools, prices and how to pay (x402, USDC on Base).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

token_risk ~119

ERC-20 token risk score 0-100 (honeypot, taxes, mint, hidden owner, blacklist, LP lock, top holders). Paid $0.02 USDC on Base via x402.

NameTypeReqDescription
addressstringyes–
chainstringyesethereum|base|arbitrum|optimism|polygon|bsc|avalanche
x402_paymentstring–Optional x402 v2 payment payload (value of PAYMENT-SIGNATURE header, base64). Omit to receive payment terms.

No output schema declared.

No examples provided.

wallet_report ~93

Multi-chain EVM wallet report (7 chains): native/USDC/USDT balances, tx counts, contract + EIP-7702 detection. Paid $0.01 USDC on Base via x402.

NameTypeReqDescription
addressstringyes–
x402_paymentstring–Optional x402 v2 payment payload (value of PAYMENT-SIGNATURE header, base64). Omit to receive payment terms.

No output schema declared.

No examples provided.

Install

How do I install the Chain Check (x402) MCP server?

Chain Check (x402) is a hosted endpoint at https://chaincheck-api.netlify.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · chaincheck-api.netlify.app

# add to Claude Code
claude mcp add --transport http app-netlify-chaincheck-api-chaincheck 'https://chaincheck-api.netlify.app/mcp'
Common questions

What is the Chain Check (x402) MCP server?

Chain Check (x402) is an MCP server listed in the public MCP registry as app.netlify.chaincheck-api/chaincheck. x402-paid on-chain tools: wallet report, contract scan, token risk, gas, address labels (USDC/Base). This page covers its hosted endpoint (https://chaincheck-api.netlify.app/mcp).

Is the Chain Check (x402) MCP server safe to use?

Chain Check (x402) scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Chain Check (x402) MCP server expose?

Chain Check (x402) exposes 6 tools: wallet_report, contract_scan, token_risk, gas_snapshot, address_label, pricing. Their descriptions and schemas cost roughly 510 tokens of context every time the server is loaded.

Does the Chain Check (x402) MCP server require authentication?

No. We connected to Chain Check (x402) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Chain Check (x402) MCP server still maintained?

Chain Check (x402) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.