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 · MARSHRUT.ME

Travel in Russia & Baikal: stays, activities, travel companions (read-only, no auth).

Available components

71 Trust /100

Last scanned (12 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

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
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 922 tokens (~131/item across 7 items; 7 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 Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

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.

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

  • 20 Nov 26 0
    • Tool “search_stays” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 61% → 67% ▲ functional
    • “search_stays” added an optional parameter “amenity” cosmetic
    • “search_stays” added an optional parameter “near_centre” cosmetic
    • “search_stays” added an optional parameter “street” cosmetic
  • 19 Nov 26 +1
    • Schema quality: 651 → 779 ▼ functional
    • Schema quality: fair → good functional
    • New tool “ask_mia” functional
  • 17 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 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 21 Nov 2026 · Probed https://marshrut.me/api/agent/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=marshrut.me CN=YE1,O=Let's Encrypt,C=US 4 Nov 2026 2 Feb 2027 ECDSA 256 ECDSA-SHA384 6d117e0402767119bc6a134e963c5f65ede
SANs: business.marshrut.me, marshrut.me, partners.marshrut.me, seo.marshrut.me, www.marshrut.me
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 marshrut.me. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
me. DS published 45352 8 Verified
marshrut.me. No DS 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=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
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://marshrut.me/api/agent/mcp Verified 200
http (plaintext) http://marshrut.me/api/agent/mcp HTTPS enforced 301 https://marshrut.me/api/agent/mcp
MCP tools · 7 exposed · ~822 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
about_marshrut ~43

Как устроен МАРШРУТ: бронирование и оплата, отмена, клуб и бонусы, «Попутчики», хозяевам.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ask_mia ~128

Спросить Мию, гида МАРШРУТА, обычной фразой: «Байкал 19–21 декабря, нас двое, до 10 000 за ночь», «попутка из Иркутска на Ольхон», «дом с баней на компанию». Мия разберёт место, даты, людей и бюджет и вернёт жильё, развлечения, открытые поездки попутчиков и туры клуба со ссылками.

NameTypeReqDescription
questionstringyesПросьба человека как есть, по-русски

No output schema declared.

No examples provided.

get_place ~40

Подробности об одном объекте по id из search_stays: описание, что входит, ссылка на бронирование.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

prepare_booking ~126

Подготовить бронь для человека: проверить даты по календарю объекта и дать ссылку, которая открывает объект уже с этими датами и точной ценой. Ничего не бронирует и не списывает — бронирует и оплачивает сам человек по ссылке после входа.

NameTypeReqDescription
checkinstringyesЗаезд ГГГГ-ММ-ДД
checkoutstringyesВыезд ГГГГ-ММ-ДД
guestsinteger––
idstringyesid из search_stays

No output schema declared.

No examples provided.

search_companions ~90

Открытые поездки «Попутчиков»: совместные путешествия, свободные места в турах и домах, попутки. Можно указать место. Профили людей не отдаются — присоединиться можно на сайте после входа.

NameTypeReqDescription
limitinteger––
wherestring–Место, например «Байкал» или «Ольхон»

No output schema declared.

No examples provided.

search_journal ~52

Статьи журнала МАРШРУТА: путеводители, советы путешественникам, гостям и хозяевам жилья.

NameTypeReqDescription
limitinteger––
querystring––

No output schema declared.

No examples provided.

search_stays ~343

Подобрать жильё и развлечения МАРШРУТА: город (вся Россия — около 21 тыс. отелей), тип (отель, гостевой дом, база отдыха, баня…), слово для поиска, цена «от», число гостей, удобство (бассейн, парковка, с животными…), «в центре», улица. У отелей — номер записи в госреестре средств размещения и ссылка на неё. Возвращает варианты со ссылками.

NameTypeReqDescription
amenitystring–Удобство: бассейн, парковка, с животными, сауна, SPA, фитнес, ресторан, конференц-зал, пляж, кухня, кондиционер, детская площадка, доступная среда, семейные номера (по данным отеля)
checkinstring–Дата заезда ГГГГ-ММ-ДД (необязательно)
checkoutstring–Дата выезда ГГГГ-ММ-ДД (необязательно)
citystring–Город или место, например «Листвянка»
guestsinteger––
limitinteger––
max_priceinteger–Цена «от» не выше, ₽
near_centreboolean–Только до 1 км от центра
querystring–Слово для поиска в названии и описании
streetstring–Улица, например «Невский проспект»
typestring–Тип: отель, гостевой дом, база отдыха, баня…

No output schema declared.

No examples provided.

Install

How do I install the МАРШРУТ — Байкал и Россия MCP server?

МАРШРУТ — Байкал и Россия is a hosted endpoint at https://marshrut.me/api/agent/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 · marshrut.me

# add to Claude Code
claude mcp add --transport http me-marshrut-marshrut 'https://marshrut.me/api/agent/mcp'
Common questions

What is the МАРШРУТ — Байкал и Россия MCP server?

МАРШРУТ — Байкал и Россия is an MCP server listed in the public MCP registry as me.marshrut/marshrut. Travel in Russia & Baikal: stays, activities, travel companions (read-only, no auth). This page covers its hosted endpoint (https://marshrut.me/api/agent/mcp).

Is the МАРШРУТ — Байкал и Россия MCP server safe to use?

МАРШРУТ — Байкал и Россия scores 71 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 7 tools: search_stays, prepare_booking, get_place, search_companions, ask_mia, and 2 more. Their descriptions and schemas cost roughly 822 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 21 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 МАРШРУТ — Байкал и Россия MCP server?

VerifyMCP ran 13 checks on МАРШРУТ — Байкал и Россия, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.