verify_traveler_code — ATA Travel MCP Tool
verify_traveler_code
(verify traveler code) is one of 24 tools on the
ATA Travel
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verify_traveler_code from your client
- Claude Code ATA Travel verify_traveler_code run in your project directory
- Claude Desktop ATA Travel verify_traveler_code ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ATA Travel verify_traveler_code ~/.cursor/mcp.json
- VS Code ATA Travel verify_traveler_code .vscode/mcp.json
- Zed ATA Travel verify_traveler_code ~/.config/zed/settings.json
- Windsurf ATA Travel verify_traveler_code ~/.codeium/windsurf/mcp_config.json
- Cline ATA Travel verify_traveler_code ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ATA Travel verify_traveler_code ~/.gemini/settings.json
- Grok ATA Travel verify_traveler_code .mcp.json (in your project root)
- ChatGPT ATA Travel verify_traveler_code Settings → Connectors → Advanced → Developer mode
- Claude.ai ATA Travel verify_traveler_code Settings → Connectors → Add custom connector
- LangChain ATA Travel verify_traveler_code pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http travel-agency https://atatravel.cloud/mcpOther tools on this server
- ping
- get_network_discovery_context
- search_flexible_network_availability
- get_company_mission
- get_traveler_memories
- suggest_traveler_memory
- search_property_availability
- search_network_availability
- search_buildings
- get_building_details
- get_stays_in_building
- search_property_catalog
- get_property_details
- get_support_contacts
- list_property_extras
- start_traveler_verification
- get_traveler_verification_status
- start_traveler_handoff
- get_traveler_handoff_status
- get_booking_details
- get_reservation_status
- create_provisional_booking
- create_quote
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.