MarineTraffic MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is MarineTraffic MCP Server?

MarineTraffic MCP Server is a Model Context Protocol (MCP) server that provides access to MarineTraffic vessel tracking data, allowing users to retrieve real-time information about vessels.

how to use MarineTraffic MCP Server?

To use the MarineTraffic MCP Server, you need to clone the repository, install the necessary dependencies, and configure it with a valid MarineTraffic API key. Once set up, you can access vessel tracking data through various tools provided by the server.

key features of MarineTraffic MCP Server?

  • Real-time vessel position tracking by MMSI or IMO number
  • Detailed vessel information retrieval
  • Vessel search functionality by name, MMSI, IMO, or type
  • Geographic area vessel tracking

use cases of MarineTraffic MCP Server?

  1. Tracking the real-time position of commercial vessels.
  2. Searching for specific vessels by name or identification number.
  3. Monitoring vessel traffic in a specific geographic area.

FAQ from MarineTraffic MCP Server?

  • What is required to run the MarineTraffic MCP Server?

You need Node.js 18 or higher and a valid MarineTraffic API key.

  • How do I configure the server?

You can configure the server by editing the MCP settings configuration file with your API key and server details.

  • Are there any usage limits?

Yes, the MarineTraffic API has usage limits based on your subscription plan.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago