Saymon RU Data API
REMOTE · PAYFORAPI.COM · SCANNED SEP 28
Russian company lookup (EGRUL/INN), Cyrillic search, RU page to Markdown. Pay per call in USDC.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 20 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1150 tokens (~57/item across 20 items; 20 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 11 breaking changes, 0 auth/transport breaks, 9 additions. See how to fix → Fail
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 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
How do I install the Saymon RU Data API MCP server?
Saymon RU Data API is a hosted endpoint at https://payforapi.com/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 · payforapi.com
claude mcp add --transport http com-payforapi-saymon-ru-data-api 'https://payforapi.com/mcp'
{
"mcpServers": {
"com-payforapi-saymon-ru-data-api": {
"url": "https://payforapi.com/mcp"
}
}
} {
"servers": {
"com-payforapi-saymon-ru-data-api": {
"type": "http",
"url": "https://payforapi.com/mcp"
}
}
} [mcp_servers.com-payforapi-saymon-ru-data-api] url = "https://payforapi.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-payforapi-saymon-ru-data-api": {
"type": "remote",
"url": "https://payforapi.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-payforapi-saymon-ru-data-api --url 'https://payforapi.com/mcp' --transport streamable-http
mcp_servers:
com-payforapi-saymon-ru-data-api:
url: "https://payforapi.com/mcp" {
"McpServers": {
"com-payforapi-saymon-ru-data-api": {
"Transport": "http",
"Url": "https://payforapi.com/mcp"
}
}
} assistant mcp add com-payforapi-saymon-ru-data-api -t streamable-http -u 'https://payforapi.com/mcp'
{
"mcpServers": {
"com-payforapi-saymon-ru-data-api": {
"type": "http",
"url": "https://payforapi.com/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 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 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
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40.
- 17 Sept 26 0
- Judged manipulation: pass → unverified ▼ security
- Schema quality: 881 → 1150 ▼ functional
- New tool “fns_npd_check” functional
- New tool “ru_search_x10” functional
- New tool “ru_search_x100” functional
- New tool “ticker” functional
- New tool “web_search” functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17.
- 11 Sept 26 −3
- Stability: 0.60 → fail ▼ security
- A breaking change shipped without a version bump: still 1.30.0 ▼ security
- HSTS header: fail → pass ▲ security
- “company_report” added a required parameter “inn”, so existing callers break ▼ functional
- “inn_lookup” added a required parameter “inn”, so existing callers break ▼ functional
- “pochta_address” added a required parameter “address”, so existing callers break ▼ functional
- “pochta_delivery” added a required parameter “from_index”, so existing callers break ▼ functional
- “pochta_delivery_time” added a required parameter “from_index”, so existing callers break ▼ functional
- “pochta_delivery_time” added a required parameter “to_index”, so existing callers break ▼ functional
- “pochta_tariff” added a required parameter “from_index”, so existing callers break ▼ functional
- “pochta_tariff” added a required parameter “to_index”, so existing callers break ▼ functional
- “pochta_track” added a required parameter “barcode”, so existing callers break ▼ functional
- “pochta_zip” added a required parameter “postal_code”, so existing callers break ▼ functional
- “ru_page” added a required parameter “url”, so existing callers break ▼ functional
- “ru_research” added a required parameter “query”, so existing callers break ▼ functional
- “ru_research_deep” added a required parameter “query”, so existing callers break ▼ functional
- “ru_search” added a required parameter “query”, so existing callers break ▼ functional
- “cbr_rates” dropped the required parameter “args” ▼ functional
- “cbr_rates” dropped the required parameter “extra” ▼ functional
- “company_report” dropped the required parameter “args” ▼ functional
- “company_report” dropped the required parameter “extra” ▼ functional
- “inn_lookup” dropped the required parameter “args” ▼ functional
- “inn_lookup” dropped the required parameter “extra” ▼ functional
- “moex_quote” dropped the required parameter “args” ▼ functional
- “moex_quote” dropped the required parameter “extra” ▼ functional
- “pochta_address” dropped the required parameter “args” ▼ functional
- “pochta_address” dropped the required parameter “extra” ▼ functional
- “pochta_delivery” dropped the required parameter “args” ▼ functional
- “pochta_delivery” dropped the required parameter “extra” ▼ functional
- “pochta_delivery_time” dropped the required parameter “args” ▼ functional
- “pochta_delivery_time” dropped the required parameter “extra” ▼ functional
- “pochta_offices” dropped the required parameter “args” ▼ functional
- “pochta_offices” dropped the required parameter “extra” ▼ functional
- “pochta_tariff” dropped the required parameter “args” ▼ functional
- “pochta_tariff” dropped the required parameter “extra” ▼ functional
- “pochta_track” dropped the required parameter “args” ▼ functional
- “pochta_track” dropped the required parameter “extra” ▼ functional
- “pochta_zip” dropped the required parameter “args” ▼ functional
- “pochta_zip” dropped the required parameter “extra” ▼ functional
- “ru_page” dropped the required parameter “args” ▼ functional
- “ru_page” dropped the required parameter “extra” ▼ functional
- “ru_research” dropped the required parameter “args” ▼ functional
- “ru_research” dropped the required parameter “extra” ▼ functional
- “ru_research_deep” dropped the required parameter “args” ▼ functional
- “ru_research_deep” dropped the required parameter “extra” ▼ functional
- “ru_search” dropped the required parameter “args” ▼ functional
- “ru_search” dropped the required parameter “extra” ▼ functional
- “cbr_rates” added an optional parameter “currencies” cosmetic
- “company_report” added an optional parameter “limit” cosmetic
- “company_report” added an optional parameter “max_pages” cosmetic
- “moex_quote” added an optional parameter “market” cosmetic
- “moex_quote” added an optional parameter “symbol” cosmetic
- “pochta_delivery” added an optional parameter “declared_value” cosmetic
- “pochta_delivery” added an optional parameter “mail_category” cosmetic
- “pochta_delivery” added an optional parameter “mail_type” cosmetic
- “pochta_delivery” added an optional parameter “to_address” cosmetic
- “pochta_delivery” added an optional parameter “to_index” cosmetic
- “pochta_delivery” added an optional parameter “weight” cosmetic
- “pochta_delivery_time” added an optional parameter “mail_category” cosmetic
- “pochta_delivery_time” added an optional parameter “mail_type” cosmetic
- “pochta_offices” added an optional parameter “latitude” cosmetic
- “pochta_offices” added an optional parameter “longitude” cosmetic
- “pochta_offices” added an optional parameter “postal_code” cosmetic
- “pochta_offices” added an optional parameter “top” cosmetic
- “pochta_tariff” added an optional parameter “declared_value” cosmetic
- “pochta_tariff” added an optional parameter “dimension_type” cosmetic
- “pochta_tariff” added an optional parameter “mail_category” cosmetic
- “pochta_tariff” added an optional parameter “mail_type” cosmetic
- “pochta_tariff” added an optional parameter “weight” cosmetic
- “ru_research” added an optional parameter “limit” cosmetic
- “ru_research” added an optional parameter “max_pages” cosmetic
- “ru_research_deep” added an optional parameter “limit” cosmetic
- “ru_research_deep” added an optional parameter “max_pages” cosmetic
- “ru_search” added an optional parameter “limit” cosmetic
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://payforapi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=payforapi.com | CN=YR1,O=Let's Encrypt,C=US | 28 Aug 2026 | 26 Nov 2026 | RSA 4096 | SHA256-RSA | 605ec2a027730526e8d21ceca81890c4af6 |
| SANs: payforapi.com, payforapi.rialenergo.ru, www.payforapi.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of payforapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| payforapi.com. | 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=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), camera=(), microphone=(), payment=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://payforapi.com/mcp | Verified | 200 | |
| http (plaintext) | http://payforapi.com/mcp | HTTPS enforced | 301 | https://payforapi.com/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 →
cbr_rates ~57
Официальные курсы ЦБ РФ (ежедневные, обновление раз в день): USD, EUR, CNY, GBP, KZT и другие ISO-коды. $0.008 USDC
| Name | Type | Req | Description |
|---|---|---|---|
| currencies | – | – | – |
No output schema declared.
No examples provided.
company_report ~93
Пакет «Проверка контрагента» (KYB-досье): ЕГРЮЛ + статус самозанятого (НПД) + deep-досье по рунету одним платежом — 3 сервиса в одном. $0.05 USDC
| Name | Type | Req | Description |
|---|---|---|---|
| inn | string | yes | – |
| limit | integer | – | – |
| max_pages | integer | – | – |
No output schema declared.
No examples provided.
fns_npd_check ~48
Статус самозанятого (НПД) по ИНН через реестр ФНС. $0.01 USDC
| Name | Type | Req | Description |
|---|---|---|---|
| inn | string | yes | – |
No output schema declared.
No examples provided.
inn_lookup ~39
Проверка российского юрлица по ИНН (ЕГРЮЛ). $0.01 USDC
| Name | Type | Req | Description |
|---|---|---|---|
| inn | string | yes | – |
No output schema declared.
No examples provided.
moex_quote ~73
Котировки Московской биржи (MOEX ISS): последняя цена акций (SBER, GAZP...), валютных пар (USD/EUR/CNY) и индексов (IMOEX). $0.008 USDC
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | – | – |
| symbol | string | – | – |
No output schema declared.
No examples provided.
pochta_address ~44
Почта России: нормализация российского адреса (индекс, регион, улица, дом). $0.01 USDC
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
pochta_delivery ~96
Пакет «Доставка Почты России»: адрес, индекс, отделение, стоимость и срок одним платежом — 5 сервисов в одном. $0.04 USDC
| Name | Type | Req | Description |
|---|---|---|---|
| declared_value | – | – | – |
| from_index | string | yes | – |
| mail_category | string | – | – |
| mail_type | string | – | – |
| to_address | – | – | – |
| to_index | – | – | – |
| weight | integer | – | – |
No output schema declared.
No examples provided.
pochta_delivery_time ~63
Почта России: сроки доставки между индексами (в днях). $0.01 USDC
| Name | Type | Req | Description |
|---|---|---|---|
| from_index | string | yes | – |
| mail_category | string | – | – |
| mail_type | string | – | – |
| to_index | string | yes | – |
No output schema declared.
No examples provided.
pochta_offices ~58
Почта России: отделения по индексу или ближайшие по координатам. $0.01 USDC
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | – | – | – |
| longitude | – | – | – |
| postal_code | – | – | – |
| top | integer | – | – |
No output schema declared.
No examples provided.
pochta_tariff ~85
Почта России: стоимость и сроки доставки между индексами (официальный API). $0.01 USDC
| Name | Type | Req | Description |
|---|---|---|---|
| declared_value | – | – | – |
| dimension_type | – | – | – |
| from_index | string | yes | – |
| mail_category | string | – | – |
| mail_type | string | – | – |
| to_index | string | yes | – |
| weight | integer | – | – |
No output schema declared.
No examples provided.
pochta_track ~39
Почта России: отслеживание отправления по трек-номеру. $0.01 USDC
| Name | Type | Req | Description |
|---|---|---|---|
| barcode | string | yes | – |
No output schema declared.
No examples provided.
pochta_zip ~41
Почта России: адрес отделения и населённый пункт по индексу. $0.01 USDC
| Name | Type | Req | Description |
|---|---|---|---|
| postal_code | string | yes | – |
No output schema declared.
No examples provided.
ru_page ~33
RU-страница URL -> LLM-ready Markdown. $0.01 USDC
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
ru_research ~59
Research-пакет: кириллический поиск + top-страницы в Markdown одним платежом. $0.02 USDC
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| max_pages | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
ru_research_deep ~60
Research-пакет deep: 3 поиска + до 10 страниц в Markdown одним платежом. $0.05 USDC
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| max_pages | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
ru_search ~41
Кириллический веб-поиск для агентов. $0.02 USDC
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
ru_search_x10 ~57
Кириллический веб-поиск пакетом: до 10 запросов одним платежом (скидка 10%). $0.18 USDC
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| queries | array | yes | – |
No output schema declared.
No examples provided.
ru_search_x100 ~57
Кириллический веб-поиск пакетом: до 100 запросов одним платежом (скидка 20%). $1.60 USDC
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| queries | array | yes | – |
No output schema declared.
No examples provided.
ticker ~52
Крипто-тикеры Bybit (spot): цена, изменение за 24ч, объёмы (BTCUSDT, ETHUSDT...). $0.005 USDC
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | – | – |
No output schema declared.
No examples provided.
web_search ~55
Глобальный веб-поиск (Tavily через x402): свежие результаты и краткий ответ по запросу. $0.02 USDC
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
What is the Saymon RU Data API MCP server?
Saymon RU Data API is an MCP server listed in the public MCP registry as com.payforapi/saymon-ru-data-api. Russian company lookup (EGRUL/INN), Cyrillic search, RU page to Markdown. Pay per call in USDC. This page covers its hosted endpoint (https://payforapi.com/mcp).
Is the Saymon RU Data API MCP server safe to use?
Saymon RU Data API scores 69 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 Saymon RU Data API MCP server expose?
Saymon RU Data API exposes 20 tools: inn_lookup, ru_search, ru_page, ru_research, ru_research_deep, and 15 more. Their descriptions and schemas cost roughly 1,150 tokens of context every time the server is loaded.
Does the Saymon RU Data API MCP server require authentication?
No. We connected to Saymon RU Data API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Saymon RU Data API MCP server still maintained?
Saymon RU Data API 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.