# mcp-everything: Russian APIs (remote · mcp-everything.ru)

Russian APIs for AI agents: YooKassa, CDEK, Bitrix24 and more. Ready scenarios with code. No key.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `mcp-everything.ru`: 81/100 (this document), [markdown](https://verifymcp.io/servers/ru-mcp-everything-russian-apis/mcp-everything.md), [page](https://verifymcp.io/servers/ru-mcp-everything-russian-apis/mcp-everything)

## Channel facts

- Endpoint: `https://mcp-everything.ru/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-22.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 78% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http ru-mcp-everything-russian-apis 'https://mcp-everything.ru/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ru-mcp-everything-russian-apis": {
      "url": "https://mcp-everything.ru/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ru-mcp-everything-russian-apis": {
      "type": "http",
      "url": "https://mcp-everything.ru/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ru-mcp-everything-russian-apis]
url = "https://mcp-everything.ru/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ru-mcp-everything-russian-apis": {
      "type": "remote",
      "url": "https://mcp-everything.ru/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ru-mcp-everything-russian-apis --url 'https://mcp-everything.ru/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ru-mcp-everything-russian-apis:
    url: "https://mcp-everything.ru/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ru-mcp-everything-russian-apis": {
      "Transport": "http",
      "Url": "https://mcp-everything.ru/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ru-mcp-everything-russian-apis -t streamable-http -u 'https://mcp-everything.ru/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ru-mcp-everything-russian-apis": {
      "type": "http",
      "url": "https://mcp-everything.ru/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 81, +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.

### 2026-11-19 (score 80, +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.

### 2026-11-17 (score 79, +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.

### 2026-11-15 (score 78, +55)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.73
- [functional improvement] MCP protocol: unverified → pass

### 2026-11-14 (score 23, −53)

- [security regression] Endpoint reachability: unreachable → not serving MCP
- [security regression] HSTS header: unverified → fail
- [security improvement] TLS certificate: unverified → pass
- [security] Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 502.

### 2026-11-13 (score 76, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.63 → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-10 (score 76, +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.

### 2026-11-08 (score 75, +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.

## MCP tools (5)

### `search` (~593 tokens)

Найти сценарий или метод российского API

Ищет по задаче, сервису или методу среди российских 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.

Input parameters:

- `industry` (string): finance — Платежи и финансы; crm — CRM и продажи; logistics — Логистика и доставка; retail — Ритейл и e-commerce; marketplaces — Маркетплейсы; marketing — Реклама и аналитика; communications — Связь…
- `page` (integer)
- `query` (string, required): Задача или сервис: «принять оплату ЮKassa», «расчёт доставки СДЭК», «crm.deal.add», «accept payment»

### `get_scenario` (~108 tokens)

Готовый сценарий интеграции

Инструкция под одну задачу: шаги, пример кода, все нужные методы с параметрами и примерами, авторизация, базовый URL, подводные камни и ссылка на официальную документацию. Обычно этого достаточно, чтобы написать интеграцию. Бери id сценария из search или get_integration.

Input parameters:

- `scenario` (string, required): id сценария, например prinyat-oplatu
- `slug` (string, required): Сервис, например yookassa

### `get_method` (~84 tokens)

Один метод API

Один метод: параметры, примеры запроса и ответа, авторизация, базовый URL и ссылка на страницу метода в официальной документации. Экономит контекст, если нужен только он.

Input parameters:

- `method` (string, required): «POST /payments», «/payments» или «crm.deal.add»
- `slug` (string, required): Сервис, например yookassa

### `get_integration` (~75 tokens)

Вся запись о сервисе

Всё о сервисе одним документом: охват (что описано, а что смотреть в официальной документации), сценарии, авторизация, методы, ошибки, нюансы. Объёмно — если задача понятна, лучше get_scenario.

Input parameters:

- `slug` (string, required): Сервис, например yookassa

### `list_catalog` (~44 tokens)

Каталог сервисов

Все сервисы каталога по отраслям, со сценариями. Используй, если search ничего не нашёл или нужно выбрать сервис.

Input parameters:

- `industry` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ru-mcp-everything-russian-apis/mcp-everything#diagnostics

## Score history

- 2026-11-22: 81
- 2026-11-21: 81
- 2026-11-20: 80
- 2026-11-19: 80
- 2026-11-18: 79
- 2026-11-17: 79
- 2026-11-16: 78
- 2026-11-15: 78
- 2026-11-14: 23
- 2026-11-13: 76
- 2026-11-12: 76
- 2026-11-11: 76
- 2026-11-10: 76
- 2026-11-09: 75
- 2026-11-08: 75
- 2026-11-07: 74
- 2026-11-06: 74
- 2026-11-05: 73
- 2026-11-04: 73
- 2026-11-03: 72
- 2026-11-02: 72
- 2026-11-01: 71
- 2026-10-31: 71
- 2026-10-30: 70
- 2026-10-29: 70
- 2026-10-28: 69
- 2026-10-27: 69
- 2026-10-26: 69
- 2026-10-25: 68
- 2026-10-24: 68

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp-everything.ru/mcp
- Website: https://mcp-everything.ru/connect
- Changelog RSS feed: https://verifymcp.io/servers/ru-mcp-everything-russian-apis/mcp-everything.xml
- Changelog JSON feed: https://verifymcp.io/servers/ru-mcp-everything-russian-apis/mcp-everything/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ru-mcp-everything-russian-apis/mcp-everything.json
- HTML version of this page: https://verifymcp.io/servers/ru-mcp-everything-russian-apis/mcp-everything
