# Ploshadkin — event venues in Russia (remote · ploshadkin.ru)

Event venues in Russia: restaurants, lofts, hotel halls, country clubs. Capacity, prices, requests.

- Trust score: 33/100 (low)
- Change this week: −39
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `ploshadkin.ru`: 33/100 (this document), [markdown](https://verifymcp.io/servers/ru-ploshadkin-venues/ploshadkin.md), [page](https://verifymcp.io/servers/ru-ploshadkin-venues/ploshadkin)

## Channel facts

- Endpoint: `https://ploshadkin.ru/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.0.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-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - 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**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

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

## Install

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

### Claude

```bash
claude mcp add --transport http ru-ploshadkin-venues 'https://ploshadkin.ru/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ru-ploshadkin-venues": {
      "url": "https://ploshadkin.ru/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ru-ploshadkin-venues": {
      "type": "http",
      "url": "https://ploshadkin.ru/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ru-ploshadkin-venues]
url = "https://ploshadkin.ru/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ru-ploshadkin-venues --url 'https://ploshadkin.ru/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ru-ploshadkin-venues:
    url: "https://ploshadkin.ru/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ru-ploshadkin-venues": {
      "Transport": "http",
      "Url": "https://ploshadkin.ru/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ru-ploshadkin-venues -t streamable-http -u 'https://ploshadkin.ru/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ru-ploshadkin-venues": {
      "type": "http",
      "url": "https://ploshadkin.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-04 (score 33, −40)

- [security regression] Endpoint reachability: unreachable → behind authorisation
- [security regression] HSTS header: unverified → fail
- [security regression] Authorization: unverified → fail
- [security regression] Transport: fail → unverified
- [security improvement] TLS certificate: unverified → pass
- [security] Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] 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.

### 2026-11-03 (score 73, 0)

- [security regression] DNSSEC: unverified → fail

### 2026-11-02 (score 73, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] DNSSEC: fail → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Stability: 0.43 → 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: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-01 (score 73, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-31 (score 73, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-30 (score 72, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

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

### 2026-10-28 (score 71, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

## MCP tools (5)

### `search_venues` (~336 tokens)

Поиск площадок

Поиск по каталогу Площадкин по словам и фильтрам. Возвращает до 10 карточек: slug, название, рубрика, город, адрес, вместимость (банкет/фуршет/театр/максимум), ориентир цены, короткое описание, фото, ссылка. Порядок — рекомендованные каталогом, затем по популярности. Подробности — get_venue.

Input parameters:

- `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): корпоратив, новый год, конференция, свадьба, с проживанием, своя кухня…

### `get_venue` (~106 tokens)

Карточка площадки

Подробная карточка площадки: описание, залы и вместимость по рассадкам, цена-ориентир, кухня, парковка, проживание, поводы, фото, другие залы комплекса, ссылка. Контакты не выдаются — для свободной даты и сметы используйте request_quote.

Input parameters:

- `slug` (string): slug из search_venues
- `url` (string): Или ссылка на карточку площадки на ploshadkin.ru

### `list_categories` (~61 tokens)

Рубрики и поводы

Рубрики площадок (slug, название, число площадок, ссылка) и теги — поводы (корпоратив, новый год, конференция…) и особенности (с проживанием, своя кухня…) для фильтров search_venues.

### `list_cities` (~24 tokens)

Города

Города каталога: slug, название, число площадок, ссылка.

### `request_quote` (~217 tokens)

Заявка: свободная дата и смета

Отправить агентству заявку: проверить свободную дату площадки и прислать смету (одной площадки или подбор). Нужны имя и телефон пользователя — спросите их и получите согласие на передачу. Агентство перезвонит в течение рабочего дня. Не больше 3 заявок в сутки.

Input parameters:

- `city` (string): Город мероприятия
- `comment` (string): Бюджет, пожелания
- `email` (string): E-mail (необязательно)
- `event_date` (string): Дата мероприятия, ГГГГ-ММ-ДД
- `format` (string): Формат: банкет, фуршет, конференция, корпоратив…
- `guests` (integer): Число гостей
- `name` (string, required): Имя пользователя
- `phone` (string, required): Телефон, например +7 900 000-00-00
- `venue` (string): slug площадки из search_venues (если заявка на конкретную)

## Diagnostics

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

## Score history

- 2026-11-05: 33
- 2026-11-04: 33
- 2026-11-03: 73
- 2026-11-02: 73
- 2026-11-01: 73
- 2026-10-31: 73
- 2026-10-30: 72
- 2026-10-29: 72
- 2026-10-28: 71
- 2026-10-27: 71
- 2026-10-26: 70
- 2026-10-25: 70
- 2026-10-24: 70
- 2026-10-23: 69
- 2026-10-22: 69
- 2026-10-21: 68
- 2026-10-20: 68
- 2026-10-19: 67

## Common questions

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

## Links

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