Ploshadkin — event venues in Russia
REMOTE · PLOSHADKIN.RU
Event venues in Russia: restaurants, lofts, hotel halls, country clubs. Capacity, prices, requests.
Available components
Last scanned (22 hours ago)
Scores higher than 16% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 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. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (5)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
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.
- 4 Nov 26 −40
- Endpoint reachability: unreachable → behind authorisation ▼ security
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → fail ▼ security
- Transport: fail → unverified ▼ security
- TLS certificate: unverified → pass ▲ security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- 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
- Stability: 0.43 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 1 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 31 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 30 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 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.
- 28 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
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://ploshadkin.ru/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=artist24.ru | CN=YE2,O=Let's Encrypt,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 67439b4b653e4c298fa7f6b5a921b4220ed |
| SANs: artist24.ru, event-ploshadki.ru, gdeprovesti.ru, ploshadkin.ru, www.artist24.ru, www.event-ploshadki.ru, www.gdeprovesti.ru, www.ploshadkin.ru, www.zakazat-zvezdu.ru, zakazat-zvezdu.ru | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 ploshadkin.ru. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ru. | DS published | 26734 | 8 | Verified |
| ploshadkin.ru. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 403 |
| Header | Value |
|---|---|
| content-security-policy | frame-ancestors 'self'; object-src 'none'; base-uri 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ploshadkin.ru/mcp | Auth required | 403 | |
| http (plaintext) | http://ploshadkin.ru/mcp | HTTPS enforced | 301 | https://ploshadkin.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_venue Карточка площадки ~106
Подробная карточка площадки: описание, залы и вместимость по рассадкам, цена-ориентир, кухня, парковка, проживание, поводы, фото, другие залы комплекса, ссылка. Контакты не выдаются — для свободной даты и сметы используйте request_quote.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | – | slug из search_venues |
| url | string | – | Или ссылка на карточку площадки на ploshadkin.ru |
No output schema declared.
No examples provided.
list_categories Рубрики и поводы ~61
Рубрики площадок (slug, название, число площадок, ссылка) и теги — поводы (корпоратив, новый год, конференция…) и особенности (с проживанием, своя кухня…) для фильтров search_venues.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_cities Города ~24
Города каталога: slug, название, число площадок, ссылка.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_quote Заявка: свободная дата и смета ~217
Отправить агентству заявку: проверить свободную дату площадки и прислать смету (одной площадки или подбор). Нужны имя и телефон пользователя — спросите их и получите согласие на передачу. Агентство перезвонит в течение рабочего дня. Не больше 3 заявок в сутки.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Город мероприятия |
| comment | string | – | Бюджет, пожелания |
| string | – | E-mail (необязательно) | |
| event_date | string | – | Дата мероприятия, ГГГГ-ММ-ДД |
| format | string | – | Формат: банкет, фуршет, конференция, корпоратив… |
| guests | integer | – | Число гостей |
| name | string | yes | Имя пользователя |
| phone | string | yes | Телефон, например +7 900 000-00-00 |
| venue | string | – | slug площадки из search_venues (если заявка на конкретную) |
No output schema declared.
No examples provided.
search_venues Поиск площадок ~336
Поиск по каталогу Площадкин по словам и фильтрам. Возвращает до 10 карточек: slug, название, рубрика, город, адрес, вместимость (банкет/фуршет/театр/максимум), ориентир цены, короткое описание, фото, ссылка. Порядок — рекомендованные каталогом, затем по популярности. Подробности — get_venue.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Рубрика: slug или название из list_categories («лофт», «ресторан», «конференц-зал», «теплоход») |
| city | string | – | Город: slug или название из list_cities («Москва», «спб») |
| country | boolean | – | Только загородные площадки |
| guests | integer | – | Сколько гостей должно поместиться (по максимальной вместимости площадки) |
| limit | integer | – | Карточек за вызов (до 10) |
| page | integer | – | Страница выдачи (не дальше 5-й — дальше уточняйте фильтрами) |
| price_max | integer | – | Бюджет банкета на гостя до, ₽ (площадки без указанной цены тоже попадают) |
| q | string | – | Название или слова: «Сенкевич», «лофт с террасой», «ресторан у воды» |
| tags | array | – | Повод или особенность (slug или название из list_categories → tags): корпоратив, новый год, конференция, свадьба, с проживанием, своя кухня… |
No output schema declared.
No examples provided.
How do I install the Ploshadkin — event venues in Russia MCP server?
Ploshadkin — event venues in Russia is a hosted endpoint at https://ploshadkin.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 · ploshadkin.ru
claude mcp add --transport http ru-ploshadkin-venues 'https://ploshadkin.ru/mcp'
What is the Ploshadkin — event venues in Russia MCP server?
Ploshadkin — event venues in Russia is an MCP server listed in the public MCP registry as ru.ploshadkin/venues. Event venues in Russia: restaurants, lofts, hotel halls, country clubs. Capacity, prices, requests. This page covers its hosted endpoint (https://ploshadkin.ru/mcp).
Is the Ploshadkin — event venues in Russia MCP server safe to use?
Ploshadkin — event venues in Russia scores 33 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 Ploshadkin — event venues in Russia MCP server expose?
Ploshadkin — event venues in Russia exposes 5 tools: search_venues, get_venue, list_categories, list_cities, request_quote. Their descriptions and schemas cost roughly 744 tokens of context every time the server is loaded.
Does the Ploshadkin — event venues in Russia MCP server require authentication?
Yes. Ploshadkin — event venues in Russia asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Ploshadkin — event venues in Russia MCP server still maintained?
Ploshadkin — event venues in Russia 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.
What did VerifyMCP test on the Ploshadkin — event venues in Russia MCP server?
VerifyMCP ran 5 checks on Ploshadkin — event venues in Russia, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Ploshadkin — event venues in Russia: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. 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.