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.

VICATOO Hotel Discovery

REMOTE · MCP.VICATOO.COM · SCANNED SEP 28

Search VICATOO hotels by traveler needs, features, location, and landmarks with factual evidence.

Available components

+4 this week 70 Trust /100
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 Security77
Transport & Reachability100
Schema Quality & AI Usability35
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1798 tokens (~256/item across 7 items; 6 tools + 1 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 Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 59% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Install

How do I install the VICATOO Hotel Discovery MCP server?

VICATOO Hotel Discovery is a hosted endpoint at https://mcp.vicatoo.com/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 · mcp.vicatoo.com

# add to Claude Code
claude mcp add --transport http asem-batawy-vicatoo 'https://mcp.vicatoo.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "asem-batawy-vicatoo": {
      "url": "https://mcp.vicatoo.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "asem-batawy-vicatoo": {
      "type": "http",
      "url": "https://mcp.vicatoo.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.asem-batawy-vicatoo]
url = "https://mcp.vicatoo.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "asem-batawy-vicatoo": {
      "type": "remote",
      "url": "https://mcp.vicatoo.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add asem-batawy-vicatoo --url 'https://mcp.vicatoo.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  asem-batawy-vicatoo:
    url: "https://mcp.vicatoo.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "asem-batawy-vicatoo": {
      "Transport": "http",
      "Url": "https://mcp.vicatoo.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add asem-batawy-vicatoo -t streamable-http -u 'https://mcp.vicatoo.com/mcp'
// mcp.json
{
  "mcpServers": {
    "asem-batawy-vicatoo": {
      "type": "http",
      "url": "https://mcp.vicatoo.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 28 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
  • 26 Sept 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.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 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.

  • 22 Sept 26 +1

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

  • 20 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 17 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
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 28 Sept 2026 · Probed https://mcp.vicatoo.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=vicatoo.com CN=YE2,O=Let's Encrypt,C=US 18 Aug 2026 16 Nov 2026 ECDSA 256 ECDSA-SHA384 686c4846311fa9734842be053d22e7c7061
SANs: *.vicatoo.com, vicatoo.com
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 secure

Validation of mcp.vicatoo.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
vicatoo.com. present 2371 13 Verified
mcp.vicatoo.com. Verified address RRset verified with the apex keys
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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.vicatoo.com/mcp Verified 200
http (plaintext) http://mcp.vicatoo.com/mcp HTTPS enforced 301 https://mcp.vicatoo.com/mcp
MCP tools · 6 exposed · ~1,784 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_vicatoo ~110

Returns factual information about VICATOO the company: who VICATOO is, the "Truth Before You Book" value proposition and benefits, and trust credentials (legal entity, TRUE/CCRA accreditation, D-U-N-S number, registered address). Call this whenever the guest asks who VICATOO is, why they should trust VICATOO, what VICATOO offers or how it is different, or anything about the company or brand — so you answer from grounded facts, never invented ones.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

check_availability ~283

Fetch live VICATOO rates for a hotel for the given check-in/check-out dates and occupancy. Returns up to `limit` rates with room name, price, meal type, bed type and cancellation policy. Booking itself always completes on vicatoo.com — to book, direct the guest to open the hotel page URL (the search_hotels card link already carries the dates and guests); never promise in-chat booking.

NameTypeReqDescription
adultsinteger––
check_instringyes–
check_outstringyes–
children_agesarray––
currencystring–3-letter ISO currency for the rate prices. Defaults to USD so rates match the search-result prices; pass the same currency the guest saw in search.
hotel_id–yesVICATOO hotel id — numeric hid or slug (same as get_hotel_details).
limitinteger––
residencystring––
room_type_filterstring–Optional case-insensitive substring filter on room_name.
roomsinteger––
viewstring–Optional preferred view family (e.g. "bosphorus", "sea", "garden", "city", "pool"). When the guest cares about a specific view, pass it so matching-view rates are floated to the top instead of the de…

No output schema declared.

No examples provided.

get_hotel_details ~312

Fetch full details for a single hotel by its VICATOO hotel_id (numeric hid or slug). Returns name, star rating, REAL guest rating (score/10 + review count — cite it, and call get_hotel_reviews for guest pros/cons before strongly recommending), what the hotel is known for (vibe_tags), location, check-in/out times, headline amenities, images, a description, AND the available rooms cheapest-first — each with photos, live from-price, size, view, bed type, meal plan and cancellation. When has_video is true, offer the real room-tour video via get_room_video with the returned reel_id.

NameTypeReqDescription
currencystring–3-letter ISO currency for room prices. Defaults to USD so hotel details match the search-result prices; pass the same currency the guest saw in search.
hotel_id–yesVICATOO hotel id — either the numeric hid (e.g., 7476954) or the slug (e.g., "bentley-hotel-bosphorus-7476954").
langstring–2-letter language code for content (en, ar, de, fr, es, ru, etc.).
viewstring–Optional preferred view family (e.g. "bosphorus", "sea", "garden", "city", "pool"). When the guest arrived from a view-constrained search, pass it so rooms with that view are floated to the top inste…

No output schema declared.

No examples provided.

get_hotel_reviews ~122

Fetch guest reviews for a hotel from the VICATOO content API. Supports pagination via `cursor` (page offset) and `limit`. Returns aggregate count and per-review summary (author, rating, pros/cons, stay context).

NameTypeReqDescription
cursorinteger–Page offset (0-based).
hotel_id–yesVICATOO hotel id — numeric hid OR slug etg_id (the same id search_hotels and get_hotel_details return); slugs are resolved server-side.
langstring––
limitinteger––

No output schema declared.

No examples provided.

get_room_video ~74

Returns VICATOO's real room-tour video for a hotel reel as a branded reel PAGE link on vicatoo.com (reel_url). Share that page link with the guest — NEVER surface any raw video file URL. Includes hotel/room name and caption.

NameTypeReqDescription
reel_id–yesReel primary-key id (numeric).

No output schema declared.

No examples provided.

search_hotels ~883

Search hotels by a descriptive natural-language query in Arabic or English. Applies star rating, bedroom count, room type, and landmark or view as filters, and returns results grouped into match-quality sections (perfect match, close, alternative type, more) — each with the matched room, its photos, and a live per-night + total stay price, meal plan and cancellation policy — every card shown carries a live price bound to its displayed room. Use it for any hotel search; pass the user's full descriptive phrase as `query` (for example "5-star hotel in Paris" or "two-bedroom apartment with an Eiffel Tower view"). Call check_availability for booking-ready rates on a specific hotel. TIER MEANINGS (disclose when recommending): perfect = every stated constraint met; near = minor deviation; unit_swap = the requested unit type had no availability so a similar type is offered; wider/fallback = constraints relaxed. PRESENTATION (follow this when you talk about the results): you are VICATOO's travel concierge — always call the platform VICATOO, never name any supplier. Speak warmly and help the guest feel confident booking, but stay strictly truthful per 'Truth Before You Book': no invented urgency, no 'booked N times', no fake scarcity — only real signals. The real quality signals you may cite: review_score (out of 10) with review_count, and vibe_priority (what the hotel is known for, e.g. families/spa/luxury). For each hotel say in one line WHY it matches (tier, view, distance, what it is known for, rating), and briefly compare the top 2-3 so the guest can choose. Before strongly recommending one hotel, call get_hotel_reviews for real guest pros/cons. When a card has has_reel=true, offer VICATOO's real room-tour video via get_room_video with that card's reel_id. When the search includes children, mention each hotel's extra-bed note so families know whether a child bed is included before they open the page. NEVER render external/third-party maps (Google Maps widgets etc.) for…

NameTypeReqDescription
adultsinteger––
check_instringyesYYYY-MM-DD
check_outstringyesYYYY-MM-DD
children_agesarray––
langstring–The user's language as an ISO 639-1 code (e.g. 'ar', 'ru', 'de', 'fr', 'en') for localizing the result cards. Infer it from the conversation language. If omitted, it is detected from the query script.
limitinteger–Maximum hotels to return across all sections.
querystringyesThe full descriptive search phrase from the user (city + any room type, view, budget, star rating, bedroom count, or vibe cues). Pass exactly what the user typed — e.g. "5-star hotel in Paris" or "شق…
residencystring–ISO 3166-1 alpha-2 of guest residency.
roomsinteger––

No output schema declared.

No examples provided.

Common questions

What is the VICATOO Hotel Discovery MCP server?

VICATOO Hotel Discovery is an MCP server listed in the public MCP registry as io.github.ASEM-BATAWY/vicatoo. Search VICATOO hotels by traveler needs, features, location, and landmarks with factual evidence. This page covers its hosted endpoint (https://mcp.vicatoo.com/mcp).

Is the VICATOO Hotel Discovery MCP server safe to use?

VICATOO Hotel Discovery scores 70 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 VICATOO Hotel Discovery MCP server expose?

VICATOO Hotel Discovery exposes 6 tools: search_hotels, get_hotel_details, check_availability, get_hotel_reviews, get_room_video, about_vicatoo. Their descriptions and schemas cost roughly 1,784 tokens of context every time the server is loaded.

Does the VICATOO Hotel Discovery MCP server require authentication?

No. We connected to VICATOO Hotel Discovery without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the VICATOO Hotel Discovery MCP server still maintained?

VICATOO Hotel Discovery is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.