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 · DESIGN-EVENTS.FUN

Афиша для дизайнеров: лекции, митапы, выставки. Поиск по городу, датам, теме, только чтение.

+3 this week 73 Trust /100

Last scanned (3 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Entertainment and Games

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 Security80
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 961 tokens (~240/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 Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 79% of tool parameters carry a description.Partial
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
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.

  • 4 Nov 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.

  • 2 Nov 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.

  • 1 Nov 26 +38
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • Authorization: fail → partial ▲ security
    • HSTS header: fail → pass ▲ security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: behind authorisation → reachable ▲ functional
    • Stability: unverified → 0.23 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
  • 31 Oct 26 −37
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • Stability: 0.17 → unverified ▼ security
    • Authorization: partial → fail ▼ security
    • HSTS header: pass → fail ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 28 Oct 26 +1

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

  • 26 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 25 Oct 26 68

    First indexed and scored.

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 5 Nov 2026 · Probed https://design-events.fun/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=design-events.fun CN=YE1,O=Let's Encrypt,C=US 12 Oct 2026 10 Jan 2027 ECDSA 256 ECDSA-SHA384 64e00885474726d801aabfd9cd999be9cc0
SANs: design-events.fun, www.design-events.fun
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 design-events.fun. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
fun. present 47728 13 Verified
design-events.fun. 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=63072000
x-content-type-options nosniff
x-frame-options SAMEORIGIN

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://design-events.fun/mcp Verified 200
http (plaintext) http://design-events.fun/mcp HTTPS enforced 301 https://design-events.fun/mcp
MCP tools · 4 exposed · ~835 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
get_event ~114

Полная карточка события по id из адреса design-events.fun/event/<id> (или по самому адресу): описание (текст организатора, обрезан до 3000 знаков), время в поясе события, город, формат, направления, ссылка на карточку и на регистрацию, площадка и организатор именами, если подтверждены. У прошедшего события past: true — карточка остаётся архивной страницей.

NameTypeReqDescription
idstringyesid события, как в url карточки.

No output schema declared.

No examples provided.

list_directions ~34

Направления (темы) афиши: slug для search_events.directions, название и страница направления на сайте.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

plan_my_week ~74

Pro, ранний доступ: личный недельный план по интересам и городу. Pro ещё не открыт — инструмент отвечает ссылкой на заявку. Не обещайте пользователю готовый план из этого инструмента; соберите его сами через search_events.

NameTypeReqDescription
citystring––
interestsarray––

No output schema declared.

No examples provided.

search_events ~613

События афиши в окне дат: город, онлайн или офлайн, направление, формат, поиск по тексту. Окно по умолчанию — 7 дней с сегодняшнего дня по Москве; задан только date_from — 7 дней от него; только date_to — с сегодня до date_to. Подставленные даты перечислены в applied_filters.defaulted_dates. Отбор — по пересечению интервала события с окном; сначала события, начинающиеся в окне (по началу), затем длящиеся — выставки и т. п. (по дате окончания). Серии — одной карточкой. По умолчанию отдаются только будущие и идущие события; прошедшие (past: true) — только если окно начинается раньше сегодняшнего дня по Москве (не глубже 60 дней). Ответ: краткие карточки (полное описание отдаёт get_event), total, next_cursor для следующей страницы, data_freshness. Если data_freshness = «резервная копия», живой список не прочитался и части событий может не быть — скажите об этом пользователю. Цен и статуса регистрации в данных нет.

NameTypeReqDescription
citystring–Город, без регистра; «Питер», «СПб» → Санкт-Петербург.
cursorstring–next_cursor из предыдущего ответа, с теми же фильтрами.
date_fromstring–Начало окна, YYYY-MM-DD, по Москве, включительно; по умолчанию сегодня. Не раньше 60 дней назад.
date_tostring–Конец окна, YYYY-MM-DD, по Москве, включительно; по умолчанию date_from + 6 дней. Окно не больше 92 дней.
directionsarray–Направления, любое из: ux, ai, brand, marketing, business, typography, books, vibecoding, gamedev, art-direction, illustration, collage, photography, visualization, video, architecture, product-desig…
formatstring–Формат, точное значение: Выставка, Лекция, Воркшоп / мастер-класс, Конференция, Фестиваль, Экскурсия, Митап, Дискуссия, Кинопоказ, Интенсив, Презентация, Маркет, Хакатон, День открытых дверей, Конкур…
include_ongoingboolean–Включать события, начавшиеся до окна и ещё идущие.
include_onlineboolean–При заданном городе добавлять онлайн-события.
limitinteger––
modestring–Только офлайн или только онлайн.
querystring–Подстрока в заголовке или описании, без регистра.

No output schema declared.

No examples provided.

Install

How do I install the Дизайн-афиша MCP server?

Дизайн-афиша is a hosted endpoint at https://design-events.fun/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 · design-events.fun

# add to Claude Code
claude mcp add --transport http fun-design-events-afisha 'https://design-events.fun/mcp'
Common questions

What is the Дизайн-афиша MCP server?

Дизайн-афиша is an MCP server listed in the public MCP registry as fun.design-events/afisha. Афиша для дизайнеров: лекции, митапы, выставки. Поиск по городу, датам, теме, только чтение. This page covers its hosted endpoint (https://design-events.fun/mcp).

Is the Дизайн-афиша MCP server safe to use?

Дизайн-афиша scores 73 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 4 tools: search_events, get_event, list_directions, plan_my_week. Their descriptions and schemas cost roughly 835 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.