# Tourhabk Ui Vedar MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.tourhabk-ui%2Fvedar
Registry id: `mcp-registry/io.github.tourhabk-ui/vedar`
Status: live (checked 2026-10-26T19:50:02.549Z)

## Verdict

Tourhabk Ui Vedar MCP server answered 98.41% of Glimind's liveness checks over 30 days, better than 6% of MCP servers, with 952 ms median handshake and 143 outages in 90 days. Its agent-readiness grade is A (94/100) across 22 tools, costing an agent about 8,208 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 98.41% | 6% of MCP servers |
| Median handshake latency | 952 ms | 25% of MCP servers |
| p95 handshake latency | 4408 ms | — |
| Checks in 30 days | 4,868 | — |
| Outages, 90 days | 143 | — |
| Median recovery | 8 min | — |
| Agent-readiness score | 94/100 (A) | 78% of MCP servers |
| Tools | 22 | — |
| Tool-list size for an agent | ~8,208 tokens | 33% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "tourhabk-ui-vedar-mcp-server": {
      "type": "http",
      "url": "https://vedarai.ru/api/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http tourhabk-ui-vedar-mcp-server https://vedarai.ru/api/mcp
```

## Tools (32)

- `check_tour_availability`: Проверка реальной занятости тура на даты
- `create_booking_request`: Use when the user wants to book a Kamchatka tour on a date: live availability checked first, human-confirmed by the operator, no payment. Needs consent: true. N
- `create_car_rental_request`: Two-step Kamchatka self-drive car rental request: step 1 returns a draft and confirmation code; step 2 only after the person explicitly agrees. Never set consen
- `create_lead`: Tour-selection request for Kamchatka when no tour or date is chosen yet; human-confirmed by a manager, no payment. Needs consent: true, else refused. Whole-vehi
- `create_stay_request`: Kamchatka stay request: dates and guests go to the owner, human-confirmed by the owner, no payment. Needs consent: true, otherwise refused. For tours use create
- `create_trip_plan`: Создание плана поездки
- `edit_trip_plan`: Edit a Kamchatka trip plan from make_trip_plan by its ID: add, remove or move a day, change lodging level, or apply a flight delay the traveller reports; untouc
- `fetch`: Full text of one Vedar Kamchatka record by id from search (tour, place, stay, route): description, price, program, safety facts, canonical url. Published record
- `get_guardian_context`: Kamchatka safety context for a place or route: hazards, active alerts, advice. For plain facts (type, coordinates) use get_place_info. Получить полный контекст 
- `get_place_info`: Kamchatka place facts only: what it is, type, coordinates. Does not return hazards, alerts or nearby places — for safety use get_guardian_context. Найти базовую
- `get_place_real_time_status`: Получение реалтайм-статуса места
- `get_place_safety`: Получение профиля безопасности места
- `get_request_status`: Status of a Kamchatka request by the key from create_lead, create_booking_request, create_stay_request, request_charter or create_car_rental_request: operator a
- `get_route`: Получение детальной информации о маршруте
- `get_route_safety`: Получение информации о безопасности маршрута
- `get_tour`: Получение детальной информации о туре
- `get_tour_availability`: Use when the user asks if a Kamchatka tour has free seats: live availability by date, free seats and nearest open dates. Then booking via create_booking_request
- `get_tour_details`: One Kamchatka tour in depth: program, what is included, what to bring, safety notes. To list or search tours use get_tours. Полные детали КОНКРЕТНОГО тура: опис
- `get_tours`: Use when the user asks about Kamchatka (Russia) tours: operator tours with prices and dates; live availability via get_tour_availability. One tour in depth: get
- `get_volcano_status`: Use when the user asks about Kamchatka volcano activity: KVERT aviation code and KB GS RAS seismicity. No name — all elevated. One place or route: get_guardian_
- `get_weather`: Daily weather forecast (Open-Meteo) for a Kamchatka place by name, or for any point by latitude/longitude. Прогноз погоды по дням (Open-Meteo) для места Камчатк
- `make_trip_plan`: Day-by-day Kamchatka trip plan with weather and live availability; returns a plan ID for edit_trip_plan. Собрать план поездки по Камчатке по дням: зоны, активно
- `request_charter`: Whole-vehicle (vakhtovka, minibus) request to a Kamchatka charter carrier: destination, dates, group size; human-confirmed by a manager, no payment. Needs conse
- `safety_status`: Kamchatka regional safety status: active alerts (seismic, volcanic, weather, MChS) with their source and dates, plus elevated volcanoes (KVERT, KB GS RAS). Теку
- `search`: Keyword search across Vedar Kamchatka: operator tours, places, stays, routes; returns up to 10 results with id for fetch, title and canonical url. For live seat
- `search_accommodations`: Use when the user asks about hotels or accommodation in Kamchatka, Russia: stays from platform partners. To send dates and guests to a stay owner use create_sta
- `search_car_rental`: Use when the user wants to rent a car, SUV, 4x4 or minibus in Kamchatka (car rental, car hire): self-drive, price per day, deposit. With a driver: search_transf
- `search_gear`: Gear rental in Kamchatka from platform partners. An empty result is normal: the rental shelf may have no partners yet, and the answer says so — do not invent re
- `search_places`: Поиск мест (вулканы, озёра, источники и т.д.)
- `search_routes`: Поиск маршрутов
- `search_tours`: Поиск туров по параметрам
- `search_transfers`: Use when the user asks about Kamchatka transfers: whole-vehicle charters (vakhtovka, minibus, jeep), price per vehicle by destination or hour/day, not per seat.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.