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.

АЛИАС — арт-кондитерская, Санкт-Петербург

REMOTE · ALIASBAKERY.RU

Торты, пряники и десерты на заказ в Петербурге: каталог, цены, расчёт торта, доставка, заявки

Available components

+4 this week 80 Trust /100

Last scanned (17 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

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 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
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2010 tokens (~154/item across 13 items; 13 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 Management77
  • Stability observed for 23 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 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 (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 →

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 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 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 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.

  • 13 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.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://aliasbakery.ru/mcp

TLS valid

Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aliasbakery.ru CN=YR2,O=Let's Encrypt,C=US 8 Oct 2026 6 Jan 2027 RSA 2048 SHA256-RSA 5771a243ad5bf15a1fdde2b2aea3b55a853
SANs: *.aliasbakery.ru, aliasbakery.ru
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 aliasbakery.ru. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ru. DS published 26734 8 Verified
aliasbakery.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
Header Value
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(self), microphone=(), camera=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://aliasbakery.ru/mcp Verified 200
http (plaintext) http://aliasbakery.ru/mcp HTTPS enforced 301 https://aliasbakery.ru/mcp
MCP tools · 13 exposed · ~1,660 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
about ~34

Кто мы, контакты, адрес, часы работы, рейтинг, оплата, доставка, как проходит заказ. Начните с этого.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

book_tasting ~285

Записать заказчика на дегустацию начинок. День и время подтверждает менеджер. Перед отправкой получите согласие заказчика на обработку данных.

NameTypeReqDescription
assistantstring–Как называется ваш ассистент (ChatGPT, Алиса, Claude…) — менеджер увидит, откуда заявка
commentstring–Повод, число гостей, пожелания
consentbooleanyesЗаказчик согласился на обработку персональных данных по политике https://aliasbakery.ru/privacy.php. Спросите его до отправки.
datestringyesЖелаемая дата дегустации, ГГГГ-ММ-ДД или ДД.ММ.ГГГГ
emailstring–Почта (необязательно)
event_datestring–Дата самого праздника, если известна
fillingsarray–До 6 начинок для пробы (названия из list_fillings)
formatstring–Как удобнее: в мастерской, самовывоз набора или доставка набора
namestringyesИмя заказчика
phonestringyesТелефон заказчика, с кодом страны
timestring–Желаемое время, 12:00–18:00

No output schema declared.

No examples provided.

check_date ~53

Принимаем ли заказ на дату и есть ли наценка за срочность.

NameTypeReqDescription
datestringyesДата, ГГГГ-ММ-ДД или ДД.ММ.ГГГГ

No output schema declared.

No examples provided.

decor_list ~30

Фигурки, топперы, свечи и другой декор к торту с ценами.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

delivery_quote ~47

Цена доставки по адресу (площадка, дом) в Санкт-Петербурге и Ленинградской области. Без адреса — общие условия.

NameTypeReqDescription
addressstring–Адрес доставки

No output schema declared.

No examples provided.

estimate_cake ~299

Расчёт торта: вес по числу гостей (или заданный), цена за кг по оформлению, наценка за начинки, срочность по дате. Цена за кг не зависит от числа ярусов — ярусы зависят от веса и согласуются с кондитером.

NameTypeReqDescription
candy_barboolean–На празднике есть кэнди-бар (вес меньше на четверть)
datestring–Дата праздника, ГГГГ-ММ-ДД или ДД.ММ.ГГГГ
decorationstring–Оформление: cream — гладкий крем без украшений; naked — «голые» коржи; flowers — крем с живыми цветами или ягодами; velour — велюр, дорогие цветы и декор; mastic — мастика или шоколадное покрытие. Не…
fillings_countinteger–Сколько разных начинок
guestsinteger–Число гостей
occasionstring–Повод — чтобы дать ссылку на нужный раздел
premium_fillingboolean–Есть премиальная начинка (см. list_fillings)
weight_kgnumber–Вес торта, кг (если известен; иначе считается по гостям)

No output schema declared.

No examples provided.

list_fillings ~37

Начинки для тортов с описанием и правилами: премиальные, только целым тортом, наценки.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

product_details ~43

Описание, цена, минимальный вес или тираж, вопросы и ответы по конкретному изделию (slug из search_products).

NameTypeReqDescription
slugstringyesslug изделия

No output schema declared.

No examples provided.

quote_gingerbread ~178

Без параметров — размеры, виды росписи, типы и упаковка. С параметрами — цена за штуку на ступенях тиража и итог вместе с упаковкой. Свадьба: пряники с именами для рассадки — обычно стандартный размер, простая или средняя роспись; список имён менеджер возьмёт после заявки.

NameTypeReqDescription
kind_idinteger–Тип пряника (id), по умолчанию плоский
level_idinteger–Роспись (id)
packaging_idinteger–Упаковка (id), по умолчанию пакетик с запайкой
qtyinteger–Тираж, шт
size_idinteger–Размер (id из справочника)

No output schema declared.

No examples provided.

read_guides ~61

Ответы из статей блога и раздела «Вопросы и ответы»: сколько торта на гостей, как выбрать начинку, свадебные пряники, срочный заказ и другое.

NameTypeReqDescription
querystringyesВопрос или тема

No output schema declared.

No examples provided.

search_products ~204

Поиск по каталогу: торты, пряники, капкейки, десерты, подарки. Возвращает до 10 позиций с фото, ценой и ссылкой. Если по всем условиям пусто, сервер сам ослабит условия и скажет, какие.

NameTypeReqDescription
colorstring–Основной цвет торта
limitinteger–Сколько позиций вернуть, 1–10
max_priceinteger–Верхняя граница цены за кг (торты) или за штуку, ₽
occasionstring–Повод
querystring–Слова для поиска: «единорог», «логотип», «сухоцветы». Не повторяйте здесь раздел и повод — для них есть свои поля
sectionstring–Раздел каталога
tiersinteger–Число ярусов торта, 1–4

No output schema declared.

No examples provided.

submit_request ~365

Передать заявку менеджеру кондитерской. Это не оплата и не подтверждение заказа: менеджер перезвонит, уточнит детали и назовёт точную цену. Перед отправкой получите согласие заказчика на обработку данных.

NameTypeReqDescription
assistantstring–Как называется ваш ассистент (ChatGPT, Алиса, Claude…) — менеджер увидит, откуда заявка
budgetstring–Бюджет, если назвали
consentbooleanyesЗаказчик согласился на обработку персональных данных по политике https://aliasbakery.ru/privacy.php. Спросите его до отправки.
decorationstring–Если изделие не выбрано: оформление торта
delivery_addressstring–Адрес доставки (площадка). Пусто — самовывоз
emailstring–Почта (необязательно)
event_datestringyesДата праздника, ГГГГ-ММ-ДД или ДД.ММ.ГГГГ
guestsinteger–Число гостей
itemsarray–Выбранные изделия (slug из search_products). Можно пусто — тогда опишите торт в wishes.
namestringyesИмя заказчика
phonestringyesТелефон заказчика, с кодом страны
timestring–Желаемое время доставки или самовывоза, например 15:00
wants_tastingboolean–Хотят сначала дегустацию
wishesstring–Пожелания: описание торта, цвета, повод, что ещё интересует (пряники, капкейки)

No output schema declared.

No examples provided.

tasting_info ~24

Как проходит дегустация начинок, сколько стоит и как записаться.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the АЛИАС — арт-кондитерская, Санкт-Петербург MCP server?

АЛИАС — арт-кондитерская, Санкт-Петербург is a hosted endpoint at https://aliasbakery.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 · aliasbakery.ru

# add to Claude Code
claude mcp add --transport http ru-aliasbakery-bakery 'https://aliasbakery.ru/mcp'
Common questions

What is the АЛИАС — арт-кондитерская, Санкт-Петербург MCP server?

АЛИАС — арт-кондитерская, Санкт-Петербург is an MCP server listed in the public MCP registry as ru.aliasbakery/bakery. Торты, пряники и десерты на заказ в Петербурге: каталог, цены, расчёт торта, доставка, заявки. This page covers its hosted endpoint (https://aliasbakery.ru/mcp).

Is the АЛИАС — арт-кондитерская, Санкт-Петербург MCP server safe to use?

АЛИАС — арт-кондитерская, Санкт-Петербург scores 80 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 server expose?

АЛИАС — арт-кондитерская, Санкт-Петербург exposes 13 tools: about, search_products, product_details, list_fillings, estimate_cake, and 8 more. Their descriptions and schemas cost roughly 1,660 tokens of context every time the server is loaded.

Does the АЛИАС — арт-кондитерская, Санкт-Петербург MCP server require authentication?

No. We connected to АЛИАС — арт-кондитерская, Санкт-Петербург without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the АЛИАС — арт-кондитерская, Санкт-Петербург MCP server still maintained?

АЛИАС — арт-кондитерская, Санкт-Петербург 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 АЛИАС — арт-кондитерская, Санкт-Петербург MCP server?

VerifyMCP ran 13 checks on АЛИАС — арт-кондитерская, Санкт-Петербург, 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.