ai.autonomad/travel
REMOTE · MCP.AUTONOMAD.AI · 2 COMPONENTS · SCANNED AUG 3
AI travel agent — book flights, hotels, activities, and events worldwide via autonomad.ai.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1889 tokens (~188/item across 10 items; 8 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 45% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.autonomad.ai
claude mcp add --transport http ai-autonomad-travel https://mcp.autonomad.ai/mcp
[mcp_servers.ai-autonomad-travel] url = "https://mcp.autonomad.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-autonomad-travel": {
"type": "remote",
"url": "https://mcp.autonomad.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-autonomad-travel --url https://mcp.autonomad.ai/mcp --transport streamable-http
mcp_servers:
ai-autonomad-travel:
url: "https://mcp.autonomad.ai/mcp" {
"mcpServers": {
"ai-autonomad-travel": {
"type": "http",
"url": "https://mcp.autonomad.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://mcp.autonomad.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.autonomad.ai | CN=YE1,O=Let's Encrypt,C=US | 7 Jul 2026 | 5 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5abe60ddc63ca816f3c115ec87156b6b32a |
| SANs: mcp.autonomad.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of mcp.autonomad.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| autonomad.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.autonomad.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.autonomad.ai/mcp | HTTPS enforced | 301 | https://mcp.autonomad.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
create_booking_intent ~724
Create a booking intent — returns a deep-link the user clicks to complete the booking on autonomad.ai. The first booking they complete unlocks a 1-month free Autonomad Premium trial automatically. ALWAYS call this instead of trying to book directly through MCP — bookings require payment + identity verification that must happen on the web. WHEN TO CALL — generate a deep-link ONLY after the user has picked something concrete: a specific flight, a specific hotel, or both (a trip). Do NOT call this for browsing or for activities/events alone. Activities and events are picked on the autonomad.ai add-ons page AFTER the user lands via the deep-link — Claude should describe them but not generate per-activity/per-event intents. INTENT TYPE GUIDE — pick exactly one: - 'flight' → user picked a flight only. offer_data = the flight offer object verbatim from search_flights, PLUS a top-level `passengers: <number>` field (the number of travelers the user originally requested — search_flights individual offers don't echo this back, so you must add it explicitly). - 'hotel' → user picked a hotel only. offer_data = the hotel offer from search_hotels PLUS top-level `check_in` and `check_out` (YYYY-MM-DD) as STRINGS. CRITICAL: search_hotels does NOT echo dates back inside the offer object — you MUST add them yourself (use the same dates you passed to search_hotels) or the booking page will fall back to an empty form and the user will have to re-enter everything. Also include `adults: <number>` and `rooms: <number>`. - 'trip' → user picked BOTH a flight AND a hotel together for the same trip. Pack them in offer_data as { flight: { ...offer, passengers: <n> }, hotel: { ...offer, adults: <n>, rooms: <n>, check_in, check_out } }. ONE deep-link covers both. Don't generate two separate intents (flight + hotel) for the same trip — that produces two deep-links and a confusing user experience. For activities, events, and experience browsing: describe what's available in your reply, but d…
| Name | Type | Req | Description |
|---|---|---|---|
| expires_minutes | number | — | — |
| intent_type | string | yes | — |
| offer_data | object | yes | — |
No output schema declared.
No examples provided.
get_capabilities ~51
Return the server's version, mode (human vs autonomous-agent), API base, and the list of currently-exposed tools. Useful for the LLM to confirm tool-schema compatibility before issuing a sequence of calls.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_activities ~137
Search tours, experiences, attractions, sightseeing, and things to do via Viator (200K+ activities worldwide). Filter by city, date range, and category (food tours, walking tours, museums, snorkeling, sailing, hiking, sunset cruises, cooking classes, day trips, etc.). Returns activities with photos, ratings, durations, and per-person pricing. Use this when the user wants to plan day activities, find tours, book experiences, fill a trip itinerary, or pick attractions.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | — |
| city | string | yes | — |
| date_from | string | yes | — |
| date_to | string | — | — |
No output schema declared.
No examples provided.
search_dining ~145
Search restaurants and dining options by city, date, time, cuisine, party size, neighborhood, and price range. PLANNING ONLY — this returns restaurant details and indicative availability; Autonomad does not place reservations, and the user completes any booking with the restaurant directly. Use this when the user wants to find, compare, or shortlist somewhere to eat on a trip.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | — |
| cuisine | string | — | — |
| date | string | yes | YYYY-MM-DD |
| neighborhood | string | — | — |
| party_size | number | — | — |
| price_range | string | — | — |
| time | string | — | HH:MM in 24h |
No output schema declared.
No examples provided.
search_events ~131
Search live events, concerts, sports games, theater, comedy, and shows in a city (Ticketmaster + SeatGeek catalog). Filter by city, date range, category (music / sports / arts / theater / family / comedy), and keyword (artist name, team name, show title). Use this when the user wants tickets to a concert, a sports game, a Broadway show, or any live event during their trip.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | — |
| city | string | yes | — |
| date_from | string | yes | — |
| date_to | string | — | — |
| keyword | string | — | — |
No output schema declared.
No examples provided.
search_flights ~243
Search airline flights / airfares between two cities by date, cabin class (economy / premium economy / business / first), and number of passengers. Returns available flights from 800+ airlines (Duffel) with real-time pricing, schedules, and stops. Uses IATA airport codes (e.g., MIA, JFK, LAX, LHR). Use this when the user wants to book a flight, fly somewhere, find airfare, or compare airlines.
| Name | Type | Req | Description |
|---|---|---|---|
| cabin_class | string | — | Cabin class (default: economy) |
| departure_date | string | yes | Departure date (YYYY-MM-DD) |
| destination | string | yes | IATA destination airport code |
| max_price_usd | number | — | Maximum total price in USD |
| nonstop_only | boolean | — | Only show nonstop flights (default: false) |
| origin | string | yes | IATA origin airport code (e.g., 'MIA', 'JFK', 'LAX') |
| passengers | number | — | Number of passengers (1-9, default: 1) |
| return_date | string | — | Return date for round-trip (YYYY-MM-DD). Omit for one-way. |
No output schema declared.
No examples provided.
search_hotels ~253
Search hotels, lodging, accommodations, resorts, and places to stay for a trip. Filter by city, country, check-in/check-out dates, room type, nightly price, star rating, and amenities (pool, gym, wifi, etc.). Returns matching properties with rates, photos, and availability across 2M+ properties (LiteAPI). Use this when the user wants to book a hotel, find a place to stay, compare lodging options, or pick a resort.
| Name | Type | Req | Description |
|---|---|---|---|
| amenities | array | — | Required amenities (wifi, gym, pool, spa, restaurant, etc.) |
| brand | string | — | Hotel brand name to filter by |
| check_in | string | yes | Check-in date (YYYY-MM-DD) |
| check_out | string | yes | Check-out date (YYYY-MM-DD) |
| city | string | — | City name (e.g., 'New York', 'Tokyo') |
| country | string | — | ISO 3166-1 alpha-2 country code (e.g., 'US', 'JP') |
| max_rate_usd | number | — | Maximum nightly rate in USD |
| min_star_rating | number | — | Minimum star rating (1-5) |
| room_type | string | — | — |
No output schema declared.
No examples provided.
search_transport ~170
Search ground transportation — rideshare (Uber, Lyft) and car rental (Hertz, Enterprise, Avis, etc.) — timed to a flight arrival for door-to-door planning. NOTE: these return indicative quotes for planning only; in-app booking is not yet live (rideshare and car-rental supplier integrations are still in progress). Use this when the user wants to scope a rental car, an airport transfer, or rideshare to/from their hotel.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City or metro area |
| dropoff_location | string | — | — |
| passengers | number | — | — |
| pickup_datetime | string | — | ISO 8601 |
| pickup_location | string | — | — |
| return_datetime | string | — | — |
| transport_type | string | — | — |
| vehicle_type | string | — | — |
No output schema declared.
No examples provided.