Autonomad Travel — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Autonomad travel planning and booking through MCP: Do personalized search inputs and booking commitments retain clear user approval and public-social-data boundaries?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Travel search, trip orchestration and booking through live providers.

What we know

Travel MCP/hosted connector for flights, hotels, activities/events, trip planning, booking management, feedback and optional personalization/rewards.

Maintenance / activity evidence

autonomad-travel 1.4.4 published 2026-09-12T03:29:38.716Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Search plus booking-management authority. Writes: Create/manage/cancel bookings; Submit reviews/feedback.
Agent DID plus provider checkout/payment authorization as applicable.
Sensitive access: Travel identity/preferences, Itineraries, Booking/payment context, Agent reward data

Booking/payment actions can create real charges and cancellation consequences; require explicit user confirmation.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do personalized search inputs and booking commitments retain clear user approval and public-social-data boundaries?

The bounded review of the publisher's documented Autonomad travel planning and booking through MCP and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Booking/payment actions can create real charges and cancellation consequences; require explicit user confirmation.
Search plus booking-management authority.
Agent DID plus provider checkout/payment authorization as applicable.
Travel searches/bookings route through external providers; itinerary and optional personalization data are processed by Autonomad.
Reviewed write actions: Create/manage/cancel bookings; Submit reviews/feedback
Sensitive access: Travel identity/preferences, Itineraries, Booking/payment context, Agent reward data
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Bookings are real external side effects and may involve payment/penalties.
Agent booking path requires an Agent DID.
Social-account personalization is optional.
Some categories such as rideshare/dining were not fully live.

Original activity observations

autonomad-travel 1.4.4 published 2026-09-12T03:29:38.716Z

Technical identity

npm/autonomad-travel

Exact implementation source: https://www.npmjs.com/package/autonomad-travel ↗
Reviewed resource type: MCP Server
Repository identity: Autonomad1/autonomad1
Package identity: npm:autonomad-travel
Service endpoint: https://mcp.autonomad.ai/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
autonomad-travel
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
www.autonomad.ai/developers
Source material retained for this review.
Includes references whose attribution is not established.
GitHub repository ↗
autonomad1/autonomad1
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
Hosted path differs from Agent DID autonomous booking/rewards path; financial booking authority not granted by install
Distinguished agent DID from human hosted connector, and booking approval from installation.
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Hosted URL described by publisher as https://mcp.autonomad.ai/mcp; booking actions require explicit user authorization.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / connect
Publisher instructions
Hosted path differs from Agent DID autonomous booking/rewards path; financial booking authority not granted by install | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Publisher instructions
npx autonomad-travel
Configure / authenticate
MCP100 setup guide
Local stdio config: command npx; args ["autonomad-travel"]; AGENT_DID needed only for autonomous agent identity/reward path, not hosted human connector. Hosted URL described by publisher as https://mcp.autonomad.ai/mcp; booking actions require explicit user authorization. Verify the correct host/transport from the publisher README; secure credentials in local client settings.
Check connection
Suggested check
Check that the registered MCP tools are discoverable in the client; run only publisher-described read-only status/health tools if provided. No runtime verification was performed.
Remove / uninstall / revoke
MCP100 setup guide
If your Claude Code MCP registration is named `autonomad-travel`, run the client removal command. For Claude Desktop/Cursor/Codex or another registered name, remove the matching entry in that host’s MCP settings. Hosted OAuth disconnect and stopping a self-hosted process are separate; npx has no permanent global package install.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove autonomad-travel

Official Documentation & Sources

What it does

Travel MCP/hosted connector for flights, hotels, activities/events, trip planning, booking management, feedback and optional personalization/rewards.

Capability: Search & Web
Resource type: MCP Server
Industry: Travel, Transportation & Aviation, Hospitality, Sports & Entertainment
Best fit: Travel search, trip orchestration and booking through live providers.

Representative uses

Search flights/hotels/activities/events
Orchestrate trips
Create/manage/cancel hotel bookings
Use Travel DNA/group personalization
Inspect agent rewards

Limitations

Bookings are real external side effects and may involve payment/penalties.
Agent booking path requires an Agent DID.
Social-account personalization is optional.
Some categories such as rideshare/dining were not fully live.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Agent DID plus provider checkout/payment authorization as applicable.
Permissions: Search plus booking-management authority.
Data handling: Travel searches/bookings route through external providers; itinerary and optional personalization data are processed by Autonomad.
Cost: transactional
Risk and cautions: Booking/payment actions can create real charges and cancellation consequences; require explicit user confirmation.

Access scope and cautions

Write actions: Create/manage/cancel bookings Submit reviews/feedback
Sensitive access: Travel identity/preferences Itineraries Booking/payment context Agent reward data
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Search flights/hotels/activities/events; Orchestrate trips; Create/manage/cancel hotel bookings; Use Travel DNA/group personalization; Inspect agent rewards.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx autonomad-travel. Recorded endpoint: https://mcp.autonomad.ai/mcp. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: AGENT_DID (required for autonomous booking/rewards); BOOKING_API_URL (optional); IDENTITY_API_URL (optional); REWARD_API_URL (optional). No configuration values are supplied here. Prerequisites: MCP client; Agent DID for bookings; user/payment authorization as required. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: No API key shown; Agent DID authorizes autonomous-agent booking/reward path.

Can it modify data or perform write operations?

Documented write actions include: Create/manage/cancel bookings; Submit reviews/feedback. Recorded permission boundary: Search plus booking-management authority.

What data-handling boundary should I consider?

Travel searches/bookings route through external providers; itinerary and optional personalization data are processed by Autonomad. Recorded sensitive-access context: Travel identity/preferences; Itineraries; Booking/payment context; Agent reward data.

What limitations and risks should I check before use?

Booking/payment actions can create real charges and cancellation consequences; require explicit user confirmation. Bookings are real external side effects and may involve payment/penalties. Agent booking path requires an Agent DID. Social-account personalization is optional. Some categories such as rideshare/dining were not fully live. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is transactional. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.

Is this an official MCP?

Autonomad is listed as First-party MCP in MCP100’s current evidence.