Aggregated travel MCP — flights, tours, activities, price checks, visas, and more.
One MCP server. Every travel tool. Search flights, compare prices, check visas, look up airports, get travel advisories — through a single endpoint. Travel data is scattered across dozens of APIs, each with its own auth, format, and quirks. MoltTravel aggregates them behind a single Model Context Protocol endpoint: 21+ tools from 4 upstream MCP providers + 6 built-in datasets Zero config for…
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
One MCP server. Every travel tool. Search flights, compare prices, check visas, look up airports, get travel advisories — through a single endpoint. Travel data is scattered across dozens of APIs, each with its own auth, format, and quirks. MoltTravel aggregates them behind a single Model Context Protocol endpoint: 21+ tools from 4 upstream MCP providers + 6 built-in datasets Zero config for static data — airports, airlines, and visas load lazily with no API keys Schema-transparent proxy —…
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.