ATAbooking

Is ATAbooking MCP server safe?

• None of the hidden-instruction wordings we know were found in its tool descriptions.
• Its error messages showed no secrets or internal details.
• 3 of its 5 tools are labeled read-only; the others may change or send things.
• Overall it scored 88/100 on 1 Nov 2026.

A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.

What it can do

5 tools, in the server's own words.

Test results

Safe mode: only tools labeled read-only were run. How the test works

• !
  Ready for the newest MCP version

  1 warning

  • !Uses an older MCP version (2025-11-25). It works today, but it isn't on the July 2026 version (2026-07-28) yet.
  note
• !
  Every tool is described

  3 warnings

  • !get_stay: Inputs with no description: guests
  • !check_availability: Inputs with no description: stay_id, room_id, check_in, check_out, guests
  • !book_direct: Inputs with no description: stay_id, room_id, check_in, check_out, guests, guest_name, guest_email, guest_phone
  note
• ✓
  ConnectsConnected in 1.0 s
  pass
• ✓
  Lists its toolsFound 5 tools
  pass
• ✓
  Tools are labeled safe or dangerousEvery tool has a safety label
  pass
• ✓
  No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.
  pass
• ✓
  Tools work with good inputs

  All good

  • ✓search_stays: Answered with an error, probably because of our sample input: MCP error -32602: Input validation error: Invalid arguments for tool search_stays: YYYY-MM-DD at check_in YYYY-MM-DD at check_out
  • ✓get_stay: Answered with an error, probably because of our sample input: { "error": "Unknown stay_id 'test'." } {"error":"Unknown stay_id 'test'."}
  • ✓check_availability: Answered with an error, probably because of our sample input: MCP error -32602: Input validation error: Invalid arguments for tool check_availability: YYYY-MM-DD at check_in YYYY-MM-DD at check_out
  • –book_direct: Not run: labeled as changing data
  • –confirm_booking: Not run: labeled as changing data
  pass
• ✓
  Bad inputs give a clean error

  All good

  • ✓search_stays: Refused missing required input "place" with a clear error
  • ✓search_stays: Refused wrong type for "place" with a clear error
  • ✓get_stay: Refused missing required input "stay_id" with a clear error
  • ✓get_stay: Refused wrong type for "stay_id" with a clear error
  • ✓check_availability: Refused missing required input "stay_id" with a clear error
  • ✓check_availability: Refused wrong type for "stay_id" with a clear error
  pass
• ✓
  Fast enough

  All good

  • ✓Connecting took 1.0 s
  • ✓Listing tools took 127 ms
  • ✓Average tool answer: 128 ms
  • ✓search_stays: Slowest tool: search_stays (130 ms)
  pass
• ✓
  No secrets leakedChecked 9 error messages: no secrets or internal details
  pass
• ✓
  Follows MCP best practices (not scored yet)Tool names, safety labels and tool list size follow the MCP guide
  pass
• –
  Tools work togetherNo safe tool returned data to start a chain from, so chains were not tested (not counted either way)
  not tested

Test it yourself

Free and open source. Same checks, same score.

Show this score on GitHub

Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.

Score over time

• 1 Nov 202688

One test so far. New tests will show here.

Reviews

Coming soon: reviews from people who use ATAbooking, signed in with GitHub, one per person. Reviews never change the score.