Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Live AIS ship positions, vessel history, port calls and events, plus sanctions flags. Read-only.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
AuthorizationLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Esta dirección necesita una clave en un header de la solicitud, y el menú para agregar conectores no puede ponerla. Usa Claude Code, Cursor o VS Code.
Ejecuta esto en tu terminal
claude mcp add --transport http ais https://api.aistrail.com/mcp --header 'Authorization: your-value'Completa los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"ais": {
"url": "https://api.aistrail.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"ais": {
"type": "http",
"url": "https://api.aistrail.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Esta dirección necesita una clave en un header de la solicitud, y el menú para agregar conectores no puede ponerla. Usa Claude Code, Cursor o VS Code.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Authorization secreto HTTP headerEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Nombres y descripciones de las herramientas tal como los informó el servidor el 7 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.
search_vesselsFind 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_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) and ETA as given by the crew, how long ago it was heard, its track over the last 40 minutes, and th
vessels_in_areaShips 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_nearShips 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_trackWhere 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_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 per source with available_until (the latest time vessel_track can return for that source on plans w
find_portFind 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_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 unchanged, from the draught change), previous and next port. Give mmsi or imo. A port call starts whe
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 departure, cargo estimate, previous and next port. Get the port_id from find_port. event: any (in port at an
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, in arrival order. Available for Finnish ports; elsewhere the list is empty. Get the port_id from f
vessel_eventsEvents 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_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, estimated deadweight, first and last seen) and sanctions flags by IMO number from three official lists
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con el dominio aistrail.com (el registro comprueba quién es dueño del dominio)
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Respondió en 396 ms (HTTP 200)
No hace falta iniciar sesión
Leímos 12 descripciones de herramientas y no encontramos instrucciones ocultas para la IA
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 3 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: Authorization
Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.
El repo de GitHub cambió por última vez –, y la última versión (1.6.0) llegó al registro hoy.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, AvaHR
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Read hiring data and create inactive assessment and questionnaire drafts for human review.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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
| Endpoint | https://api.aistrail.com/mcp |
| Transport | Streamable HTTP, stateless (one JSON response per request) |
| Protocol versions | 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26 |
| Authentication | Authorization: Bearer , required only for the archive tools |
| Registry | com.aistrail/ais in the official MCP Registry; also on Smithery |
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.
Ask in plain words; the assistant picks the tools.
All tools are read-only.
| Tool | Answers | API key |
|---|---|---|
search_vessels | Ships by name, MMSI or IMO number, live ships first | No |
get_vessel | One ship now: identity, flag, size, position, speed, course, destination, ETA and its recent track | No |
vessels_in_area | Ships heard in the last hour inside a box, largest first, optionally by ship type | No |
vessels_near | Ships heard in the last hour near a point or another ship, nearest first | No |
find_port | Ports by name, UN/LOCODE or country | No |
data_status | Live ship count, archive coverage per source and service status | No |
vessel_track | Where a ship has been between two times | Yes |
vessel_port_calls | A ship's port calls with draught, cargo estimate and sanctions flags | Yes |
port_calls | Arrivals and departures at one port | Yes |
vessel_events | Port and anchorage calls, stops, identity and destination changes, AIS gaps and encounters | Yes |
lookup_vessels | Records 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.
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:
| Tool | Credits |
|---|---|
vessel_track | 1 per vessel-day |
vessel_port_calls, port_calls | 1 per port call returned |
vessel_events | 1 per event returned |
lookup_vessels | 1 per vessel found |
See Pricing for plans and the REST API documentation for the underlying endpoints.
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.