Bloody Mary Bar & Grill
REMOTE · GO.BLOODYMARYBAR.RU
Часы, меню, акции, бронь и заявки на банкет: Bloody Mary Bar & Grill, Санкт-Петербург.
Available components
Last scanned (23 hours ago)
Scores higher than 42% of remote servers
Unreachable for 3 days in a row. Last reached 1 Nov 2026.
Category E-commerce
Degraded
One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 3 Nov 26 0
- DNSSEC: unverified → fail ▼ security
- 2 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Stability: 0.20 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 26 Oct 26 66
First indexed and scored.
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 4 Nov 2026 · Probed https://go.bloodymarybar.ru/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of go.bloodymarybar.ru. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ru. | present | 26734 | 8 | Verified |
| bloodymarybar.ru. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://go.bloodymarybar.ru/mcp | Unreachable | ||
| http (plaintext) | http://go.bloodymarybar.ru/mcp | HTTPS enforced |
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_banquets_and_events ~53
Банкеты, корпоративы, праздники и мероприятия: форматы, вместимость, условия, ссылки и как отправить заявку (submit_inquiry). Banquets, corporate events and how to inquire.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_hours ~82
Часы работы (Europe/Moscow, 24 ч): зала, кухни и бара. С датой - часы на этот день; без даты - сегодня, открыто ли сейчас и неделя. Opening hours (Moscow time).
| Name | Type | Req | Description |
|---|---|---|---|
| date | – | – | Необязательная дата YYYY-MM-DD (Europe/Moscow). Без даты - сегодня и вся неделя. |
No output schema declared.
No examples provided.
get_kids_menu ~36
Детское меню и условия для гостей с детьми (если есть у этого ресторана). Kids menu, if the restaurant has one.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_loyalty_info ~34
Клуб друзей / программа лояльности: условия, уровни, как вступить. Loyalty club info.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_menu ~111
Меню с ценами в рублях (по данным кассы, с НДС). Без аргументов - обзор меню и разделов; с section - позиции раздела. Алкоголь помечен 18+. Menu with RUB prices; alcohol is 18+.
| Name | Type | Req | Description |
|---|---|---|---|
| section | – | – | Название меню или раздела, например 'бар', 'коктейли', 'горячее', 'десерты', 'детское'. Без аргумента - обзор меню и разделов. |
No output schema declared.
No examples provided.
get_order_link ~36
Доставка и заказ навынос: ссылка, условия, телефон (если у ресторана есть). Delivery / takeaway link, if available.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_reservation_link ~74
Как забронировать стол: страница/виджет бронирования и телефон. Глубокой ссылки на дату нет - гость выбирает дату и время на странице. How to reserve a table.
| Name | Type | Req | Description |
|---|---|---|---|
| date | – | – | Необязательная дата визита YYYY-MM-DD - чтобы проверить часы работы в этот день. |
No output schema declared.
No examples provided.
get_restaurant_info ~50
Основные сведения о ресторане: адрес, метро, телефон, сайт, кухня, особенности, рейтинг, ключевые ссылки. Basic facts: address, phone, website, cuisine, features, links.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_specials ~88
Акции, бизнес-ланчи и спецпредложения. С днём - только то, что действует в этот день, плюс предложения без привязки к дню. Promotions and lunch offers.
| Name | Type | Req | Description |
|---|---|---|---|
| day | – | – | День недели ('суббота', 'saturday'), 'сегодня', 'завтра' или YYYY-MM-DD. Без аргумента - все акции. |
No output schema declared.
No examples provided.
search_menu ~83
Поиск по названию и описанию позиций меню (все слова должны совпасть). До 15 позиций с ценами в рублях. Search menu items by name.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Блюдо или напиток, например 'брискет', 'пастрома', 'Кровавая Мэри', 'пиво'. |
No output schema declared.
No examples provided.
submit_inquiry ~309
Отправить заявку (банкет / корпоратив / группа / бронь) команде ресторана. Вызывать ТОЛЬКО если человек сам просит связаться, назвал имя и телефон и согласился на обработку персональных данных (consent_personal_data=true) - без согласия заявка не принимается. Ресторан перезвонит. Send an inquiry; needs explicit personal-data consent (152-FZ).
| Name | Type | Req | Description |
|---|---|---|---|
| company_website | – | – | Антиспам-ловушка. ОСТАВЬТЕ ПУСТЫМ. Никогда не заполняйте. |
| consent_personal_data | boolean | yes | Явное согласие гостя на обработку персональных данных (152-ФЗ). Ставьте true ТОЛЬКО если гость сам согласился; иначе заявка отклоняется. |
| date | – | – | Желаемая дата или период (текст, например '2026-12-18'). |
| guests | – | – | Примерное число гостей (1-200). |
| message | – | – | Детали: повод, пожелания, бюджет (до 1000 символов). |
| name | string | yes | Имя контактного лица. |
| phone | string | yes | Телефон для связи, например +7 999 123-45-67. |
| type | string | yes | Вид заявки: banquet (банкет), corporate (корпоратив), group (группа), reservation_request (запрос на бронь). |
No output schema declared.
No examples provided.
How do I install the Bloody Mary Bar & Grill MCP server?
Bloody Mary Bar & Grill is a hosted endpoint at https://go.bloodymarybar.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 · go.bloodymarybar.ru
claude mcp add --transport http ru-bloodymarybar-go-bloody-mary 'https://go.bloodymarybar.ru/mcp'
What is the Bloody Mary Bar & Grill MCP server?
Bloody Mary Bar & Grill is an MCP server listed in the public MCP registry as ru.bloodymarybar.go/bloody-mary. Часы, меню, акции, бронь и заявки на банкет: Bloody Mary Bar & Grill, Санкт-Петербург. This page covers its hosted endpoint (https://go.bloodymarybar.ru/mcp).
Is the Bloody Mary Bar & Grill MCP server safe to use?
Bloody Mary Bar & Grill scores 54 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 Bloody Mary Bar & Grill MCP server expose?
Bloody Mary Bar & Grill exposes 11 tools: get_restaurant_info, get_hours, get_menu, search_menu, get_specials, and 6 more. Their descriptions and schemas cost roughly 956 tokens of context every time the server is loaded.
Does the Bloody Mary Bar & Grill MCP server require authentication?
Its publisher declares no required credentials for Bloody Mary Bar & Grill. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Bloody Mary Bar & Grill MCP server still maintained?
Bloody Mary Bar & Grill is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 1 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.