Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Japan Port Vessel Traffic MCP (AIS Position & ETA)

MCPB · SERVER.MCPB

Port vessel traffic MCP Apify apify.com/fruitful_quintessence Gumroad atushi5.gumroad.com/l/kutuxe

Available components

mcpb · server.mcpb 5
5 Trust /100

Last scanned (3 hours ago)

Scores higher than 8% of MCPB servers

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it.Unverified
  • Install-script risk could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it.Unverified
  • Dependency health could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it.Unverified
Provenance & Transparency26
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Build provenance could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it. View diagnostics → Unverified
  • Licence could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it.Unverified
  • Maintenance history could not be checked: the bundle we downloaded does not match the SHA-256 its registry entry declares, so we did not read it. Either the file changed after that digest was published or the digest is wrong; check the file before you install it.Unverified
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we never saw its MCP handshake.Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Oct 26 5

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 19 Oct 2026 · Analysed mcpb/https://github.com/atushi1841/japan-port-vessel-mcp/releases/download/v0.1.0/server.mcpb@0.1.0

Provenance Inconclusive

We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.

Result Inconclusive
Ecosystem mcpb
Reason Bundle digest mismatch

Background: How many MCP packages publish verified provenance →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.

Install

How do I install the Japan Port Vessel Traffic MCP (AIS Position & ETA) server?

Japan Port Vessel Traffic MCP (AIS Position & ETA) ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 99c37dbb9e1a333c0fc8585b531db707eb7aabfc75a20baa22a82817e04213ec; the commands to do that are on this page. If it does not match, do not open it.

mcpb · server.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

99c37dbb9e1a333c0fc8585b531db707eb7aabfc75a20baa22a82817e04213ec

macOS / Linux 

echo "99c37dbb9e1a333c0fc8585b531db707eb7aabfc75a20baa22a82817e04213ec  server.mcpb" | shasum -a 256 -c

Windows (PowerShell) 

(Get-FileHash -Algorithm SHA256 .\server.mcpb).Hash -eq "99c37dbb9e1a333c0fc8585b531db707eb7aabfc75a20baa22a82817e04213ec"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.