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.

YRUZ x402 tools

REMOTE · YRUZ.ONE

Pay-per-call x402 tools: package advisories, EU tenders, Wikidata facts, promo board, web, crypto

Available components

+4 this week 78 Trust /100

Last scanned (45 minutes ago)

Scores higher than 76% 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 Security83
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 12740 tokens (~227/item across 56 items; 56 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 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 56 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 57 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.

  • 5 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.

  • 3 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.

  • 1 Nov 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.

  • 30 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.

  • 28 Oct 26 +1
    • “promo_create_listing” reworded the description of “url” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 27 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “broken_links” rewrote its description, which is the text the model reads security
    • Tool “company_enrich” rewrote its description, which is the text the model reads security
    • Tool “crypto_price” rewrote its description, which is the text the model reads security
    • Tool “crypto_trending” rewrote its description, which is the text the model reads security
    • Tool “domain_intel” rewrote its description, which is the text the model reads security
    • Tool “get_example” rewrote its description, which is the text the model reads security
    • Tool “link_preview” rewrote its description, which is the text the model reads security
    • Tool “network_fees” rewrote its description, which is the text the model reads security
    • Tool “site_audit” rewrote its description, which is the text the model reads security
    • Tool “solana_portfolio” rewrote its description, which is the text the model reads security
    • Tool “solana_token_check” rewrote its description, which is the text the model reads security
    • Tool “solana_tx_explain” rewrote its description, which is the text the model reads security
    • Tool “uptime_check” rewrote its description, which is the text the model reads security
    • Tool “url_safety_check” rewrote its description, which is the text the model reads security
    • Tool “wallet_balance” rewrote its description, which is the text the model reads security
    • Tool “weather_forecast” rewrote its description, which is the text the model reads security
    • Tool “web_extract” rewrote its description, which is the text the model reads security
    • Tool “x402_endpoint_check” rewrote its description, which is the text the model reads security
    • Schema quality: 3990 → 12719 ▼ functional
    • New tool “deps_audit_project” functional
    • New tool “deps_batch_check” functional
    • New tool “deps_check_advisories” functional
    • New tool “deps_compare_releases” functional
    • New tool “deps_get_advisory” functional
    • New tool “deps_get_changes” functional
    • New tool “deps_get_dependency_tree” functional
    • New tool “deps_get_package” functional
    • New tool “deps_get_version_history” functional
    • New tool “deps_monitor_check” functional
    • New tool “promo_create_listing” functional
    • New tool “promo_get_campaign_history” functional
    • New tool “promo_get_featured” functional
    • New tool “promo_get_leaderboard” functional
    • New tool “promo_get_listing” functional
    • New tool “promo_get_pricing” functional
    • New tool “promo_renew_listing” functional
    • New tool “promo_search_listings” functional
    • New tool “promo_takeover_top_spot” functional
    • New tool “reality_compare” functional
    • New tool “reality_get_conflicts” functional
    • New tool “reality_get_entity” functional
    • New tool “reality_get_evidence” functional
    • New tool “reality_get_history” functional
    • New tool “reality_monitor_check” functional
    • New tool “reality_resolve_entity” functional
    • New tool “reality_search” functional
    • New tool “tenders_get_authority” functional
    • New tool “tenders_get_awards” functional
    • New tool “tenders_get_changes” functional
    • New tool “tenders_get_deadlines” functional
    • New tool “tenders_get_history” functional
    • New tool “tenders_get_notice” functional
    • New tool “tenders_get_supplier_history” functional
    • New tool “tenders_monitor_check” functional
    • New tool “tenders_search” functional
    • New tool “yruz_get_source_status” functional
    • New tool “yruz_list_services” functional
    • Tool “get_example” changed its title: YRUZ example answer (free) → YRUZ how to call a tool (instructions) cosmetic
  • 26 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 25 Oct 26 73

    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://yruz.one/mcp/x402

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=yruz.one CN=WE1,O=Google Trust Services,C=US 30 Sept 2026 29 Dec 2026 ECDSA 256 ECDSA-SHA256 49973e33a427c594133d3ddeab780ddc
SANs: yruz.one, *.yruz.one
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 secure

Validation of yruz.one. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
one. present 64939 8 Verified
yruz.one. present 2371 13 Verified
yruz.one. Verified address RRset verified with the apex keys
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
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(self), microphone=(), camera=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://yruz.one/mcp/x402 Verified 200
http (plaintext) http://yruz.one/mcp/x402 HTTPS enforced 301 https://yruz.one/mcp/x402
MCP tools · 56 exposed · ~12,341 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
wallet_balance ~234

USDC and gas balance of any Solana or Base address, read from the chain: USDC amount, SOL or ETH for fees, whether the USDC account exists, and whether the wallet can pay a given x402 price. Lets an agent check its own funds or a counterparty before it pays. Price: 0.002 USDC per call, paid with x402 (USDC on Base or Solana, no account, no API key); invalid input is refused before payment and a failed run is never charged. Without a payment the tool returns the x402 PaymentRequired. How to call it: get_example {"tool":"wallet_balance"}. Same tool over HTTP: https://yruz.one/api/wallet?address=CWfaj5vDppWCp4q1X4iPYGWpCGY2Rerj9DQWqxTnz1Pp

NameTypeReqDescription
addressstringyesSolana (base58) or Base (0x) address (required)
amountstring–optional USDC price to test, e.g. 0.01

No output schema declared.

No examples provided.

weather_forecast ~237

Weather for any place on Earth: current conditions (temperature, feels-like, wind, humidity, pressure, cloud, precipitation), the next 48 hours hour by hour and a 7-day forecast with highs, lows and rain, in metric and imperial units, plus active official weather alerts for US locations. Place by name or coordinates. Data: MET Norway (CC BY 4.0) and the US National Weather Service. Price: 0.003 USDC per call, paid with x402 (USDC on Base or Solana, no account, no API key); invalid input is refused before payment and a failed run is never charged. Without a payment the tool returns the x402 PaymentRequired. How to call it: get_example {"tool":"weather_forecast"}. Same tool over HTTP: https://yruz.one/api/weather?q=New+York

NameTypeReqDescription
latstring–latitude, -90 to 90
lonstring–longitude, -180 to 180
qstring–place name (required unless lat/lon), e.g. Berlin or Austin, TX

No output schema declared.

No examples provided.

web_extract ~253

Fetch any public web page and return its main content as clean Markdown (navigation, scripts and boilerplate removed) with title, description, language, canonical URL, author, publish date, headings, links and images. Built for agents that need to read or cite the web. Follows up to 5 redirects; HTML, plain text and JSON pages. Price: 0.005 USDC per call, paid with x402 (USDC on Base or Solana, no account, no API key); invalid input is refused before payment and a failed run is never charged. Without a payment the tool returns the x402 PaymentRequired. How to call it: get_example {"tool":"web_extract"}. Same tool over HTTP: https://yruz.one/api/extract?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FHTTP_402

NameTypeReqDescription
linksstring–1 to include every link on the page (default 1)
max_charsstring–cap on the Markdown length, 1000-200000 (default 60000)
urlstringyespage URL (required), e.g. https://example.com/post

No output schema declared.

No examples provided.

x402_endpoint_check ~244

Validate any x402 endpoint the way buyer agents see it: calls it unpaid, decodes the 402 challenge (v2 PAYMENT-REQUIRED header and v1 JSON body), checks every offer (scheme, network, asset, amount, payTo format, timeout, fee payer, EIP-712 domain), CORS exposure and the origin's discovery files (/.well-known/x402, openapi.json, llms.txt). Returns networks, prices in USD and every problem with its fix. Price: 0.005 USDC per call, paid with x402 (USDC on Base or Solana, no account, no API key); invalid input is refused before payment and a failed run is never charged. Without a payment the tool returns the x402 PaymentRequired. How to call it: get_example {"tool":"x402_endpoint_check"}. Same tool over HTTP: https://yruz.one/api/x402-check?url=https%3A%2F%2Fyruz.one%2Fapi%2Faudit

NameTypeReqDescription
methodstring–GET (default) or POST
urlstringyesendpoint URL (required)

No output schema declared.

No examples provided.

yruz_get_source_status ~65

Discovery: every public source behind the data products (npm, PyPI, Packagist, OSV, TED, Wikidata) with licence, attribution, coverage and its measured health: last success, last failure and failure rate of YRUZ's own requests.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

yruz_list_services ~89

Discovery: the DependencyPulse, TenderGraph and RealityGraph tasks with their task ids, prices and billing units, limits, sources, freshness, MCP tool names and the x402 payment rails (v1 and v2, exact scheme, USDC on Base and Solana). Pass product (deps, tenders, reality) to narrow it.

NameTypeReqDescription
productstring–optional product id

No output schema declared.

No examples provided.

Install

How do I install the YRUZ x402 tools MCP server?

YRUZ x402 tools is a hosted endpoint at https://yruz.one/mcp/x402, 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 · yruz.one

# add to Claude Code
claude mcp add --transport http xzntexe-yruz-x402 'https://yruz.one/mcp/x402'
Common questions

What is the YRUZ x402 tools MCP server?

YRUZ x402 tools is an MCP server listed in the public MCP registry as io.github.xzntexe/yruz-x402. Pay-per-call x402 tools: package advisories, EU tenders, Wikidata facts, promo board, web, crypto. This page covers its hosted endpoint (https://yruz.one/mcp/x402).

Is the YRUZ x402 tools MCP server safe to use?

YRUZ x402 tools scores 78 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 YRUZ x402 tools MCP server expose?

YRUZ x402 tools exposes 56 tools: site_audit, web_extract, company_enrich, url_safety_check, domain_intel, and 51 more. Their descriptions and schemas cost roughly 12,341 tokens of context every time the server is loaded.

Does the YRUZ x402 tools MCP server require authentication?

No. We connected to YRUZ x402 tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the YRUZ x402 tools MCP server still maintained?

YRUZ x402 tools 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.