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.

io.github.89rat/code402-verify-mcp

REMOTE · VERIFY.CODE402.DEV

Verify code402 XDR-1 receipts: keccak digest + secp256k1 signer recovery. Free, stateless.

+3 this week 73 Trust /100

Last scanned (1 hour ago)

Scores higher than 60% 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 Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1240 tokens (~68/item across 18 items; 18 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 18 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

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 24 Oct 26 67

    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://verify.code402.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=code402.dev CN=WE1,O=Google Trust Services,C=US 22 Sept 2026 21 Dec 2026 ECDSA 256 ECDSA-SHA256 a298a44302fdbbf313012e80df7e040a
SANs: code402.dev, verify.code402.dev, *.verify.code402.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of verify.code402.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
code402.dev. 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=15552000
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://verify.code402.dev/mcp Verified 200
http (plaintext) http://verify.code402.dev/mcp HTTPS enforced 301 https://verify.code402.dev/mcp
MCP tools · 18 exposed · ~1,240 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
bundle_verify ~127

Paid ($0.0029–$0.50). Multi-gate compliance bundle: run any combination of IBAN validation, sanctions screening, and EVM address validation in a single call. Returns all gate results + XDR-1 signed receipt. Tier auto-detected from field count.

NameTypeReqDescription
ibanstring–IBAN to validate
onchain_addressstring–EVM address to validate
sanctionsobject–Sanctions screening: { addresses: string[], names: string[] }
tierstring–Pricing tier (auto-detected if omitted)

No output schema declared.

No examples provided.

chain_balance ~46

Paid ($0.0029). Get native ETH balance of any Ethereum address. Returns balance in wei and ETH.

NameTypeReqDescription
addressstringyes0x-prefixed EVM address

No output schema declared.

No examples provided.

chain_block_number ~31

Paid ($0.0029). Get the latest Ethereum mainnet block number. Returns block height and timestamp.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

chain_code ~61

Paid ($0.0029). Get the deployed bytecode at an address. Returns hex bytecode (empty = EOA, non-empty = contract). Useful for distinguishing contracts from wallets.

NameTypeReqDescription
addressstringyes0x-prefixed EVM address

No output schema declared.

No examples provided.

chain_ens_resolve ~48

Paid ($0.008). Resolve a .eth ENS name to its Ethereum address via the universal resolver.

NameTypeReqDescription
namestringyesENS name (e.g. vitalik.eth)

No output schema declared.

No examples provided.

chain_erc20_balance ~69

Paid ($0.0029). Get ERC-20 token balance via balanceOf. Returns balance in raw and human-readable form.

NameTypeReqDescription
addressstringyes0x-prefixed wallet address
tokenstringyes0x-prefixed ERC-20 token contract address

No output schema declared.

No examples provided.

chain_gas_price ~48

Paid ($0.0029). Get the current Ethereum mainnet gas price. Returns base fee, priority fee, and max fee in wei and gwei. Useful for estimating transaction costs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

chain_nonce ~40

Paid ($0.0029). Get the next transaction nonce for an Ethereum address.

NameTypeReqDescription
addressstringyes0x-prefixed EVM address

No output schema declared.

No examples provided.

chain_tx ~54

Paid ($0.008). Get Ethereum transaction details by hash. Returns from, to, value, gas used, status, block info.

NameTypeReqDescription
hashstringyes0x-prefixed 64-hex transaction hash

No output schema declared.

No examples provided.

chain_tx_receipt ~59

Paid ($0.008). Get the receipt of a confirmed transaction. Returns status (success/fail), gas used, logs, contract address if deployment.

NameTypeReqDescription
hashstringyes0x-prefixed 64-hex transaction hash

No output schema declared.

No examples provided.

iban_check ~81

Paid ($0.0029). Validate an IBAN: ISO 13616 structure, country registration, length, MOD 97-10 checksum. Returns pass/fail with all checks and issues. Covers 50 countries.

NameTypeReqDescription
ibanstringyesIBAN to validate (e.g. GB29NWBK60161331926819, spaces allowed)

No output schema declared.

No examples provided.

lei_check ~82

Paid ($0.0029). Validate a Legal Entity Identifier (LEI, ISO 17442). Checks 20-char alphanumeric format and Mod 97-10 check character. Verified via Rust WASM engine.

NameTypeReqDescription
leistringyes20-character LEI (e.g. 5493001KJTIIGC8Y1R12)

No output schema declared.

No examples provided.

luhn_check ~73

Paid ($0.0029). Validate a payment card or account number using the Luhn algorithm (ISO/IEC 7812-1). Checks numeric format and Mod-10 checksum. Verified via Rust WASM engine.

NameTypeReqDescription
numberstringyesCard or account number (12-19 digits, spaces allowed)

No output schema declared.

No examples provided.

mod97_check ~83

Paid ($0.0029). Calculate ISO 7064 Mod 97-10 remainder for any alphanumeric string. Returns the remainder (0-96, valid=1). Used for IBAN, LEI, and custom identifier validation. Verified via Rust WASM engine.

NameTypeReqDescription
inputstringyesAlphanumeric string to compute Mod 97-10 on

No output schema declared.

No examples provided.

onchain_address_check ~90

Paid ($0.0029). Validate an EVM address format and EIP-55 mixed-case checksum. Returns valid/invalid with normalization and checksum status.

NameTypeReqDescription
addressstringyes0x-prefixed EVM address to validate (e.g. 0x742d35Cc6634C0532925a3b844Bc9e7595f2bD18)

No output schema declared.

No examples provided.

price_lookup ~86

Look up pricing for any code402 tool (free). Returns current x402 pricing tiers, accepted networks, and tool availability. Use tool_name for named lookups or url for URL-based lookups.

NameTypeReqDescription
tool_namestring–Tool name (e.g. iban_check, bundle_verify, chain_block_number)
urlstring–Full endpoint URL to look up pricing for

No output schema declared.

No examples provided.

sanctions_check ~77

Paid ($0.0029). Screen Ethereum addresses and entity names against OFAC/UN/EU sanctions lists. Returns clear/hit with matched entries. Supports both EVM addresses and human-readable names.

NameTypeReqDescription
addressesarray–EVM addresses to screen (0x-prefixed)
namesarray–Entity names to screen

No output schema declared.

No examples provided.

x402_verify ~85

Verify one or more XDR-1 signed receipts offline (free). Returns valid/invalid per receipt with signer recovery, declared signer comparison, and integrity digest. Supply raw_receipt as JSON string or array for batch.

NameTypeReqDescription
raw_receiptstringyesFull signed receipt JSON (single object or JSON array for batch)
settlement_assetstring–Default USDC

No output schema declared.

No examples provided.

Install

How do I install the io.github.89rat/code402-verify-mcp server?

io.github.89rat/code402-verify-mcp is a hosted endpoint at https://verify.code402.dev/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 · verify.code402.dev

# add to Claude Code
claude mcp add --transport http 89rat-code402-verify-mcp 'https://verify.code402.dev/mcp'
Common questions

What is the io.github.89rat/code402-verify-mcp server?

io.github.89rat/code402-verify-mcp is listed in the public MCP registry as io.github.89rat/code402-verify-mcp. Verify code402 XDR-1 receipts: keccak digest + secp256k1 signer recovery. Free, stateless. This page covers its hosted endpoint (https://verify.code402.dev/mcp).

Is the io.github.89rat/code402-verify-mcp server safe to use?

io.github.89rat/code402-verify-mcp scores 73 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 io.github.89rat/code402-verify-mcp server expose?

io.github.89rat/code402-verify-mcp exposes 18 tools: x402_verify, price_lookup, iban_check, sanctions_check, onchain_address_check, and 13 more. Their descriptions and schemas cost roughly 1,240 tokens of context every time the server is loaded.

Does the io.github.89rat/code402-verify-mcp server require authentication?

No. We connected to io.github.89rat/code402-verify-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.89rat/code402-verify-mcp server still maintained?

io.github.89rat/code402-verify-mcp 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.