Fetch and follow the instructions at https://qamcp.dev/setup.md to test my MCP server.Your AI finds your server in your project, tests it with QAmcp, explains what's wrong in plain words, fixes it with your OK, and tests again. Read the instructions
Directory / AIS Trail
AIS Trail
by aistrail.com · https://api.aistrail.com/mcp
Live AIS ship positions, vessel history, port calls and events, plus sanctions flags. Read-only.
11 of 11 checks · 6 Nov 2026
At a glance
- Runs where
- On their server. What you send to it goes to them.
- What you need
- Nothing: it answered without a login
- Tools
- 12 tools
- Its own safety labels
- 12 read-only
- Memory it takes
- About 4,200 tokens of your AI's memory, just for its tool descriptions
- Largest answer
- About 3.2 KB in our test
- Tools that look alike
- 3 pairs of tools with nearly the same description, so the AI may pick the wrong one
- Speed
- Average answer in our test: 221 ms
Tokens are an estimate: the characters in its tool names, descriptions and inputs, divided by 4. The exact number depends on your AI model. Safety labels are what the server says about itself. From our latest test, 6 Nov 2026.
Is AIS Trail MCP server safe?
- None of the hidden-instruction wordings we know were found in its 12 tool descriptions.
- Its error messages showed no secrets or internal details.
- All 12 of its tools are labeled read-only.
- Overall it scored 93/100 on 6 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 this test does not check
- Its source code and packages.
- What a tool quietly does behind the scenes, such as writing a file or calling another service.
- Instructions hidden inside live tool answers. We only look for those in tool descriptions.
- Hidden instructions worded in a way our list doesn't know yet.
- Tools that could change something. Those are read, never run.
What QAmcp can and can't see · How to tell if an MCP server is safe · Hidden instructions · Prompt injection
Known security advisories
Not looked up yet. QAmcp tests how a server behaves. It does not scan source code.
What it can do
12 tools, in the server's own words.
search_vesselsread-onlyFind ships by name (or part of it), MMSI (9 digits) or IMO number (7 digits).
get_vesselread-onlyEverything known about one ship now: identity (name, IMO, call sign, flag, type, size), last position, speed, course, heading, navigational status, destination…
vessels_in_arearead-onlyShips heard in the last hour inside a box (at most 5° on each side), largest first.
vessels_nearread-onlyShips heard in the last hour within a radius (at most 50 nautical miles) of a point or of another ship, nearest first.
vessel_trackread-onlyWhere a ship has been between two times (UTC, ISO 8601), from the AIS Trail archive.
data_statusread-onlyHow many ships are live now (live_ships_private: how many of them are private vessels, counted only), how many are known from the last 7 days, the date range o…
find_portread-onlyFind ports by name (or part of it), UN/LOCODE (e.g.
vessel_port_callsread-onlyPort calls of a ship between two times (UTC, ISO 8601), from the AIS Trail archive: port, arrival, departure, draught on arrival and departure, cargo estimate …
port_callsread-onlyShips that called at one port between two times (UTC, ISO 8601), from the AIS Trail archive: ship (with its flag from the MMSI), arrival, departure, draught on…
expected_arrivalsread-onlyShips that have not arrived yet at one port, from the port's own records: estimated arrival and departure (UTC), berth and declared previous port, from 6 hours…
vessel_eventsread-onlyEvents of a ship between two times (UTC, ISO 8601), computed from the AIS Trail archive.
lookup_vesselsread-onlyRecords of up to 20 ships at once from the AIS Trail archive, by mmsi and/or imo (lists): identity and particulars (name, IMO, call sign, type, flag from the M…
Test results
Safe mode: only tools labeled read-only were run. How the test works
- !Every tool is describednote
3 warnings
- !vessels_in_area and vessels_near have nearly the same description (83% of their words are shared; the only difference: "inside", "box", "side" vs "within", "radiu", "nautical"), so an AI may not know which to pick
- !search_vessels and vessels_in_area have nearly the same description (74% of their words are shared; the only difference: "find", "part", "digit" vs "heard", "hour", "inside"), so an AI may not know which to pick
- !search_vessels and vessels_near have nearly the same description (70% of their words are shared; the only difference: "find", "part", "digit" vs "heard", "hour", "within"), so an AI may not know which to pick
- ✓ConnectsConnected in 519 mspass
- ✓Ready for the newest MCP versionUses the latest MCP version (2026-07-28)pass
- ✓Lists its toolsFound 12 toolspass
- ✓Tools are labeled safe or dangerousEvery tool has a safety labelpass
- ✓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 inputspass
All good
- ✓search_vessels: Worked (289 ms)
- ✓get_vessel: Answered with an error, probably because of our sample input: No ship with MMSI 1 is available: it has not been heard in the last 7 days or is not served. Private vessels (pleasure craft, sailing vesse…
- ✓vessels_in_area: Answered with an error, probably because of our sample input: box must satisfy min < max for both latitude and longitude
- ✓vessels_near: Answered with an error, probably because of our sample input: give lat and lon, or an mmsi to use as the centre
- ✓vessel_track: Answered with an error, probably because of our sample input: vessel_track needs an AIS Trail API key. Add the HTTP header 'Authorization: Bearer ap_live_…' to this MCP server in your client's configur…
- ✓data_status: Worked (812 ms)
- ✓find_port: Answered with an error, probably because of our sample input: give a query (port name), a country or a locode
- ✓vessel_port_calls: Answered with an error, probably because of our sample input: vessel_port_calls needs an AIS Trail API key. Add the HTTP header 'Authorization: Bearer ap_live_…' to this MCP server in your client's con…
- and 4 more
- ✓Bad inputs give a clean errorpass
All good
- ✓search_vessels: Refused missing required input "query" with a clear error
- ✓search_vessels: Refused wrong type for "query" with a clear error
- ✓get_vessel: Refused missing required input "mmsi" with a clear error
- ✓get_vessel: Refused wrong type for "mmsi" with a clear error
- ✓vessels_in_area: Refused missing required input "min_lat" with a clear error
- ✓vessels_in_area: Refused wrong type for "min_lat" with a clear error
- ✓vessels_near: Refused wrong type for "lat" with a clear error
- ✓vessel_track: Refused missing required input "mmsi" with a clear error
- and 10 more
- ✓Fast enoughpass
All good
- ✓Connecting took 519 ms
- ✓Listing tools took 186 ms
- ✓Average tool answer: 221 ms
- ✓data_status: Slowest tool: data_status (812 ms)
- ✓No secrets leakedChecked 28 error messages: no secrets or internal detailspass
- ✓Follows MCP best practices (not scored yet)Tool names, safety labels and tool list size follow the MCP guidepass
- –Tools work togetherNo tool's answer could be fed into another tool, so there were no chains to test (not counted either way)not tested
Test it yourself
Free and open source. Same checks, same score.
npx qamcp-cli https://api.aistrail.com/mcpShow 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.
[](https://qamcp.dev/s/com-aistrail-ais.html)Score over time
- 6 Nov 202693
One test so far. New tests will show here.
Reviews
Coming soon: reviews from people who use AIS Trail, signed in with GitHub, one per person. Reviews never change the score.
QAmcp Monitor tests it every hour and emails you when it goes down, the score drops, a tool changes or a secret leaks. Free for 1 server, no card.
Have a concern, or want it removed? Ask us and we'll take it off the list. How the directory works