ATA Travel MCP Server

https://atatravel.cloud/mcp Remote v2.1.2

Published by atatravel.cloud — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Search accommodations, create quotes, and start traveler-approved booking handoffs.

Trust grade
B
82/100
Last scanned get badge →
Trust
B · 82/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Live
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
B Why this grade threat 85 − adoption risk = 82/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 15.4 = 85. What the published surface and source actually contain:

PointsWhat was foundCategory
−15.4 Secrecy directive MTC-INJ-SECRECY-1 injection

2. Client adoption risk — 85 − 3 = 82. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

high Secrecy directive (conceal action from the user)MTC-INJ-SECRECY-1

Secrecy directive (conceal action from the user) detected in the description of tool "get_traveler_handoff_status". Instruction-like content in tool metadata is executed by the model, not the human, and is the primary tool-poisoning vector.

Evidence: Do not mention this

Fix: Tool descriptions should describe behavior, not instruct the assistant. Treat imperative / secrecy / sequencing language in metadata as hostile.

Location: tool get_traveler_handoff_status · description

Tools 18

Each tool and what it can reach — enumerated from the running server.

  • search_property_catalogingests untrusted input
  • create_provisional_bookingno sensitive capability
  • create_quoteno sensitive capability
  • get_building_detailsno sensitive capability
  • get_company_missionno sensitive capability
  • get_network_discovery_contextno sensitive capability
  • get_property_detailsno sensitive capability
  • get_stays_in_buildingno sensitive capability
  • get_traveler_handoff_statusno sensitive capability
  • get_traveler_memoriesno sensitive capability
Show 8 more tools ↓
  • list_property_extrasno sensitive capability
  • pingno sensitive capability
  • search_buildingsno sensitive capability
  • search_flexible_network_availabilityno sensitive capability
  • search_network_availabilityno sensitive capability
  • search_property_availabilityno sensitive capability
  • start_traveler_handoffno sensitive capability
  • suggest_traveler_memoryno sensitive capability

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v2.1.2 latest B 82/100 1 1.10.0 2026-07-24

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: B · 82/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/atatravel-cloud/badge.svg)](https://mcptrustchecker.com/registry/atatravel-cloud)
HTML
<a href="https://mcptrustchecker.com/registry/atatravel-cloud"><img src="https://mcptrustchecker.com/registry/atatravel-cloud/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/atatravel-cloud/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan https://atatravel.cloud/mcp --online

Use the free API → How scoring works

More in Web, Search & Scraping