Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

AIS Trail

by aistrailversion 1.6.0i★ –iRuns in the cloud
Registry namecom.aistrail/ais

Install

Overview

Description from the maker (original English)

Live AIS ship positions, vessel history, port calls and events, plus sanctions flags. Read-only.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Other
  • You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http ais https://api.aistrail.com/mcp --header 'Authorization: your-value'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "ais": {
      "url": "https://api.aistrail.com/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "ais": {
      "type": "http",
      "url": "https://api.aistrail.com/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • Authorization secret HTTP header
    Optional. "Bearer " for the archive tools (vessel_track, vessel_port_calls, port_calls, expected_arrivals, vessel_events, lookup_vessels). The live tools work without it.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.

  • search_vessels

    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, c

  • get_vessel

    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 th

  • vessels_in_area

    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

  • vessels_near

    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)

  • vessel_track

    Where a ship has been between two times (UTC, ISO 8601), from the AIS Trail archive. Needs an AIS Trail API key sent by the MCP client as the HTTP header 'Authorization: Bearer ap_live_…' (keys at https://aistrail.com); clients that cannot add headers (OAuth-only web connectors)

  • data_status

    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 w

  • find_port

    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 p

  • vessel_port_calls

    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 whe

  • port_calls

    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 an

  • expected_arrivals

    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 f

  • vessel_events

    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

  • lookup_vessels

    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

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain aistrail.com (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • ✓ Pass

    Endpoint responds

    Responded in 396 ms (HTTP 200)

  • – Not applicable

    Sign-in with OAuth

    No sign-in needed

  • ✓ Pass

    No hidden instructions in tool descriptions

    Read 12 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

  • More stars than 0% of the other 32684 servers in this category
  • Published to the registry more recently than 98% of the other 32684 servers in this category
  • Basic checks equal to or better than 100% of the other 32684 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is AIS Trail safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.6.0) reached the registry today.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Master CSS

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

Master CSS

by master-co

Inspect Master CSS classes, generated CSS, and project stylesheets from your AI client.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

AIS Trail MCP Server

Ship data for AI assistants. The AIS Trail MCP server gives Claude, ChatGPT, Cursor and any other Model Context Protocol client read-only access to live AIS positions, vessel history, port calls, vessel events and sanctions list flags.

The server is hosted by AIS Trail, so there is nothing to install: point your client at the endpoint below. This repository holds its public documentation.

Website · Documentation · Live map · Coverage · Pricing

Server

Endpointhttps://api.aistrail.com/mcp
TransportStreamable HTTP, stateless (one JSON response per request)
Protocol versions2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26
AuthenticationAuthorization: Bearer , required only for the archive tools
Registrycom.aistrail/ais in the official MCP Registry; also on Smithery

Connect

Claude Code

claude mcp add --transport http aistrail https://api.aistrail.com/mcp \

--header "Authorization: Bearer $AIS_TRAIL_KEY"

Run /mcp in Claude Code to confirm that aistrail is connected.

Other clients. Add a remote (Streamable HTTP) server with the same URL and header. For clients configured with JSON, such as VS Code and Cursor:

{

"servers": { "aistrail": { "type": "http", "url": "https://api.aistrail.com/mcp", "headers": { "Authorization": "Bearer YOUR_AIS_TRAIL_KEY" } } } }

Leave out the header to use the live tools only; clients that cannot send a header (for example connectors that offer only OAuth) work the same way. API keys are created in the AIS Trail dashboard, and the Free plan includes one. Give each client its own key so it can be revoked separately.

Example questions

Ask in plain words; the assistant picks the tools.

  • "Which tankers are off Helsinki right now?"
  • "Find the ship MYSTAR and show where it sailed three days ago."
  • "Which ships called at Turku last week?"
  • "Is the ship with IMO 1234567 on a sanctions list?"
  • "What happened to MMSI 276859000 last week? Include AIS gaps and encounters."

Tools

All tools are read-only.

ToolAnswersAPI key
search_vesselsShips by name, MMSI or IMO number, live ships firstNo
get_vesselOne ship now: identity, flag, size, position, speed, course, destination, ETA and its recent trackNo
vessels_in_areaShips heard in the last hour inside a box, largest first, optionally by ship typeNo
vessels_nearShips heard in the last hour near a point or another ship, nearest firstNo
find_portPorts by name, UN/LOCODE or countryNo
data_statusLive ship count, archive coverage per source and service statusNo
vessel_trackWhere a ship has been between two timesYes
vessel_port_callsA ship's port calls with draught, cargo estimate and sanctions flagsYes
port_callsArrivals and departures at one portYes
vessel_eventsPort and anchorage calls, stops, identity and destination changes, AIS gaps and encountersYes
lookup_vesselsRecords of up to 20 ships at once, with the sanctions lists that name them (OFAC SDN, UK, EU)Yes

Limits and parameters for each tool are in the documentation.

API key and credits

The live tools use no credits. The archive tools call the AIS Trail REST API with your key, so your plan's history depth, credits and rate limits apply exactly as they do in the API:

ToolCredits
vessel_track1 per vessel-day
vessel_port_calls, port_calls1 per port call returned
vessel_events1 per event returned
lookup_vessels1 per vessel found

See Pricing for plans and the REST API documentation for the underlying endpoints.

Data

  • Positions are what ships broadcast over AIS; all times are UTC.
  • Every answer with ship data names the sources to credit. Coverage and sources: coverage map, data sources.
  • Private vessels (pleasure craft, sailing vessels and Class B transponders without a valid IMO number) are never listed or looked up; area and nearby results only count them.
  • Not for navigation.

Support

Open an issue in this repository or write to hello@aistrail.com.

Use of the server is subject to the Terms of Service and the Privacy Policy.

Ask PopNx