Shipxy Api MCP Server

mcp-shipxy-api PyPI v0.1.0

Published by garrettxu — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Shipxy MCP server and CLI for maritime vessel, port, route, weather, and tide APIs.

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 96 − adoption risk = 95/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 3.6 = 96. What the published surface and source actually contain:

PointsWhat was foundCategory
−3.6 Hidden zero-width / joiner character in description MTC-UNI-005 injection

2. Client adoption risk — 96 − 1 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

medium Hidden zero-width / joiner character in descriptionMTC-UNI-005

Found 2 zero-width / joiner character character(s) in the description of tool "search_ship". These are invisible to a human reviewer but are read verbatim by the model.

Evidence: 2× zero-width

Fix: Reject or normalize server metadata containing invisible/smuggling characters. Legitimate tool descriptions do not need them.

Location: tool search_ship · description

Tools 27

Each tool and what it can reach — statically extracted from the published source.

  • get_all_typhoonno sensitive capability
  • get_anchor_shipsno sensitive capability
  • get_area_shipno sensitive capability
  • get_berth_shipsno sensitive capability
  • get_eta_shipsno sensitive capability
  • get_fleet_shipno sensitive capability
  • get_many_shipno sensitive capability
  • get_port_of_call_by_portno sensitive capability
  • get_port_of_call_by_shipno sensitive capability
  • get_port_of_call_by_ship_portno sensitive capability
Show 17 more tools ↓
  • get_ship_registryno sensitive capability
  • get_ship_statusno sensitive capability
  • get_ship_trackno sensitive capability
  • get_single_eta_preciseno sensitive capability
  • get_single_shipno sensitive capability
  • get_single_typhoonno sensitive capability
  • get_surrounding_shipno sensitive capability
  • get_tide_datano sensitive capability
  • get_tidesno sensitive capability
  • get_weatherno sensitive capability
  • get_weather_by_pointno sensitive capability
  • plan_route_by_pointno sensitive capability
  • plan_route_by_portno sensitive capability
  • search_portno sensitive capability
  • search_shipno sensitive capability
  • search_ship_approachno sensitive capability
  • search_ship_particularno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.0 latest A 95/100 1 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-shipxy-api/badge.svg)](https://mcptrustchecker.com/registry/mcp-shipxy-api)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-shipxy-api"><img src="https://mcptrustchecker.com/registry/mcp-shipxy-api/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-shipxy-api/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-shipxy-api --online --registry pypi

Use the free API → How scoring works

More in Lifestyle & Local