mcp-everything: Russian APIs
REMOTE · MCP-EVERYTHING.RU
Russian APIs for AI agents: YooKassa, CDEK, Bitrix24 and more. Ready scenarios with code. No key.
Available components
Last scanned (2 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 22 Nov 2026.
Category Developer Tools
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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1083 tokens (~216/item across 5 items; 5 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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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 →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +55
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.73 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 14 Nov 26 −53
- Endpoint reachability: unreachable → not serving MCP ▼ security
- HSTS header: unverified → fail ▼ security
- TLS certificate: unverified → pass ▲ security
- Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. security
- 13 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.63 → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Nov 2026 · Probed https://mcp-everything.ru/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.mcp-everything.ru | CN=GlobalSign GCC R46 DV TLS CA 2025,O=GlobalSign nv-sa,C=BE | 8 Oct 2026 | 25 Apr 2027 | RSA 4096 | SHA256-RSA | 488274d4b9fd3c8b7cc52403 |
| SANs: www.mcp-everything.ru, autodiscover.mcp-everything.ru, mail.mcp-everything.ru, owa.mcp-everything.ru, mcp-everything.ru | ||||||
| CN=GlobalSign GCC R46 DV TLS CA 2025,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root R46,O=GlobalSign nv-sa,C=BE | 17 Sept 2025 | 23 Jun 2029 | RSA 2048 | SHA256-RSA | 8443588121db5ab28499ffae80670ba4 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp-everything.ru. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ru. | DS published | 26734 | 8 | Verified |
| mcp-everything.ru. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp-everything.ru/mcp | Verified | 200 | |
| http (plaintext) | http://mcp-everything.ru/mcp | HTTPS enforced | 301 | https://mcp-everything.ru/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_integration Вся запись о сервисе ~75
Всё о сервисе одним документом: охват (что описано, а что смотреть в официальной документации), сценарии, авторизация, методы, ошибки, нюансы. Объёмно — если задача понятна, лучше get_scenario.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Сервис, например yookassa |
No output schema declared.
No examples provided.
get_method Один метод API ~84
Один метод: параметры, примеры запроса и ответа, авторизация, базовый URL и ссылка на страницу метода в официальной документации. Экономит контекст, если нужен только он.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | yes | «POST /payments», «/payments» или «crm.deal.add» |
| slug | string | yes | Сервис, например yookassa |
No output schema declared.
No examples provided.
get_scenario Готовый сценарий интеграции ~108
Инструкция под одну задачу: шаги, пример кода, все нужные методы с параметрами и примерами, авторизация, базовый URL, подводные камни и ссылка на официальную документацию. Обычно этого достаточно, чтобы написать интеграцию. Бери id сценария из search или get_integration.
| Name | Type | Req | Description |
|---|---|---|---|
| scenario | string | yes | id сценария, например prinyat-oplatu |
| slug | string | yes | Сервис, например yookassa |
No output schema declared.
No examples provided.
list_catalog Каталог сервисов ~44
Все сервисы каталога по отраслям, со сценариями. Используй, если search ничего не нашёл или нужно выбрать сервис.
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | – | – |
No output schema declared.
No examples provided.
search Найти сценарий или метод российского API ~593
Ищет по задаче, сервису или методу среди российских API и возвращает готовые сценарии (шаги + код) и методы. Используй, когда нужно интегрироваться с российским сервисом: приём платежей, доставка, CRM, маркетплейсы, учёт, SMS. Понимает запросы на русском и английском. Сейчас в каталоге: 5Post API, Авито API для бизнеса, Авто.ру API для дилеров, Битрикс24 REST API, Ветис.API — Меркурий (ФГИС ВетИС), Достависта Business API, Контур.Диадок API, Контур.Фокус API, Мегамаркет API DBS, Мегаплан API v3, Модульбанк API, МойСклад JSON API 1.2, Московская биржа — ISS (Informational & Statistical Server), Островок — ETG API (RateHawk), Пачка API, Почта России, ПЭК API личного кабинета, СДЭК API v2, Т‑Касса, Такском API (Такском-Касса, ОФД), Точка Банк API, Хантфлоу API v2, ЦБ РФ — курсы валют и ставки (XML и DailyInfo), Циан API, ЮKassa, Яндекс Диск REST API, Яндекс Доставка API (Доставка по России), Яндекс Еда Vendor API, Яндекс Маркет Partner API, Alfa API, amoCRM API v4, API Геокодера Яндекс Карт, API Деловых Линий, API Яндекс Директа v5, API Яндекс Метрики, API Яндекс Погоды, API Яндекс Расписаний, API Яндекс Go для бизнеса, API VK Рекламы, Aviasales Data API (Travelpayouts) и ещё 41.
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | – | finance — Платежи и финансы; crm — CRM и продажи; logistics — Логистика и доставка; retail — Ритейл и e-commerce; marketplaces — Маркетплейсы; marketing — Реклама и аналитика; communications — Связь… |
| page | integer | – | – |
| query | string | yes | Задача или сервис: «принять оплату ЮKassa», «расчёт доставки СДЭК», «crm.deal.add», «accept payment» |
No output schema declared.
No examples provided.
How do I install the mcp-everything: Russian APIs server?
mcp-everything: Russian APIs is a hosted endpoint at https://mcp-everything.ru/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 · mcp-everything.ru
claude mcp add --transport http ru-mcp-everything-russian-apis 'https://mcp-everything.ru/mcp'
What is the mcp-everything: Russian APIs server?
mcp-everything: Russian APIs is listed in the public MCP registry as ru.mcp-everything/russian-apis. Russian APIs for AI agents: YooKassa, CDEK, Bitrix24 and more. Ready scenarios with code. No key. This page covers its hosted endpoint (https://mcp-everything.ru/mcp).
Is the mcp-everything: Russian APIs server safe to use?
mcp-everything: Russian APIs scores 81 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 mcp-everything: Russian APIs server expose?
mcp-everything: Russian APIs exposes 5 tools: search, get_scenario, get_method, get_integration, list_catalog. Their descriptions and schemas cost roughly 904 tokens of context every time the server is loaded.
Does the mcp-everything: Russian APIs server require authentication?
No. We connected to mcp-everything: Russian APIs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the mcp-everything: Russian APIs server still maintained?
mcp-everything: Russian APIs is still listed as active in the MCP registry. We last reached this channel on 22 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 mcp-everything: Russian APIs server?
VerifyMCP ran 13 checks on mcp-everything: Russian APIs, 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.