Mcp

io.tooloracle/hoteloracle

Hotel Intelligence MCP — search, price compare, area guides, price calendars via Google Hotels

Verified: 2026-05-13 (mcp-registry-ingest-2026-05-13+enrich-capability-skill)

When to use io.tooloracle/hoteloracle

Choose if

You're building a travel-booking or trip-planning agent and want Google-Hotels-grade inventory (search, price compare, area guides, price calendars) behind one MCP server. Useful when the agent needs to surface hotel options inside a chat without rolling its own scraper or signing a separate Booking.com / Expedia API contract.

Avoid if

You need source-attributable, audit-trail hotel pricing — the underlying GitHub repo is currently 404 and ToolOracle's per-oracle docs are not publicly exposed, so you can't verify how the data is collected. Also avoid if you need direct-booking links, loyalty- program awareness, or B2B / GDS-grade inventory.

Risk Flags

  • MEDIUM cost Part of the ToolOracle mesh — pricing is "route-dependent" with a common baseline around USD 0.01/call, settled via x402 USDC on Base. Per-tool overrides apply. Agents must budget per-call.
  • HIGH data_quality Source GitHub repo (github.com/ToolOracle/hoteloracle) returns 404 as of 2026-05-13 — no public README, only catalog metadata (8 tools, port 6601, did:web:tooloracle.io:hoteloracle). Provenance and refresh cadence of the Google Hotels data are not documented.
  • MEDIUM scope Inventory limited to what's exposed via Google Hotels — does not cover direct-booking sites, boutique inventory not indexed by Google, or rate parity across OTAs.
  • LOW maturity ToolOracle mesh is itself early-stage agent infrastructure (x402-USDC settled). Limited public track record for individual oracles.

Cost

Type: Usage based

Distribution

MCP Registry
io.tooloracle/hoteloracle
Repository
https://github.com/ToolOracle/hoteloracle