Home / MCP registry index / io.github.89rat/x402-checks

io.github.89rat/x402-checks

io.github.89rat/x402-checks in the official MCP registry. Endpoint https://api.code402.dev/mcp. Source: github.com/89rat/m2m-exchange.

The registry describes it as: Machine-payable deterministic identifier checks + signed XDR-1 receipts for agents.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http x402-checks https://api.code402.dev/mcp

{
  "mcpServers": {
    "x402-checks": {
      "url": "https://api.code402.dev/mcp"
    }
  }
}

code --add-mcp '{"name":"x402-checks","type":"http","url":"https://api.code402.dev/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

crypto_ticker erc20_balance fx_spot_price_oracle block_info tx_activity token_contract_risk clean_markdown_scraper context_distill instant_json_schema_verifier balance_check calculate_fx_savings iban_check lei_check vat_mod97_check swift_bic_check batch_validate vendor_onboarding_pack india_supplier_check pre_disbursement_guard gstin_check ifsc_check sanctions_address_screen company_number_format aba_routing_check ein_format_check abn_check e164_check sedol_check isin_check ean13_check cnpj_check uscc_check japan_corp_check kra_pin_check rfc_check iso4217_currency_check upi_vpa_check pan_format_check uae_trn_check china_supplier_check japan_supplier_check latam_supplier_check gulf_supplier_check africa_supplier_check rent_deposit_guard rental_listing_risk rental_verdict reconcile create_b2b_invoice get_b2b_invoice simulate_spend_sentinel aci_trust_lookup csp_commitment_create iso20022_validate iso20022_to_x402_intent check_price receipt_verify

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-89rat-x402-checks/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-89rat-x402-checks)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers