Is com.moltravel/travel up? Live MCP status

Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2025-11-25.

A stock client connected with no credential and negotiated 2025-11-25. Use it.

One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.

Live status every few hours: Wellknown

Email me when this server changes

That was one look. To hear when it stops answering or its tools change, leave an address.

Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.

Monthly census, 6 October 2026

The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

Read at https://mcp.moltravel.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.

Tool changes between snapshots

In the 2026-10 snapshot it listed 56 tools: airlines_lookup, airlines_search, airports_lookup, airports_near, airports_search, data_status, fcdo_list_countries, fcdo_travel_advice, ferryhopper_get_direct_connections_for_ports, ferryhopper_get_disruptions, ferryhopper_get_ports, ferryhopper_search_trips, ferryhopper_search_trips_v2, ferryhopper_trip_details, peek_experience_availability, peek_experience_details, peek_list_tags, peek_render_activity_tiles, peek_search_experiences, peek_search_regions, restcountries_country_info, skiplagged_sk_cars_search, skiplagged_sk_destinations_anywhere, skiplagged_sk_faq_search, skiplagged_sk_flex_departure_calendar, skiplagged_sk_flex_return_calendar, skiplagged_sk_flights_search, skiplagged_sk_hotel_details, skiplagged_sk_hotels_search, skiplagged_sk_resolve_iata, skiplagged_sk_resolve_location, tourradar_algolia-operator-search, tourradar_b2b-cities-search, tourradar_b2b-continents-list, tourradar_b2b-countries-list, tourradar_b2b-currencies-list, tourradar_b2b-languages-list, tourradar_b2b-operator-details, tourradar_b2b-tour-departures, tourradar_b2b-tour-details, tourradar_b2b-tour-faq, tourradar_b2b-tour-map, tourradar_b2b-tour-types-list, tourradar_general-current-date, tourradar_vertex-review-search, tourradar_vertex-tour-search, tourradar_vertex-tour-title-search, tourradar_web-ask-question, tourradar_web-tour-booking, tourradar_web-tour-send-brochure, travel_agent, trivago_trivago-accommodation-radius-search, trivago_trivago-accommodation-search, trivago_trivago-destination-price-trends, visa_check, visa_summary.

Its tools changed between 2026-09 and 2026-10:

• trivago_trivago-accommodation-radius-search: description, input schema changed
• trivago_trivago-accommodation-search: description, input schema changed
• trivago_trivago-destination-price-trends: description changed

Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.

The listing

Also

The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt

Free, no key, no signup. Terms · Privacy