Remote MCP · Endpoint

SAIKYO: pay from Russia MCP server

No. SAIKYO: pay from Russia answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://saikyo.exchange/api/mcp

The last check completed an MCP handshake.

Registry name
exchange.saikyo/saikyo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
515 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
USDT/RUB quote, wallet AML check, foreign Visa card terms, paying for foreign services from Russia
Listing
From the official MCP registry (active).
Recent checks of SAIKYO: pay from Russia
CheckedResultHandshake
2 hours agoHandshake completed515 ms
2 days agoHandshake completed408 ms
4 days agoHandshake completed408 ms
6 days agoHandshake completed420 ms
8 days agoHandshake completed411 ms
10 days agoHandshake completed749 ms
12 days agoHandshake completed407 ms
13 days agoHandshake completed465 ms
14 days agoHandshake completed393 ms
16 days agoHandshake completed415 ms
18 days agoHandshake completed403 ms
20 days agoHandshake completed485 ms
21 days agoHandshake completed407 ms
23 days agoHandshake completed411 ms
24 days agoHandshake completed404 ms

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

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 SAIKYO: pay from Russia and makes no claim about it beyond what these checks measured.