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.

Saymon RU Data API

REMOTE · PAYFORAPI.COM

Russian company lookup (EGRUL/INN), Cyrillic search, RU page to Markdown. Pay per call in USDC.

Available components

+5 this week 76 Trust /100

Last scanned (20 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

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 Security63
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 728 tokens (~56/item across 13 items; 13 tools + 0 resources), lean.Pass
  • 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 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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
What we tested

Checks we ran (12)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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.

  • 17 Nov 26 +5
    • Stability: fail → pass ▲ security
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 61 to 64.

  • 10 Nov 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 64 to 61.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 61 to 64.

  • 8 Nov 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 64 to 61.

  • 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
  • 18 Oct 26 0
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 1.30.0 ▼ security
    • Tool “company_report” was removed ▼ security
    • Tool “ru_research” was removed ▼ security
    • Tool “ru_research_deep” was removed ▼ security
    • Tool “ru_search” was removed ▼ security
    • Tool “ru_search_x10” was removed ▼ security
    • Tool “ru_search_x100” was removed ▼ security
    • Tool “web_search” was removed ▼ security
    • Schema quality: 1150 → 728 ▲ functional
  • 12 Oct 26 0
    • Stability: fail → 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://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=YR2,O=Let's Encrypt,C=US 27 Oct 2026 25 Jan 2027 RSA 4096 SHA256-RSA 6d0dc3c9f61cccc019ff716b0a26aaa4b47
SANs: payforapi.com, payforapi.rialenergo.ru, www.payforapi.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
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. DS published 19718 13 Verified
payforapi.com. No DS 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
MCP tools · 13 exposed · ~728 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
cbr_rates ~57

Официальные курсы ЦБ РФ (ежедневные, обновление раз в день): USD, EUR, CNY, GBP, KZT и другие ISO-коды. $0.008 USDC

NameTypeReqDescription
currencies–––

No output schema declared.

No examples provided.

fns_npd_check ~48

Статус самозанятого (НПД) по ИНН через реестр ФНС. $0.01 USDC

NameTypeReqDescription
innstringyes–

No output schema declared.

No examples provided.

inn_lookup ~39

Проверка российского юрлица по ИНН (ЕГРЮЛ). $0.01 USDC

NameTypeReqDescription
innstringyes–

No output schema declared.

No examples provided.

moex_quote ~73

Котировки Московской биржи (MOEX ISS): последняя цена акций (SBER, GAZP...), валютных пар (USD/EUR/CNY) и индексов (IMOEX). $0.008 USDC

NameTypeReqDescription
marketstring––
symbolstring––

No output schema declared.

No examples provided.

pochta_address ~44

Почта России: нормализация российского адреса (индекс, регион, улица, дом). $0.01 USDC

NameTypeReqDescription
addressstringyes–

No output schema declared.

No examples provided.

pochta_delivery ~96

Пакет «Доставка Почты России»: адрес, индекс, отделение, стоимость и срок одним платежом — 5 сервисов в одном. $0.04 USDC

NameTypeReqDescription
declared_value–––
from_indexstringyes–
mail_categorystring––
mail_typestring––
to_address–––
to_index–––
weightinteger––

No output schema declared.

No examples provided.

pochta_delivery_time ~63

Почта России: сроки доставки между индексами (в днях). $0.01 USDC

NameTypeReqDescription
from_indexstringyes–
mail_categorystring––
mail_typestring––
to_indexstringyes–

No output schema declared.

No examples provided.

pochta_offices ~58

Почта России: отделения по индексу или ближайшие по координатам. $0.01 USDC

NameTypeReqDescription
latitude–––
longitude–––
postal_code–––
topinteger––

No output schema declared.

No examples provided.

pochta_tariff ~85

Почта России: стоимость и сроки доставки между индексами (официальный API). $0.01 USDC

NameTypeReqDescription
declared_value–––
dimension_type–––
from_indexstringyes–
mail_categorystring––
mail_typestring––
to_indexstringyes–
weightinteger––

No output schema declared.

No examples provided.

pochta_track ~39

Почта России: отслеживание отправления по трек-номеру. $0.01 USDC

NameTypeReqDescription
barcodestringyes–

No output schema declared.

No examples provided.

pochta_zip ~41

Почта России: адрес отделения и населённый пункт по индексу. $0.01 USDC

NameTypeReqDescription
postal_codestringyes–

No output schema declared.

No examples provided.

ru_page ~33

RU-страница URL -> LLM-ready Markdown. $0.01 USDC

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

ticker ~52

Крипто-тикеры Bybit (spot): цена, изменение за 24ч, объёмы (BTCUSDT, ETHUSDT...). $0.005 USDC

NameTypeReqDescription
symbolstring––

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http com-payforapi-saymon-ru-data-api 'https://payforapi.com/mcp'
Common questions

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 76 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 13 tools: inn_lookup, ru_page, cbr_rates, moex_quote, pochta_tariff, and 8 more. Their descriptions and schemas cost roughly 728 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 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 Saymon RU Data API MCP server?

VerifyMCP ran 12 checks on Saymon RU Data API, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Saymon RU Data API: Authorization. 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.