MCP: Travel Fare Intel - Flights, Hotels, Fare-Drop
Pricing
$5.00 / 1,000 mcp tool calls
MCP: Travel Fare Intel - Flights, Hotels, Fare-Drop
MCP server for travel-fare-intel. AI-agent tools: search_flight_fares, get_route_grid, watch_fare, search_hotel_prices. Google Flights has no API - this reads the open result pages. x402 (USDC on Base) and Skyfire ready. For OTAs, fare-drop apps, corporate travel, travel fintech.
Pricing
$5.00 / 1,000 mcp tool calls
Rating
0.0
(0)
Developer
Seibs.co
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
3 days ago
Last modified
Categories
Share
MCP: Travel Fare & Hotel Price Intel
An MCP (Model Context Protocol) server wrapper around travel-fare-intel, exposing structured flight-fare and hotel-price data as AI-agent tools. Because Google Flights has no public API (and ITA's was discontinued), this reads the open, logged-out result pages and returns clean, normalized fares an agent can reason over.
Tools
| Tool | What it does |
|---|---|
search_flight_fares | Current fares for one route (origin/destination/date, optional return), cheapest-first: carrier, USD fare, cabin, stops, duration, times, booking source. |
get_route_grid | Cheapest fare per departure date across a window for one route - the date grid for "which day is cheapest?". |
watch_fare | Fare-watch one route: current cheapest fares plus price drops vs the previous run (pair with a Schedule for recurring alerts). |
search_hotel_prices | Hotel prices for a destination + check-in/check-out window, cheapest-per-night-first: total + per-night price, stars, review score, room type. |
Modes
list_tools- emit the tool catalog (name, description, JSON schema per tool) plus the agentic-payment descriptor. Free.call_tool- invoke one tool: settoolandargs.batch- invoke several{tool, args}calls in one run (max 10).
{ "mode": "call_tool", "tool": "search_flight_fares","args": { "origin": "JFK", "destination": "LAX", "departure_date": "2026-07-15" } }
Agentic payments (x402 + Skyfire)
This server is x402 (USDC on Base) and Skyfire ready. When the operator enables Apify's MCP monetization, an AI agent can pay per tool call with no pre-provisioned API token. The list_tools response advertises the accepted rails in its payments block. Enable via env: X402_ENABLED, X402_PAY_TO_ADDRESS, SKYFIRE_ENABLED, SKYFIRE_SELLER_ID.
Pricing
Flat $0.005 per MCP tool call plus upstream pass-through (the travel-fare-intel actor charges its own fare_record / hotel_record / route_history / price_drop_alert events to the same run). A hard cap of 5 tool calls per run, a $0.05 minimum-revenue abuse guard, and a 600s runtime cap protect against runaway agent loops.
How it connects
The wrapper validates tool args with Pydantic, calls the upstream actor via Actor.call(), reshapes the dataset into small, deterministic JSON ({ tool, args, ok, count, items, summary, error }), and never throws - upstream failures come back as ok=false with an error. That envelope is exactly what MCP clients (Claude Desktop, Cursor, OpenAI Assistants, LangChain) expect.
Part of the seibs.co intel portfolio.