Home / MCP registry index / io.github.digitalweb33333-creator/x402-endpoints

io.github.digitalweb33333-creator/x402-endpoints

io.github.digitalweb33333-creator/x402-endpoints in the official MCP registry. Endpoint https://x402-endpoints.onrender.com/mcp/. Source: github.com/digitalweb33333-creator/x402-endpoints.

The registry describes it as: x402 paid API tools for AI agents on Base: EU/global registries, crypto, wallet & agent trust.

We read its 52 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

gleif_lei vies_vat polymarket_odds flights_states ev_charging bodacc_annonces ted_tenders eurlex_search sanctions_screen cve_lookup recalls_search drug_label osm_building_footprint climate_risk_score polymarket_resolution solar_building_insights uk_companies_search patents_search fr_sirene_lookup iban_validate fr_legifrance_search ecb_exchange_rate crypto_token_safety crypto_derivatives_radar crypto_wallet_xray crypto_dex_cex_spread web_extract crypto_new_pairs x402_seller_trust x402_payment_firewall compliance_wallet_screen macro_snapshot solana_token_safety solana_pre_trade crypto_signal_fusion agent_due_diligence agent_analysis_report agent_clearance agent_output_qa agent_content_scan crypto_pre_trade_verdict agent_ledger proof_notarize crypto_token_dossier market_intel crypto_wallet_forensics chain_events x402_seller_audit agent_clearance_packet agent_visibility_audit agent_rank_check agent_passport

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-digitalweb33333-creator-x402-endpoints/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-digitalweb33333-creator-x402-endpoints)

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

The Stall
ai.intuitek.the-stall/the-stall
200 tools, nothing matched
2026-10-22
SAP MCP Server
ai.oobeprotocol.sap.mcp/sap-mcp
200 tools, nothing matched
2026-10-22
ScorpTech x402 API
com.it.scorptech/x402
200 tools, nothing matched
2026-10-26
Apex Edge — x402-paid machine services
dev.pages.nonsynthetic/apex-edge
200 tools, nothing matched
2026-10-23
uk.minia2a/minia2a-mcp-remote
uk.minia2a/minia2a-mcp-remote
200 tools, nothing matched
2026-10-21
AI 代理人任務中樞
dev.workers.panda198271.agent-hub-tw/agent-hub
174 tools, nothing matched
2026-10-22