Skip to content
External endpointresponds

Skiplagged MCP

Skiplagged MCP Server for flight search, hotel booking, and travel planning

Endpoint URL
https://mcp.skiplagged.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:05 AM UTC
Check
MCP initialize · 8s limit
Latency
677 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.skiplagged/mcp

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
@skiplagged/mcp
Version
0.0.4
Capability keys
tools, resources, logging, prompts, completions
Tool names
sk_flights_search, sk_destinations_anywhere, sk_flex_departure_calendar, sk_flex_return_calendar, sk_hotels_search, sk_cars_search, sk_hotel_details, sk_faq_search, sk_resolve_location, sk_resolve_iata
Instructions excerpt

- If origin is missing or ambiguous, call sk_resolve_location first, then prefer IATA codes in all tools. - For date flexibility: run sk_flex_departure_calendar first; when trip length matters, follow with sk_flex_return_calendar; use sk_flights_search only after picking dates. - Use sk_destinations_anywhere when the user is open to where to go; otherwise prefer sk_flights_search for specific routes. - On empty or thin results, widen dates by +/-3 days and retry once; stop after two total attempts. - Skiplagged APIs do not support searches in the past; always ensure flight, hotel, and car rental dates are today or later. - Defaults: 1 adult, economy cabin, sk_flights_search limit=12 unless user asks for more; calendar tools max 2 pages; request concise/compact responses where supported. - After completed tool calls, give a one-line takeaway; never invent data not returned by tools.

Reported Aug 17, 2026, 05:05 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 162ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 357ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 195ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 677ms