AIS Trail MCP server
com.aistrail/aisaistrail.comstreamable-httpv1.6.0Scanned
Live AIS ship positions, vessel history, port calls and events, plus sanctions flags. Read-only.
12 tools: 4 do something that can't be undone, 3 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 6
- Can send data out · 4
- 4 findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the AIS Trail MCP server can do
The AIS Trail MCP server is published by aistrail.com, a domain the MCP Registry verified. It has 12 tools. It can do things that cannot be undone, such as sending, paying or publishing (vessel_track, vessel_port_calls, port_calls and vessel_events) and create or change data (3 tools: vessels_in_area, vessels_near and expected_arrivals), but cannot delete data. 5 tools only read.
6 tools bring in text other people can write (vessel_track, vessel_port_calls, port_calls and 3 more); 4 tools can send data out of your system (vessel_track, vessel_port_calls, port_calls and 1 more).
The fixed checks matched 4 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 1.6.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
12 tools
Can't be undone 4Claude Code: ask
port_callsShips 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 arrival and departur…Reads text others writeCan send data out1 finding
Why it is in this group
- The name "port_calls" says "call": a word for a change.
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "port_calls" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "port_calls" says "call": a word for a change.
Description, as the server wrote it Ships 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 arrival and departure, cargo estimate, previous and next port. Get the port_id from find_port. event: any (in port at any time in the range, default), arrival or departure. The sanctions column gives the codes of the sanctions lists (OFAC, UK, EU) that name the ship's IMO number; informational only, not a compliance determination. Needs an AIS Trail account: sign in when the MCP client asks, or send an API key as the HTTP header 'Authorization: Bearer ap_live_…'. At most 100 port calls per call and at most 366 days; the plan's rules and credits (1 per port call returned) apply as for vessel_port_calls.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- title: Port arrivals and departures (account)
vessel_eventsEvents of a ship between two times (UTC, ISO 8601), computed from the AIS Trail archive.Reads text others writeCan send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "vessel_events" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.
Description, as the server wrote it Events of a ship between two times (UTC, ISO 8601), computed from the AIS Trail archive. from and to are optional: without to, now (24 hours ago on plans without live data); without from, 7 days before to (on Free, no earlier than the oldest day the plan includes), as on the REST endpoint. Give mmsi or imo (with imo, every MMSI that reported that IMO number in the range). Types: ENTER_ZONE and EXIT_ZONE (arrival at and departure from a port or anchorage; port_id for port_calls, zone port or anchorage), STATE_CHANGED (MOVING, NOT_MOVING, LONG_STOP), NAME_CHANGED, IMO_CHANGED, CALLSIGN_CHANGED, DESTINATION_CHANGED and DRAUGHT_CHANGED (old and new value); only when asked by name or with types ['all']: AIS_GAP (long AIS silence while under way; old_value hours, new_value nautical miles), ENCOUNTER (slow close approach to another ship outside port areas, a candidate ship-to-ship transfer; new_value the other ship's MMSI), FLAG_CHANGED (the IMO number reappears under an MMSI with another flag) and POSITION_JUMP (a physically impossible position jump). Rows: [time, event, old_value, new_value, lat, lon, mmsi, port_id, zone, sanctions, detail]; detail says more about behaviour events. The sanctions column gives the codes of the sanctions lists (OFAC, UK, EU) that name the ship's IMO number; informational only, not a compliance determination. Needs an AIS Trail account: sign in when the MCP client asks, or send an API key as the HTTP header 'Authorization: Bearer ap_live_…'. At most 200 events per call and at most 31 days; the plan's history depth, credits (1 per event returned), rate limit and 24-hour delay (on plans without live data) apply.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- title: Ship events (account)
vessel_port_callsPort 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 (loaded, ballast or u…Reads text others writeCan send data out1 finding
Why it is in this group
- The name "vessel_port_calls" says "call": a word for a change.
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "vessel_port_calls" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "vessel_port_calls" says "call": a word for a change.
Description, as the server wrote it Port 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 (loaded, ballast or unchanged, from the draught change), previous and next port. Give mmsi or imo. A port call starts when the ship stops inside a port area and ends when it leaves; departure is null while it is still in port. The sanctions column gives the codes of the sanctions lists (OFAC, UK, EU) that name the ship's IMO number; informational only, not a compliance determination. Needs an AIS Trail account: sign in when the MCP client asks, or send an API key as the HTTP header 'Authorization: Bearer ap_live_…'. At most 100 port calls per call and at most 366 days; the plan's history depth, credits (1 per port call returned), rate limit and 24-hour delay (on plans without live data) apply.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- title: Ship port calls (account)
vessel_trackWhere a ship has been between two times (UTC, ISO 8601), from the AIS Trail archive.Reads text others writeCan send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "vessel_track" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.
Description, as the server wrote it Where a ship has been between two times (UTC, ISO 8601), from the AIS Trail archive. Needs an AIS Trail account: sign in when the MCP client asks, or send an API key as the HTTP header 'Authorization: Bearer ap_live_…' (keys at https://aistrail.com). Resolution: raw (up to 24 h per call), 1m (up to 7 days) or 1h (up to 366 days); at most 200 points per call, as rows of [time, lat, lon, speed_kn, course_deg]. The plan's history depth, credits (as on the track endpoint: 1 per vessel-day) and rate limit apply, and the 24-hour delay on recent data on plans without live data. sources_through gives, per source, the time up to which the archive holds its data; pending_days lists days in the range a source has not delivered yet, so no points on those days does not mean the ship was absent.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- title: Ship history (account)
Changes things 3Claude Code: ask
expected_arrivalsShips 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 ago to 14 days ahead…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Ships 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 ago to 14 days ahead, in arrival order. Available for Finnish ports; elsewhere the list is empty. Get the port_id from find_port. Needs an AIS Trail account (sign in when the MCP client asks, or send an API key as the HTTP header 'Authorization: Bearer ap_live_…') and a plan with live data (Pro or Business); at most 200 ships per call, 1 credit per ship returned.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- title: Ships expected at a port (account)
vessels_in_areaShips heard in the last hour inside a box (at most 5° on each side), largest first.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Ships heard in the last hour inside a box (at most 5° on each side), largest first. List results are compact rows (mmsi, name, category, flag (ISO code from the MMSI), lat, lon, speed_kn, course_deg, length_m, destination, age_s, status, source); call get_vessel for full details of one ship. Private vessels (pleasure craft, sailing vessels and Class B transponders without a valid IMO number) are never listed or looked up individually; area and nearby results report how many were left out (private_vessels).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Ships in an area
vessels_nearShips heard in the last hour within a radius (at most 50 nautical miles) of a point or of another ship, nearest first.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Ships heard in the last hour within a radius (at most 50 nautical miles) of a point or of another ship, nearest first. List results are compact rows (mmsi, name, category, flag (ISO code from the MMSI), lat, lon, speed_kn, course_deg, length_m, destination, age_s, status, source); call get_vessel for full details of one ship. Private vessels (pleasure craft, sailing vessels and Class B transponders without a valid IMO number) are never listed or looked up individually; area and nearby results report how many were left out (private_vessels).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Ships near a point or ship
Only reads 5Show 5 read-only tools
data_statusHow 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 of the history archive…No findings
Why it is in this group
- The name "data_status" says "status": a word for reading.
Description, as the server wrote it How 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 of the history archive per source with available_until (the latest time vessel_track can return for that source on plans without live data), and the service status: ok or degraded, with reason codes in reasons.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Coverage and freshness
find_portFind ports by name (or part of it), UN/LOCODE (e.g.No findings
Why it is in this group
- The name "find_port" says "find": a word for reading.
Description, as the server wrote it Find ports by name (or part of it), UN/LOCODE (e.g. FIHEL) or two-letter country code (e.g. FI) in the port reference (World Port Index and UN/LOCODE ports): id (for port_calls), name, country, UN/LOCODE, position, harbor size (World Port Index ports only) and the radius of the port area used to detect port calls. At most 20 ports, larger harbors first. No API key needed.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Find ports
get_vesselEverything known about one ship now: identity (name, IMO, call sign, flag, type, size), last position, speed, course, heading, navigational status, destination (port codes decoded)…No findings
Why it is in this group
- The name "get_vessel" says "get": a word for reading.
Description, as the server wrote it Everything known about one ship now: identity (name, IMO, call sign, flag, type, size), last position, speed, course, heading, navigational status, destination (port codes decoded) and ETA as given by the crew, how long ago it was heard, its track over the last 40 minutes, and the data sources to credit. flag (ISO code) and flag_country come from the MMSI: the flag of the radio licence, usually but not always the registry flag. dwt_estimate is an estimate from the AIS dimensions (tonnes, size class such as Panamax or VLCC, hull, draught used), not a registry value; null for tugs, pleasure craft and other types where deadweight does not apply. For archive records and sanctions flags, use lookup_vessels (account).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Ship details and position
lookup_vesselsRecords 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 MMSI, length, beam, es…Reads text others writeNo findings
Why it is in this group
- The name "lookup_vessels" says "lookup": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Records 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 MMSI, length, beam, estimated deadweight, first and last seen) and sanctions flags by IMO number from three official lists: OFAC SDN, UK Sanctions List and EU Regulation 833/2014 Annex XLII (list, programmes, date listed). An IMO number resolves to the MMSI that reported it last; ships not in the plan's sources come back with found false. Sanctions flags are informational, not a compliance determination: only ships a list names by IMO number are matched, ownership-based sanctions are not covered. Needs an AIS Trail account: sign in when the MCP client asks, or send an API key as the HTTP header 'Authorization: Bearer ap_live_…'. Credits: 1 per ship returned (none for ships not found); the plan's sources and 24-hour delay (on plans without live data) apply.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- title: Ship records and sanctions (account)
search_vesselsFind ships by name (or part of it), MMSI (9 digits) or IMO number (7 digits).No findings
Why it is in this group
- The name "search_vessels" says "search": a word for reading.
Description, as the server wrote it Find ships by name (or part of it), MMSI (9 digits) or IMO number (7 digits). Returns live ships first, then ships out of range with their last known position (up to 7 days). List results are compact rows (mmsi, name, category, flag (ISO code from the MMSI), lat, lon, speed_kn, course_deg, length_m, destination, age_s, status, source); call get_vessel for full details of one ship. Private vessels (pleasure craft, sailing vessels and Class B transponders without a valid IMO number) are never listed or looked up individually; area and nearby results report how many were left out (private_vessels).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Search ships
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write6
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out4
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:33 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 7
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.aistrail.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://app.aistrail.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- no
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 7 tools that change things (4 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.aistrail.com/mcp: tools/list returned 12 tools to an anonymous client, including vessel_track (irreversible), vessel_port_calls (irreversible), port_calls (irreversible), vessel_events (irreversible), vessels_in_area (write) and 2 more
Posture changes
- Nov 20, 2026
- RFC 9728 protected resource metadata: none to https://api.aistrail.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://app.aistrail.com
- Dynamic client registration: not observed to no
- Client ID metadata documents: not observed to yes
- Nov 13, 2026
- Tools that change things, listed without credentials: 6 to 7
Findings
Matches of fixed checks, with the text they matched.
- Warnvessel_track
The server marks "vessel_track" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.
The server marks "vessel_port_calls" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "vessel_port_calls" says "call": a word for a change.
- Warnport_calls
The server marks "port_calls" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "port_calls" says "call": a word for a change.
- Warnvessel_events
The server marks "vessel_events" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools7 changed.~7 changedView diff
- Changed:expected_arrivalsChanges thingstitledescriptionannotations
- Changed:get_vesselOnly readsdescription
- Changed:lookup_vesselsOnly readstitledescriptionannotations
- Changed:port_callsCan't be undonetitledescriptionannotations
- Changed:vessel_eventsCan't be undonetitledescriptionannotations
- Changed:vessel_port_callsCan't be undonetitledescriptionannotations
- Changed:vessel_trackCan't be undonetitledescriptionannotations
PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://api.aistrail.com/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://app.aistrail.com; Dynamic client registration: not observed -> n…View diff
- RFC 9728 protected resource metadata: none to https://api.aistrail.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://app.aistrail.com
- Dynamic client registration: not observed to no
- Client ID metadata documents: not observed to yes
PostureRemote posture changed. Tools that change things, listed without credentials: 6 -> 7.View diff
- Tools that change things, listed without credentials: 6 to 7
Tools1 added, 8 changed.+1 added~8 changedView diff
- Added:expected_arrivalsChanges things
- Changed:find_portOnly readsdescriptioninputSchema
- Changed:port_callsCan't be undoneinputSchema
- Changed:search_vesselsOnly readsinputSchema
- Changed:vessel_eventsCan't be undoneinputSchema
- Changed:vessel_port_callsCan't be undonedescriptioninputSchema
- Changed:vessel_trackCan't be undoneinputSchema
- Changed:vessels_in_areaChanges thingsinputSchema
- Changed:vessels_nearChanges thingsinputSchema
Install
Pinned to version 1.6.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http ais https://api.aistrail.com/mcpclaude mcp add --transport http ais https://api.aistrail.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ais__search_vessels",
"mcp__ais__get_vessel",
"mcp__ais__data_status",
"mcp__ais__find_port",
"mcp__ais__lookup_vessels"
],
"ask": [
"mcp__ais__vessels_in_area",
"mcp__ais__vessels_near",
"mcp__ais__vessel_track",
"mcp__ais__vessel_port_calls",
"mcp__ais__port_calls",
"mcp__ais__expected_arrivals",
"mcp__ais__vessel_events"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ais. Review it before you use it.
Capability tags behind 6 rules
- mcp__ais__vessel_track untrusted-input, outbound
- mcp__ais__vessel_port_calls untrusted-input, outbound
- mcp__ais__port_calls untrusted-input, outbound
- mcp__ais__expected_arrivals untrusted-input
- mcp__ais__vessel_events untrusted-input, outbound
- mcp__ais__lookup_vessels untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.aistrail/ais/verify?hash=aed19da7c340cb58b96ce33cc7293d8c527a0252f2dae26e8ad41d5587c40987" | jq -e '.changed == false'Pinned hash aed19da7c340, from Nov 20, 2026, 22:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.aistrail/ais/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.aistrail/ais)Source: MCP Registry · repository. Synced Nov 6, 2026, 19:17 UTC.
AIS Trail MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the AIS Trail MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 7 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the AIS Trail MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the AIS Trail MCP server do things that cannot be undone?
- Yes. 4 tools can send, pay, publish or merge: vessel_track, vessel_port_calls, port_calls and vessel_events.
What tools does the AIS Trail MCP server have?
- 12 tools: 4 irreversible, 3 write, 5 read. vessel_track, vessel_port_calls, port_calls, vessel_events, vessels_in_area, vessels_near, expected_arrivals, search_vessels and 4 more.
Does the AIS Trail MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the AIS Trail MCP server send data to outside services?
- 4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): vessel_track, vessel_port_calls, port_calls and vessel_events.
Has the AIS Trail MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.