ESEO — карточки Wildberries, Ozon, Яндекс Маркет
REMOTE · ESEO.SU
SEO score and checks for Wildberries, Ozon, Yandex Market product cards; AI card generation.
Available components
Last scanned (2 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 1 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 809 tokens (~202/item across 4 items; 4 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 Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Tool “check_description” rewrote its description, which is the text the model reads security
- Tool “generate_card” rewrote its description, which is the text the model reads security
- Tool “marketplace_limits” rewrote its description, which is the text the model reads security
- Tool “score_card” rewrote its description, which is the text the model reads security
- Schema quality: 153 → 202 ▼ functional
- Schema quality: good → excellent functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 5 Nov 2026 · Probed https://eseo.su/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=eseo.su | CN=YE1,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6166a19b3f183597075414e6756b43effad |
| SANs: eseo.su, www.eseo.su | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 eseo.su. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| su. | present | 42982 | 8 | Verified |
| eseo.su. | 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 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://mc.yandex.ru https://mc.yandex.com https://yandex.ru 'wasm-unsafe-eval' blob:; style-src 'self' 'unsafe-inline'; font-src 'self' data:; img-src 'self' data: blob: https://mc.yandex.ru https://mc.yandex.com https://avatars.yandex.net https://storage.yandexcloud.net https://eseo-images.storage.yandexcloud.net https://cdn.jsdelivr.net https://*.wbbasket.ru https://*.mds.yandex.net; connect-src 'self' https://storage.yandexcloud.net https://mc.yandex.ru https://mc.yandex.com https://oauth.yandex.ru https://login.yandex.ru https://errors.eseo.su wss: https://cdn.jsdelivr.net; worker-src 'self' blob:; media-src 'self' https://storage.yandexcloud.net; object-src 'none'; frame-src 'self' blob: https://mc.yandex.ru; frame-ancestors 'self' https://metrika.yandex.ru https://*.metrika.yandex.ru https://webvisor.com https://*.webvisor.com https://mc.yandex.ru; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://eseo.su/api/mcp | Verified | 200 | |
| http (plaintext) | http://eseo.su/api/mcp | HTTPS enforced | 301 | https://eseo.su/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 →
check_description Проверка описания ~165
Проверяет ТОЛЬКО текст описания товара: длина под площадку, конкретика, переспам ключей, запрещённые слова, AI-клише. Балл описания 0–100 и список замечаний. Когда звать: есть одно описание (черновик, правка) и нужно понять, что в нём исправить. Не для оценки всей карточки с названием и пунктами — для неё score_card. Только чтение, бесплатно, без ключа.
| Name | Type | Req | Description |
|---|---|---|---|
| marketplace | string | – | Площадка: WB — Wildberries, OZON — Ozon, YANDEX_MARKET — Яндекс Маркет, AVITO — Авито. По умолчанию WB. |
| text | string | yes | Текст описания |
No output schema declared.
No examples provided.
generate_card Сгенерировать SEO-карточку ~184
Создаёт новую SEO-карточку товара для Wildberries, Ozon или Яндекс Маркета: название, описание, пункты, ключевые слова и SEO-балл нашего движка. Когда звать: карточки ещё нет или её нужно написать заново по названию и характеристикам. Не для оценки существующей карточки — для неё score_card (бесплатно). Нужен API-ключ ESEO (платный тариф) в заголовке Authorization: Bearer eseo_…; лимит 10 запросов в минуту.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | Товар: название и важные характеристики (3–500 символов) |
| marketplace | string | – | Площадка: WB — Wildberries, OZON — Ozon, YANDEX_MARKET — Яндекс Маркет. По умолчанию WB. |
No output schema declared.
No examples provided.
marketplace_limits Лимиты площадки ~143
Справка по лимитам карточки площадки: жёсткий максимум названия, максимум слова (Ozon), рекомендуемые диапазоны названия и описания, число пунктов. Когда звать: перед тем как писать или сокращать название и описание вручную. Не для проверки готового текста — для неё score_card (вся карточка) или check_description (описание). Только чтение, бесплатно, без ключа.
| Name | Type | Req | Description |
|---|---|---|---|
| marketplace | string | – | Площадка: WB — Wildberries, OZON — Ozon, YANDEX_MARKET — Яндекс Маркет, AVITO — Авито. По умолчанию WB. |
No output schema declared.
No examples provided.
score_card SEO-балл карточки ~204
Оценивает карточку товара ЦЕЛИКОМ (название + описание + пункты) по правилам площадки: SEO-балл 0–100, разбор по факторам и подсказки, что исправить. Тот же движок, что на eseo.su. Когда звать: нужна общая оценка готовой карточки или сравнение двух версий. Не для одного текста описания — для него check_description; не для создания карточки — generate_card. Только чтение, бесплатно, без ключа.
| Name | Type | Req | Description |
|---|---|---|---|
| bullets | array | – | Пункты-преимущества (до 20) |
| description | string | – | Описание товара |
| marketplace | string | – | Площадка: WB — Wildberries, OZON — Ozon, YANDEX_MARKET — Яндекс Маркет, AVITO — Авито. По умолчанию WB. |
| title | string | yes | Название товара |
No output schema declared.
No examples provided.
How do I install the ESEO — карточки Wildberries, Ozon, Яндекс Маркет MCP server?
ESEO — карточки Wildberries, Ozon, Яндекс Маркет is a hosted endpoint at https://eseo.su/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 · eseo.su
claude mcp add --transport http su-eseo-mcp 'https://eseo.su/api/mcp'
What is the ESEO — карточки Wildberries, Ozon, Яндекс Маркет MCP server?
ESEO — карточки Wildberries, Ozon, Яндекс Маркет is an MCP server listed in the public MCP registry as su.eseo/mcp. SEO score and checks for Wildberries, Ozon, Yandex Market product cards; AI card generation. This page covers its hosted endpoint (https://eseo.su/api/mcp).
Is the ESEO — карточки Wildberries, Ozon, Яндекс Маркет MCP server safe to use?
ESEO — карточки Wildberries, Ozon, Яндекс Маркет scores 72 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 ESEO — карточки Wildberries, Ozon, Яндекс Маркет MCP server expose?
ESEO — карточки Wildberries, Ozon, Яндекс Маркет exposes 4 tools: score_card, check_description, marketplace_limits, generate_card. Their descriptions and schemas cost roughly 696 tokens of context every time the server is loaded.
Does the ESEO — карточки Wildberries, Ozon, Яндекс Маркет MCP server require authentication?
No. We connected to ESEO — карточки Wildberries, Ozon, Яндекс Маркет without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ESEO — карточки Wildberries, Ozon, Яндекс Маркет MCP server still maintained?
ESEO — карточки Wildberries, Ozon, Яндекс Маркет is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.