Home / MCP registry index / io.github.xzntexe/yruz-x402

YRUZ x402 tools

io.github.xzntexe/yruz-x402 in the official MCP registry. Endpoint https://yruz.one/mcp/x402. Source: github.com/xzntexe/yruz-x402.

The registry describes it as: Pay-per-call x402 tools: package advisories, EU tenders, Wikidata facts, promo board, web, crypto

Connect it

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

claude mcp add --transport http yruz-x402 https://yruz.one/mcp/x402

{
  "mcpServers": {
    "yruz-x402": {
      "url": "https://yruz.one/mcp/x402"
    }
  }
}

code --add-mcp '{"name":"yruz-x402","type":"http","url":"https://yruz.one/mcp/x402"}'

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.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

site_audit web_extract company_enrich url_safety_check domain_intel weather_forecast link_preview broken_links x402_endpoint_check uptime_check wallet_balance crypto_price crypto_trending solana_token_check solana_portfolio solana_tx_explain network_fees deps_get_package deps_get_version_history deps_compare_releases deps_check_advisories deps_batch_check deps_get_dependency_tree deps_audit_project deps_get_advisory deps_get_changes deps_monitor_check tenders_search tenders_get_notice tenders_get_history tenders_get_deadlines tenders_get_awards tenders_get_authority tenders_get_supplier_history tenders_get_changes tenders_monitor_check reality_search reality_get_entity reality_get_history reality_compare reality_resolve_entity reality_get_evidence reality_get_conflicts reality_monitor_check promo_create_listing promo_renew_listing promo_takeover_top_spot get_example promo_search_listings promo_get_featured promo_get_leaderboard promo_get_listing promo_get_pricing promo_get_campaign_history yruz_list_services yruz_get_source_status

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): 3aa154bda5c191d3. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

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-xzntexe-yruz-x402/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-xzntexe-yruz-x402)

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