Is io.github.tools-mcp/vessel-traffic-mcp safe to use?

io.github.tools-mcp/vessel-traffic-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.tools-mcp/vessel-traffic-mcp?

io.github.tools-mcp/vessel-traffic-mcp can be installed by cloning its GitHub repository and following the setup instructions in the README.

What AI clients work with io.github.tools-mcp/vessel-traffic-mcp?

io.github.tools-mcp/vessel-traffic-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

io.github.tools-mcp/vessel-traffic-mcp

Read-only MCP server for vessel AIS, ship tracking, schedules, and BYOK maritime providers.

0 tools GitHub

No known CVEs

No license

Maintenance unknown

No commit data

Works with most clients

Transport: stdio

0 tools

Grade F

Edit this pageView history

Analytics

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-tools-mcp-vessel-traffic-mcp": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-tools-mcp-vessel-traffic-mcp)](https://mcppedia.org/s/io-github-tools-mcp-vessel-traffic-mcp)

Read me

What io.github.tools-mcp/vessel-traffic-mcp does

Read-only MCP server for vessel AIS, ship tracking, schedules, and BYOK maritime providers.

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

21/100across 5 weighted dimensions

How we score →

0255075100

−79

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Help improve this page

This server is missing a description. Tools and install config are also missing.If you've used it, help the community.

Add information

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.tools-mcp/vessel-traffic-mcp safe to use?: io.github.tools-mcp/vessel-traffic-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.tools-mcp/vessel-traffic-mcp?: io.github.tools-mcp/vessel-traffic-mcp can be installed by cloning its GitHub repository and following the setup instructions in the README.
What AI clients work with io.github.tools-mcp/vessel-traffic-mcp?: io.github.tools-mcp/vessel-traffic-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Similar servers

Others in analytics

View all →

Observability Mcp95

MCP Server for GCP environment for interacting with various Observability APIs.

790 10

io.github.rezmeplxrf/insightsentry_mcp91

MCP server for InsightSentry financial data API - market data, options, screeners, and more

io.github.priyankark/lighthouse-mcp90

MCP server for Google Lighthouse performance metrics

141 2

Last9 Mcp Server89

Last9 MCP Server

55 35

MCP Security Weekly

Get CVE alerts and security updates for io.github.tools-mcp/vessel-traffic-mcp and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Analytics

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-tools-mcp-vessel-traffic-mcp": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-tools-mcp-vessel-traffic-mcp)](https://mcppedia.org/s/io-github-tools-mcp-vessel-traffic-mcp)

Read me

What io.github.tools-mcp/vessel-traffic-mcp does

Read-only MCP server for vessel AIS, ship tracking, schedules, and BYOK maritime providers.

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

README

vessel-traffic-mcp

Read-only Model Context Protocol (MCP) server for vessel identity, AIS-style vessel position data, carrier schedules, vessel schedules, and delay heuristics. It is designed for ChatGPT, Claude, Claude Code, Codex, MCP Inspector, and other MCP clients.

Open source under the MIT license. Pre-1.0; APIs and tool surfaces may change.

Public Access / 배포 상태

Surface	Status	Access
GitHub	Public	https://github.com/tools-mcp/vessel-traffic-mcp
Local MCP server	Ready from source	`git clone`, `npm ci`, `npm run build`, then register `dist/index.js` in your MCP client
Local map UI	Ready from source	`npm run start:map`, then open `http://127.0.0.1:8787`
MCP Registry	Published	`io.github.tools-mcp/vessel-traffic-mcp@0.1.0` is published in the MCP Registry
npm	Public	`@tools-mcp/vessel-traffic-mcp@0.1.0` is published at https://www.npmjs.com/package/@tools-mcp/vessel-traffic-mcp
HTTP directory metadata	Ready from source	`npm run start:http`, then fetch `http://127.0.0.1:3000/.well-known/mcp/server-card.json`
Glama / PulseMCP	Indexing pending	The project is in the official MCP Registry; track directory ingestion in `docs/runbooks/public-sharing.md`
Smithery	HTTPS endpoint pending	The Streamable HTTP server exposes crawler-safe server-card metadata; Smithery submission still needs a stable public HTTPS `/mcp` URL

The npm package and MCP Registry metadata are public. Directory crawlers can use the same metadata already committed in this repository, and the HTTP server exposes a public server-card endpoint for remote listings. Launch copy and directory submission material live in docs/marketing.

English

Overview

vessel-traffic-mcp connects MCP clients to authorized maritime data sources through one normalized, read-only tool surface.

It supports vessel search by name, MMSI, IMO, and callsign; latest position lookup; bounding-box and port-area lookup; recent tracks; port calls; carrier schedules; vessel schedules; and schedule delay heuristics.

Every live or public-provider response must expose provenance: source.provider and source.landingUrl. The project is designed to route users back to the original service, not to hide or rebrand the data source.

Quick Start

git clone https://github.com/tools-mcp/vessel-traffic-mcp.git
cd vessel-traffic-mcp
npm install
npm run lint
npm test
npm run build

The default verification gate uses sanitized fixtures only. It does not call paid or live providers and does not require API keys, accounts, or network access.

Local MCP Setup

For local desktop and CLI clients, run the built server over stdio:

VESSEL_MCP_TRANSPORT=stdio npm start

Use the shared MCP config snippets for Codex CLI, Claude Desktop, or Claude Code. Full client setup lives in docs/runbooks/clients.md, and Codex details live in docs/runbooks/codex.md.

Remote MCP Setup

For remote MCP clients, run Streamable HTTP at /mcp with public /health:

export VESSEL_MCP_TRANSPORT=http
export VESSEL_MCP_HTTP_HOST=127.0.0.1
export VESSEL_MCP_HTTP_PORT=8765
export VESSEL_MCP_AUTH_TOKEN="<a-strong-random-token-you-generated>"
npm run start:http

curl -sf "http://127.0.0.1:8765/health"

MCP requests require Authorization: Bearer <token> when VESSEL_MCP_AUTH_TOKEN is set. See docs/runbooks/streamable-http-server.md and docs/runbooks/deployment-https.md.

Public Providers

Public browser-captured adapte

... View full README on GitHub

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

21/100across 5 weighted dimensions

How we score →

0255075100

−79

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Help improve this page

This server is missing a description. Tools and install config are also missing.If you've used it, help the community.

Add information

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.tools-mcp/vessel-traffic-mcp safe to use?: io.github.tools-mcp/vessel-traffic-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.tools-mcp/vessel-traffic-mcp?: io.github.tools-mcp/vessel-traffic-mcp can be installed by cloning its GitHub repository and following the setup instructions in the README.
What AI clients work with io.github.tools-mcp/vessel-traffic-mcp?: io.github.tools-mcp/vessel-traffic-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.