SAIKYO: pay from Russia
REMOTE · SAIKYO.EXCHANGE · SCANNED SEP 28
USDT/RUB rate, foreign Visa card terms, how to pay for foreign services from Russia, Shop search.
Available components
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 Security80
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 482 tokens (~80/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
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 7 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
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
claude mcp add --transport http exchange-saikyo-saikyo 'https://saikyo.exchange/api/mcp'
{
"mcpServers": {
"exchange-saikyo-saikyo": {
"url": "https://saikyo.exchange/api/mcp"
}
}
} {
"servers": {
"exchange-saikyo-saikyo": {
"type": "http",
"url": "https://saikyo.exchange/api/mcp"
}
}
} [mcp_servers.exchange-saikyo-saikyo] url = "https://saikyo.exchange/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"exchange-saikyo-saikyo": {
"type": "remote",
"url": "https://saikyo.exchange/api/mcp",
"enabled": true
}
}
} openclaw mcp add exchange-saikyo-saikyo --url 'https://saikyo.exchange/api/mcp' --transport streamable-http
mcp_servers:
exchange-saikyo-saikyo:
url: "https://saikyo.exchange/api/mcp" {
"McpServers": {
"exchange-saikyo-saikyo": {
"Transport": "http",
"Url": "https://saikyo.exchange/api/mcp"
}
}
} assistant mcp add exchange-saikyo-saikyo -t streamable-http -u 'https://saikyo.exchange/api/mcp'
{
"mcpServers": {
"exchange-saikyo-saikyo": {
"type": "http",
"url": "https://saikyo.exchange/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 69
First indexed and scored.
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 28 Sept 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=YE2,O=Let's Encrypt,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5eaeabb646477c09d8f68cf37ed59055437 |
| SANs: saikyo.exchange, www.saikyo.exchange | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 insecure
Validation of saikyo.exchange. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| exchange. | present | 46084 | 8 | Verified |
| saikyo.exchange. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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: https://mc.yandex.ru https://mc.yandex.com; script-src 'self' https://www.clarity.ms https://*.clarity.ms 'unsafe-inline' 'unsafe-eval' 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; script-src-elem 'self' https://www.clarity.ms https://*.clarity.ms 'unsafe-inline' 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; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; style-src-elem '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.sa |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(self), microphone=(), geolocation=(), payment=(self), fullscreen=(self), interest-cohort=() |
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 |
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 →
get_foreign_card_terms Foreign Visa card terms ~37
Terms of the Omega Wallet virtual Visa 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 Payment passport of a foreign service ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of returned links and titles (default en). |
| service | string | – | Service name, e.g. "Notion", "Vultr", "Duolingo". Omit for dataset links. |
No output schema declared.
No examples provided.
get_usdt_rub_rate USDT/RUB rate ~44
Current SAIKYO rate for buying USDT (TRC20) with rubles via SBP QR, 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 How to pay for a foreign service 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.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of returned links and titles (default en). |
| service | string | yes | Service name, e.g. "Claude" or "Steam". |
No output schema declared.
No examples provided.
search_saikyo_shop Search Saikyo Shop ~82
Search Saikyo Shop digital goods paid in rubles: AI subscriptions, gift cards, game top-ups, Telegram Stars, software.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| lang | string | – | Language of returned links and titles (default en). |
| query | string | – | Product or brand, e.g. "ChatGPT Plus", "Steam". |
No output schema declared.
No examples provided.
travel_card_for_country Travel card guide by 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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Country name in English or Russian, e.g. "Turkey". |
| lang | string | – | Language of returned links and titles (default en). |
No output schema declared.
No examples provided.
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 rate, foreign Visa card terms, how to pay for foreign services from Russia, Shop search. 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 70 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 6 tools: get_usdt_rub_rate, get_foreign_card_terms, how_to_pay_from_russia, get_payment_passport, travel_card_for_country, search_saikyo_shop. Their descriptions and schemas cost roughly 413 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 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.