Vedar — Kamchatka travel
REMOTE · VEDARAI.RU · SCANNED SEP 27
Kamchatka travel: live tours and availability, safety alerts, places, weather, stays, trip plans
Available components
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
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2992 tokens (~213/item across 14 items; 14 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 Management33
- Stability observed for 10 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "search_transfers" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 14 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
How do I install the Vedar — Kamchatka travel MCP server?
Vedar — Kamchatka travel is a hosted endpoint at https://vedarai.ru/api/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 · vedarai.ru
claude mcp add --transport http ru-vedarai-mcp 'https://vedarai.ru/api/mcp'
{
"mcpServers": {
"ru-vedarai-mcp": {
"url": "https://vedarai.ru/api/mcp"
}
}
} {
"servers": {
"ru-vedarai-mcp": {
"type": "http",
"url": "https://vedarai.ru/api/mcp"
}
}
} [mcp_servers.ru-vedarai-mcp] url = "https://vedarai.ru/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ru-vedarai-mcp": {
"type": "remote",
"url": "https://vedarai.ru/api/mcp",
"enabled": true
}
}
} openclaw mcp add ru-vedarai-mcp --url 'https://vedarai.ru/api/mcp' --transport streamable-http
mcp_servers:
ru-vedarai-mcp:
url: "https://vedarai.ru/api/mcp" {
"McpServers": {
"ru-vedarai-mcp": {
"Transport": "http",
"Url": "https://vedarai.ru/api/mcp"
}
}
} assistant mcp add ru-vedarai-mcp -t streamable-http -u 'https://vedarai.ru/api/mcp'
{
"mcpServers": {
"ru-vedarai-mcp": {
"type": "http",
"url": "https://vedarai.ru/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 27 Sept 26 +1
- “make_trip_plan” added an optional parameter “rest_days” cosmetic
- “make_trip_plan” added an optional parameter “travel_style” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 26 Sept 26 0
- Tool “get_weather” rewrote its description, which is the text the model reads security
- Schema quality: 2453 → 2846 ▼ functional
- New tool “get_volcano_status” functional
- “get_weather” added an optional parameter “days” cosmetic
- “get_weather” added an optional parameter “lat” cosmetic
- “get_weather” added an optional parameter “lng” cosmetic
- “get_weather” added an optional parameter “place” cosmetic
- 25 Sept 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
- 22 Sept 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.
- 21 Sept 26 0
- “make_trip_plan” added an optional parameter “when” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 20 Sept 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.
- 19 Sept 26 −2
- Tool “create_booking_request” rewrote its description, which is the text the model reads security
- Tool “create_lead” rewrote its description, which is the text the model reads security
- Tool “get_guardian_context” rewrote its description, which is the text the model reads security
- Tool “get_place_info” rewrote its description, which is the text the model reads security
- Tool “get_tour_availability” rewrote its description, which is the text the model reads security
- Tool “get_tour_details” rewrote its description, which is the text the model reads security
- Tool “get_tours” rewrote its description, which is the text the model reads security
- Tool “get_weather” rewrote its description, which is the text the model reads security
- Tool “make_trip_plan” rewrote its description, which is the text the model reads security
- Tool “safety_status” rewrote its description, which is the text the model reads security
- Tool “search_accommodations” rewrote its description, which is the text the model reads security
- Tool “search_gear” rewrote its description, which is the text the model reads security
- Tool “search_transfers” rewrote its description, which is the text the model reads security
- Schema quality: 135 → 181 ▼ functional
- Destructive annotations: pass → 0 functional
- “create_booking_request” reworded the description of “comment” cosmetic
- “create_booking_request” reworded the description of “consent” cosmetic
- “create_booking_request” reworded the description of “date” cosmetic
- “create_booking_request” reworded the description of “name” cosmetic
- “create_booking_request” reworded the description of “participants” cosmetic
- “create_booking_request” reworded the description of “phone” cosmetic
- “create_booking_request” reworded the description of “tour” cosmetic
- “create_lead” reworded the description of “comment” cosmetic
- “create_lead” reworded the description of “consent” cosmetic
- “create_lead” reworded the description of “interest” cosmetic
- “create_lead” reworded the description of “name” cosmetic
- “create_lead” reworded the description of “phone” cosmetic
- “get_guardian_context” reworded the description of “place” cosmetic
- “get_place_info” reworded the description of “name” cosmetic
- “get_tour_availability” reworded the description of “date_from” cosmetic
- “get_tour_availability” reworded the description of “days” cosmetic
- “get_tour_availability” reworded the description of “tour” cosmetic
- “get_tour_details” reworded the description of “name” cosmetic
- “get_tours” reworded the description of “activity_type” cosmetic
- “make_trip_plan” reworded the description of “days” cosmetic
- “make_trip_plan” reworded the description of “interests” cosmetic
- “search_accommodations” reworded the description of “price_max” cosmetic
- “search_accommodations” reworded the description of “type” cosmetic
- “search_accommodations” reworded the description of “zone” cosmetic
- “search_gear” reworded the description of “category” cosmetic
- “search_gear” reworded the description of “price_max” cosmetic
- “search_gear” reworded the description of “query” cosmetic
- “search_transfers” reworded the description of “from” cosmetic
- “search_transfers” reworded the description of “place” cosmetic
- “search_transfers” reworded the description of “seats” cosmetic
- “search_transfers” reworded the description of “to” cosmetic
- Tool “create_booking_request” changed its title: Заявка на бронь тура → Booking request cosmetic
- Tool “create_lead” changed its title: Заявка на подбор тура → Tour request cosmetic
- Tool “get_guardian_context” changed its title: Безопасность места → Place safety cosmetic
- Tool “get_place_info” changed its title: Справка о месте → Place info cosmetic
- Tool “get_tour_availability” changed its title: Свободные даты тура → Tour availability cosmetic
- Tool “get_tour_details” changed its title: Карточка тура → Tour details cosmetic
- Tool “get_tours” changed its title: Каталог туров → Tour catalogue cosmetic
- Tool “get_weather” changed its title: Погода → Weather cosmetic
- Tool “make_trip_plan” changed its title: План поездки → Trip plan cosmetic
- Tool “safety_status” changed its title: Обстановка в крае → Regional safety status cosmetic
- Tool “search_accommodations” changed its title: Жильё → Stays cosmetic
- Tool “search_gear” changed its title: Прокат снаряжения → Gear rental cosmetic
- Tool “search_transfers” changed its title: Трансферы → Transfers cosmetic
- 18 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
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 27 Sept 2026 · Probed https://vedarai.ru/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vedarai.ru | CN=YE2,O=Let's Encrypt,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 53917ccd5e4a7d81fc5e85cec9ed51f1473 |
| SANs: vedarai.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 vedarai.ru. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ru. | present | 26734 | 8 | Verified |
| vedarai.ru. | 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; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://api-maps.yandex.ru https://*.yandex.ru https://mc.yandex.ru https://unpkg.com https://emrldco.com https://www.clarity.ms; style-src 'self' 'unsafe-inline' https://*.yandex.ru https://unpkg.com; img-src 'self' data: https: blob:; connect-src 'self' https://*.yandex.ru https://*.yandex.net https://mc.yandex.ru https://mc.yandex.md wss://mc.yandex.ru https://tile.openstreetmap.org https://*.tile.openstreetmap.org https://s3.twcstorage.ru https://emrldco.com https://www.clarity.ms; font-src 'self' data: https://*.yandex.ru; worker-src 'self' blob:; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vedarai.ru/api/mcp | Verified | 200 | |
| http (plaintext) | http://vedarai.ru/api/mcp | HTTPS enforced | 308 | https://vedarai.ru/api/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 →
create_booking_request Booking request ~373
Booking request for a specific Kamchatka tour on a date; live availability is checked first, human-confirmed by the operator; no payment. No tour chosen yet — use create_lead. Заявка на бронь конкретного тура на дату. Перед вызовом проверь свободные даты через get_tour_availability. Заявку подтверждает оператор по телефону — это не мгновенная бронь и не оплата. Если на дату нет мест, заявка не создаётся и в ответе будут ближайшие свободные даты. Имя и телефон — персональные данные: спроси согласие на их обработку и передай consent: true.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Wishes, questions, group composition. Пожелания, вопросы, состав группы |
| consent | boolean | yes | Explicit consent to process name and phone for this request; ask the person and pass true, otherwise the request is not created. Человек согласен на обработку своих персональных данных (имя, телефон)… |
| date | string | yes | Tour date, YYYY-MM-DD. Дата тура, YYYY-MM-DD |
| name | string | yes | Traveller's name. Имя туриста |
| participants | string | – | Number of people, 1–30; default 1. Сколько человек (1–30). Не сказано — 1. |
| phone | string | yes | Phone for confirmation, required. Телефон для подтверждения (обязателен) |
| tour | string | yes | Tour title or numeric ID from get_tours / get_tour_availability. Название тура или числовой ID (из get_tours / get_tour_availability) |
No output schema declared.
No examples provided.
create_lead Tour request ~293
Tour-selection request for Kamchatka when no specific tour or date is chosen yet; human-confirmed by a manager; not a booking, no payment. Оставить заявку на подбор тура по Камчатке: менеджер платформы свяжется по телефону. Обязательны имя, телефон и описание запроса (даты, состав группы, интересы). Не бронь и не оплата — только заявка. Имя и телефон — персональные данные: спроси у человека согласие на их обработку и передай consent: true, иначе заявка не создаётся.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | yes | The request: dates, group size, interests. Запрос: даты, сколько человек, что интересует |
| consent | boolean | yes | Explicit consent to process name and phone for this request; ask the person and pass true, otherwise the request is not created. Человек согласен на обработку своих персональных данных (имя, телефон)… |
| interest | string | – | Tour or route name, if already chosen. Название тура/маршрута, если уже выбран |
| name | string | yes | Traveller's name. Имя туриста |
| phone | string | yes | Contact phone, required. Телефон для связи (обязателен) |
No output schema declared.
No examples provided.
get_guardian_context Place safety ~134
Kamchatka safety context for a place or route: hazards, active alerts, advice. For plain facts (type, coordinates) use get_place_info. Получить полный контекст места как Хранитель: статус (открыто/закрыто), реалтайм алерты КБГС РАН, опасности, загрузка, традиционные знания о месте. Используй ВСЕГДА когда спрашивают о конкретном месте, вулкане, озере, маршруте, источнике Камчатки.
| Name | Type | Req | Description |
|---|---|---|---|
| place | string | yes | Place or route name. Название места или объекта |
No output schema declared.
No examples provided.
get_place_info Place info ~79
Kamchatka place facts: type, coordinates, hazards, nearby places. For current safety and alerts use get_guardian_context. Найти базовую информацию о месте из базы данных (используй get_guardian_context для полного контекста с безопасностью и алертами).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Place name. Название объекта |
No output schema declared.
No examples provided.
get_tour_availability Tour availability ~199
Kamchatka tour live availability by date: free seats and nearest open dates. Свободные даты и места КОНКРЕТНОГО тура из реальной занятости броней. Используй всегда, когда турист спрашивает «когда есть места», «свободно ли на дату», «на какие даты можно» — не называй даты и места по памяти, только отсюда.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Start of the window, YYYY-MM-DD; default today. С какой даты смотреть, YYYY-MM-DD. Не сказано — с сегодня. |
| days | string | – | Window length in days, 1–31; default 14. Окно в днях (1–31). Не сказано — 14. |
| tour | string | yes | Tour title, keyword or numeric ID from get_tours. Название тура, ключевое слово или числовой ID |
No output schema declared.
No examples provided.
get_tour_details Tour details ~169
One Kamchatka tour in depth: program, what is included, what to bring, safety notes. To list or search tours use get_tours. Полные детали КОНКРЕТНОГО тура: описание, программа, точка сбора и логистика (старт/забор), что входит и не входит, что взять с собой. Используй ВСЕГДА, когда турист спрашивает про конкретный тур — что там по программе, откуда стартуют, где сбор, что взять. Не выдумывай эти детали сам — бери отсюда.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Tour title or a keyword from it. Название тура или ключевое слово (например «сплав», «Быстрая», «рыбалка») |
No output schema declared.
No examples provided.
get_tours Tour catalogue ~137
Kamchatka tour catalogue: list operator tours with prices and dates; live availability via get_tour_availability. For one tour in depth use get_tour_details. Получить активные туры из платформы TourHab с ценами и датами. Используй когда турист спрашивает о конкретных турах или программах.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_type | string | – | Activity filter, free text (Russian works best): fishing, volcanoes, bears, geysers, trekking. Фильтр по типу: рыбалка, вулканы, медведи, гейзеры, трекинг и т.д. |
No output schema declared.
No examples provided.
get_volcano_status Volcano status ~173
Kamchatka volcano activity: KVERT aviation code and KB GS RAS seismicity. No name — all elevated. For one place or route use get_guardian_context. Вулканическая активность Камчатки по двум шкалам: авиационный код KVERT (пепел) и сводка сейсмичности КФ ЕГС РАН. Без названия — вулканы, повышенные хотя бы по одной шкале; с названием — этот вулкан по обеим. Для безопасности конкретного места и маршрута — get_guardian_context.
| Name | Type | Req | Description |
|---|---|---|---|
| volcano | string | – | Volcano name; empty — all volcanoes elevated on either scale. Название вулкана, например «Ключевской» или «Мутновский». Пусто — все повышенные. |
No output schema declared.
No examples provided.
get_weather Weather ~255
Daily weather forecast (Open-Meteo) for a Kamchatka place by name, or for any point by latitude/longitude. Прогноз погоды по дням (Open-Meteo) для места Камчатки по имени или для любой точки по координатам. Без аргументов — Петропавловск-Камчатский; в горах погода другая, поэтому место лучше назвать.
| Name | Type | Req | Description |
|---|---|---|---|
| days | string | – | Forecast days, 1–7; default 3. Сколько дней прогноза, 1–7; по умолчанию 3. |
| lat | string | – | Latitude in decimal degrees; use together with lng. Coordinates take precedence over place. Широта в градусах, например 52.45. Вместе с lng; координаты главнее названия. |
| lng | string | – | Longitude in decimal degrees; use together with lat. Долгота в градусах, например 158.19. Вместе с lat. |
| place | string | – | Place name from the platform directory (Russian works best). Название места из справочника платформы, например «Мутновский» или «Налычево». |
No output schema declared.
No examples provided.
make_trip_plan Trip plan ~418
Day-by-day Kamchatka trip plan with weather and live availability. Собрать план поездки по Камчатке по дням: зоны, активности, честные цены, предупреждения сезона. Используй, когда туриста интересует «что посмотреть за N дней», «составь маршрут/план поездки», «как спланировать неделю на Камчатке». Ответ содержит ссылку на страницу готового плана с бронью туров.
| Name | Type | Req | Description |
|---|---|---|---|
| days | string | – | Trip length in days, 3–21; default 7. Сколько дней поездка (число, 3–21). Не сказано — 7. |
| interests | string | – | Interests in free text. Интересы туриста своими словами: «вулканы и медведи», «рыбалка», «море и термальные» |
| rest_days | string | – | Rest days to add, 0–14; a weather reserve day is added separately when needed. Сколько дней отдыха вставить в план (0–14), если турист сказал. Резерв на нелётную погоду планер добавит сам. |
| travel_style | string | – | How the traveller wants to go: self (no guide, only where our safety data allows), operator (operator tours) or mixed; default mixed. Как турист хочет ехать: «сам» (без гида — только там, где это без… |
| when | string | – | When the trip starts: a Russian month name or YYYY-MM-DD; season decides what is possible in Kamchatka. Default is one month from today. Когда поездка: месяц («июль», «в августе») или дата YYYY-MM-DD… |
No output schema declared.
No examples provided.
safety_status Regional safety status ~141
Kamchatka regional safety status: active alerts (seismic, volcanic, weather, MChS) with their source. Текущая обстановка по Камчатскому краю целиком: активные предупреждения, их количество и тяжесть, свежесть данных и источник верхнего предупреждения (ленты: КБГС РАН и ЕГС РАН — сейсмика, USGS, МЧС по Камчатскому краю, NASA FIRMS — пожары). Используй, когда спрашивают, безопасно ли сейчас ехать или что происходит в крае. Для конкретного места используй get_guardian_context.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_accommodations Stays ~176
Stays in Kamchatka from platform partners. Найти жильё на Камчатке (гостиницы, базы, глэмпинг, дома) из платформы TourHab с ценами и адресами. Используй когда турист спрашивает где остановиться, переночевать, снять жильё.
| Name | Type | Req | Description |
|---|---|---|---|
| price_max | string | – | Maximum price per night, RUB. Максимальная цена за ночь в рублях |
| type | string | – | Stay type: hotel, hostel, guesthouse, glamping, apartment, cottage. Тип жилья: hotel, hostel, guesthouse, glamping, apartment, cottage |
| zone | string | – | Area or town name. Зона расположения (например: Петропавловск-Камчатский, Налычево, Паратунка) |
No output schema declared.
No examples provided.
search_gear Gear rental ~189
Gear rental in Kamchatka from platform partners. Найти прокат туристического снаряжения на Камчатке из платформы TourHab с ценами за сутки. Используй когда турист спрашивает где арендовать/взять напрокат снаряжение: палатку, спальник, треккинговые палки, рюкзак, кошки, газовую горелку и т.д.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Gear category, if known. Категория снаряжения (если известна) |
| price_max | string | – | Maximum price per day, RUB. Максимальная цена за сутки в рублях |
| query | string | – | What to rent: tent, sleeping bag, trekking poles, a brand. Что ищут: например "палатка", "спальник", "треккинговые палки", бренд |
No output schema declared.
No examples provided.
search_transfers Transfers ~256
Transfers in Kamchatka from platform partners. Найти свободные места в поездках перевозчиков Камчатки (джипы, вахтовки, микроавтобусы) из витрины TourHab: дата, направление, остаток мест, цена места. Используй когда турист спрашивает как доехать, есть ли трансфер, заброска, попутный джип к вулкану или источникам. Место занимается только после подтверждения перевозчика.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Window start, YYYY-MM-DD; default today. Начало окна дат, ГГГГ-ММ-ДД (по умолчанию сегодня) |
| place | string | – | Destination or origin keyword. Куда или откуда: слово из направления, например «Горелый», «Толбачик», «аэропорт» |
| seats | string | – | Seats needed; default 1. Сколько мест нужно (по умолчанию 1) |
| to | string | – | Window end, YYYY-MM-DD; default +14 days, at most 60. Конец окна дат, ГГГГ-ММ-ДД (по умолчанию +14 дней, не больше 60) |
No output schema declared.
No examples provided.
What is the Vedar — Kamchatka travel MCP server?
Vedar — Kamchatka travel is an MCP server listed in the public MCP registry as ru.vedarai/mcp. Kamchatka travel: live tours and availability, safety alerts, places, weather, stays, trip plans. This page covers its hosted endpoint (https://vedarai.ru/api/mcp).
Is the Vedar — Kamchatka travel MCP server safe to use?
Vedar — Kamchatka travel scores 74 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 Vedar — Kamchatka travel MCP server expose?
Vedar — Kamchatka travel exposes 14 tools: get_tours, get_tour_details, get_guardian_context, get_place_info, get_weather, and 9 more. Their descriptions and schemas cost roughly 2,992 tokens of context every time the server is loaded.
Does the Vedar — Kamchatka travel MCP server require authentication?
No. We connected to Vedar — Kamchatka travel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Vedar — Kamchatka travel MCP server still maintained?
Vedar — Kamchatka travel is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.