Search / io.github.ASEM-BATAWY/vicatoo
Search VICATOO hotels by traveler needs, features, location, and landmarks with factual evidence.
v0.9.0 · active · descriptor JSON · versions
protogrid{
"mcpServers": {
"vicatoo": {
"type": "http",
"url": "https://mcp.vicatoo.com/mcp"
}
}
}claude mcp add --transport http vicatoo https://mcp.vicatoo.com/mcp[mcp_servers.vicatoo]
url = "https://mcp.vicatoo.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vicatoo": {
"type": "remote",
"url": "https://mcp.vicatoo.com/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"vicatoo": {
"type": "http",
"url": "https://mcp.vicatoo.com/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=vicatoo&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLnZpY2F0b28uY29tL21jcCJ9"
}{
"servers": {
"vicatoo": {
"type": "http",
"url": "https://mcp.vicatoo.com/mcp"
}
}
}{
"mcpServers": {
"vicatoo": {
"httpUrl": "https://mcp.vicatoo.com/mcp"
}
}
}extensions:
"vicatoo":
enabled: true
name: "vicatoo"
type: streamable_http
uri: "https://mcp.vicatoo.com/mcp"
timeout: 300
protocol.modern, protocol.stateless, protocol.transport, protocol.list_ttlno remote answered a protocol handshake (not probed yet, unreachable, or local-only)auth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_length1 tools have descriptions over 1,024 characters, which crowds the contexttools.schemasevery tool has an object input schematools.annotations6 of 6 tools declare readOnlyHint or destructiveHinttools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHinttools.token_costabout 2,700 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changes, stability.rug_pulltool history not recorded yetdeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+reachable +uptime-99% ~updated-51d-ago -no-repository
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://mcp.vicatoo.com/mcp streamable-http | unknown | yes | 99% | 138 ms | – | 2026-10-19 |
about_vicatooread-only | 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. |
check_availabilityread-only | 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. |
get_hotel_detailsread-only | 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. |
get_hotel_reviewsread-only | 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). |
get_room_videoread-only | 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. |
search_hotelsread-only | 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 these results — every VICATOO hotel page linked in `url` already contains the exact map; if the guest asks about locations, describe distances and link the VICATOO pages instead. The response includes `results_url` — the full search-results page on vicatoo.com with the same query and dates. ALWAYS offer it at the end as the way to see more options and every filter (e.g. "لمزيد من الخيارات" / "see all results on VICATOO"). Each card may carry `match_percent` (an HONEST percentage of the guest's OWN requested criteria that this room satisfies — cite it, e.g. "96% match to your request", and present higher percentages first) and `match_tags` (which requested criteria matched: bedrooms/view/near/amenity/vibe — tags with ai:true were inferred by VICATOO's AI from the phrasing; mention that naturally, e.g. "our AI also picked up you want somewhere quiet"). Never invent a percentage when match_percent is null. |
Schemas: list_tools.
{
"name": "io.github.ASEM-BATAWY/vicatoo",
"title": "VICATOO Hotel Discovery",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://mcp.vicatoo.com/mcp",
"type": "streamable-http"
}
],
"version": "0.9.0",
"description": "Search VICATOO hotels by traveler needs, features, location, and landmarks with factual evidence."
}