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.

SAIKYO: pay from Russia

REMOTE · SAIKYO.EXCHANGE

USDT/RUB quote, wallet AML check, foreign Visa card terms, paying for foreign services from Russia

Available components

0 this week 85 Trust /100

Last scanned (20 hours ago)

Scores higher than 86% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

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
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1382 tokens (~115/item across 12 items; 12 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "how_to_pay_from_russia" implies "pay" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 18 Nov 26 0
    • Tool “get_foreign_card_terms” rewrote its description, which is the text the model reads security
    • Tool “get_foreign_card_terms” changed its title: Foreign Visa card terms → Foreign card terms cosmetic
  • 12 Nov 26 +1
    • DNSSEC: fail → pass ▲ security
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Oct 26 0
    • Stability: 0.97 → pass security
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 21 Nov 2026 · Probed https://saikyo.exchange/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=saikyo.exchange CN=YE1,O=Let's Encrypt,C=US 31 Oct 2026 29 Jan 2027 ECDSA 256 ECDSA-SHA384 66304279f2e635dd9305ae0bd0a21f73676
SANs: *.saikyo.exchange, saikyo.exchange
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of saikyo.exchange. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
exchange. DS published 5011 8 Verified
saikyo.exchange. DS published 2371 13 Verified
saikyo.exchange. 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=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; img-src 'self' data: blob: https:; script-src 'self' https://www.clarity.ms https://*.clarity.ms https://challenges.cloudflare.com https://www.googletagmanager.com https://www.google-analytics.com https://static.cloudflareinsights.com blob: https://mc.yandex.ru https://mc.yandex.com https://yastatic.net https://top-fwz1.mail.ru https://privacy-cs.mail.ru; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self' https://*.clarity.ms https://c.bing.com https://challenges.cloudflare.com https://api.coingecko.com https://apilist.tronscan.org https://id.saikyo.exchange https://id-global.saikyo.exchange https://saikyo.exchange https://global.saikyo.exchange https://www.googletagmanager.com https://www.google-analytics.com https://www.google.com https://static.cloudflareinsights.com https://fonts.googleapis.com https://fonts.gstatic.com https://www.bestchange.ru https://kurs.expert https://exnode.ru https://mc.yandex.ru htt
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://saikyo.exchange/api/mcp Verified 200
http (plaintext) http://saikyo.exchange/api/mcp HTTPS enforced 301 https://saikyo.exchange/api/mcp
MCP tools · 12 exposed · ~1,217 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
calculate_exchange ~168

Use for an exact SAIKYO quote from RUB via SBP QR (Omega Wallet) to USDT. Returns the live Omega Wallet rate, network fee, amounts, limits, reserve and order link.

NameTypeReqDescription
amountnumberyesAmount in the currency chosen by amount_side (default: rubles the user pays).
amount_sidestring–Whether amount is the amount paid (give) or received (get). Defaults to give.
from_codestring–Currency the user pays. Defaults to RUB (rubles via SBP QR).
to_codestring–Currency the user receives. Defaults to USDTTRC20 (USDT on TRON); also USDTTON, USDTPOLYGON, USDTBEP20, USDTERC20.

No output schema declared.

No examples provided.

check_wallet_aml ~113

Use when the user asks to screen a crypto wallet address for AML risk. Supports TRON, EVM, Bitcoin and TON addresses and returns an indicative screening result.

NameTypeReqDescription
addressstringyesWallet address to screen (TRON, EVM/Ethereum, Bitcoin or TON).
coinstring–Optional asset ticker, e.g. USDT, BTC, ETH, TON.
networkstring–Optional network hint: TRC20, ERC20, BEP20, BTC, TON.

No output schema declared.

No examples provided.

find_exchange_route ~158

Use when the user wants to exchange rubles, RUB or SBP QR for USDT (TRC20, TON, Polygon, BEP20, ERC20). Resolves Russian and English currency terms and returns the live SAIKYO quote and order link.

NameTypeReqDescription
amountnumber–Amount in the currency chosen by amount_side.
amount_sidestring–Whether amount is the amount paid (give) or received (get). Defaults to give.
getstringyesWhat the user wants to receive: "USDT", "тезер", "TRC20".
givestringyesWhat the user pays, in any language: "рубли", "RUB", "СБП".

No output schema declared.

No examples provided.

get_exchanger_info ~52

Use when the user asks about SAIKYO domains, published support channels, automatic exchange mode, white-crypto/licensed partners, AML/KYC policy or exchange directions. Each section includes a source URL.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_foreign_card_terms ~37

Terms of the Omega Wallet virtual international card for residents of Russia: price, fees, top-up methods, requirements and caveats.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_payment_passport ~91

Payment facts for 900+ foreign services from official pages: accepted payment methods, Russia availability, official gift cards, crypto acceptance, billing-country checks and source URLs.

NameTypeReqDescription
langstring–Language of returned links and titles (default en).
servicestring–Service name, e.g. "Notion", "Vultr", "Duolingo". Omit for dataset links.

No output schema declared.

No examples provided.

get_usdt_rub_rate ~47

Current SAIKYO rate for buying USDT (TRC20) with rubles via SBP QR through Omega Wallet, plus a market reference buy/sell rate.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

how_to_pay_from_russia ~84

Payment options from Russia for a foreign service (ChatGPT, Claude, Midjourney, Cursor, Steam, Netflix, Airbnb and 1,000+ others) with guide links.

NameTypeReqDescription
langstring–Language of returned links and titles (default en).
servicestringyesService name, e.g. "Claude" or "Steam".

No output schema declared.

No examples provided.

list_exchange_directions ~119

Use when the user asks which SAIKYO crypto exchange directions are available, including RUB via SBP QR (Omega Wallet) and USDT TRC20/TON/Polygon/BEP20/ERC20. Returns live Omega Wallet quotes for every USDT network, limits (RUB 100–10,000,000), reserve and order link.

NameTypeReqDescription
currencystring–Optional Russian or English currency, payment or network term, such as RUB, рубли, SBP, СБП, USDT or TRC20.

No output schema declared.

No examples provided.

search_saikyo_shop ~98

Search Saikyo Shop digital goods paid in rubles: AI subscriptions, gift cards, game top-ups, Telegram Stars, software.

NameTypeReqDescription
categorystring–Optional catalog category slug, e.g. "ai", "games", "subscriptions".
langstring–Language of returned links and titles (default en).
querystring–Product or brand, e.g. "ChatGPT Plus", "Steam".

No output schema declared.

No examples provided.

start_exchange_order ~175

Use when the user wants to continue with a RUB via SBP QR (Omega Wallet) to USDT exchange. Returns the live quote, a prefilled link and the steps the user completes on the site. Does not submit an order.

NameTypeReqDescription
amountnumberyesAmount in the currency chosen by amount_side (default: rubles the user pays).
amount_sidestring–Whether amount is the amount paid (give) or received (get). Defaults to give.
from_codestring–Currency the user pays. Defaults to RUB (rubles via SBP QR).
to_codestring–Currency the user receives. Defaults to USDTTRC20 (USDT on TRON); also USDTTON, USDTPOLYGON, USDTBEP20, USDTERC20.

No output schema declared.

No examples provided.

travel_card_for_country ~75

Card payment tips for Russians travelling to a country: local currency, popular apps, caveats and guide link. Omit country to list all guides.

NameTypeReqDescription
countrystring–Country name in English or Russian, e.g. "Turkey".
langstring–Language of returned links and titles (default en).

No output schema declared.

No examples provided.

Install

How do I install the SAIKYO: pay from Russia MCP server?

SAIKYO: pay from Russia is a hosted endpoint at https://saikyo.exchange/api/mcp, 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 · saikyo.exchange

# add to Claude Code
claude mcp add --transport http exchange-saikyo-saikyo 'https://saikyo.exchange/api/mcp'
Common questions

What is the SAIKYO: pay from Russia MCP server?

SAIKYO: pay from Russia is an MCP server listed in the public MCP registry as exchange.saikyo/saikyo. USDT/RUB quote, wallet AML check, foreign Visa card terms, paying for foreign services from Russia. This page covers its hosted endpoint (https://saikyo.exchange/api/mcp).

Is the SAIKYO: pay from Russia MCP server safe to use?

SAIKYO: pay from Russia scores 85 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 SAIKYO: pay from Russia MCP server expose?

SAIKYO: pay from Russia exposes 12 tools: get_usdt_rub_rate, get_foreign_card_terms, how_to_pay_from_russia, get_payment_passport, travel_card_for_country, and 7 more. Their descriptions and schemas cost roughly 1,217 tokens of context every time the server is loaded.

Does the SAIKYO: pay from Russia MCP server require authentication?

No. We connected to SAIKYO: pay from Russia without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SAIKYO: pay from Russia MCP server still maintained?

SAIKYO: pay from Russia is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the SAIKYO: pay from Russia MCP server?

VerifyMCP ran 13 checks on SAIKYO: pay from Russia, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.