Remote MCP · Endpoint

YRUZ x402 tools MCP server

No. YRUZ x402 tools answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://yruz.one/mcp/x402

The last check completed an MCP handshake.

Registry name
io.github.xzntexe/yruz-x402
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
327 ms
Tools exposed
56 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Pay-per-call x402 tools: package advisories, EU tenders, Wikidata facts, promo board, web, crypto
Listing
From the official MCP registry (active).
Recent checks of YRUZ x402 tools
CheckedResultHandshake
1 hour agoHandshake completed327 ms
3 days agoHandshake completed404 ms
13 days agoHandshake completed366 ms
14 days agoHandshake completed398 ms
15 days agoHandshake completed380 ms
16 days agoHandshake completed443 ms
18 days agoHandshake completed389 ms
18 days agoHandshake completed434 ms
19 days agoHandshake completed466 ms
21 days agoHandshake completed212 ms
22 days agoHandshake completed441 ms
25 days agoHandshake completed513 ms

The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with YRUZ x402 tools and makes no claim about it beyond what these checks measured.