Voyageintel MCP Server

voyageintel PyPI v1.0.0

Published by 0xchamin — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Trust grade
B
88/100
Last scanned
Trust
B · 88/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
Moderate
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.
B Why this grade threat 96 − adoption risk = 88/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 − 4.2 = 96. What the published surface and source actually contain:

PointsWhat was foundCategory
−2.1 Package has no source repository MTC-SUP-011 supply-chain
−2.1 Excessive ALL-CAPS emphasis in metadata ×3 MTC-INJ-CAPS injection

2. Client adoption risk — 96 − 8 = 88. 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
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−5 publisher verification (unlocatable) — no provenance and no public repository to inspect
inspection depth (source) — how much of the target the scan could see

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 4

low Excessive ALL-CAPS emphasis in metadataMTC-INJ-CAPS

A run of shouted words is a common way to give injected instructions false authority.

Evidence: Get all tracked military and naval vessels worldwide. Sources data from AIS feeds — note that many military vessels

Location: tool military_vessels · description

low Excessive ALL-CAPS emphasis in metadataMTC-INJ-CAPS

A run of shouted words is a common way to give injected instructions false authority.

Evidence: Find vessels heading to a destination port or area. Searches the AIS destination field, which is free-text set by t

Location: tool vessels_to · description

low Excessive ALL-CAPS emphasis in metadataMTC-INJ-CAPS

A run of shouted words is a common way to give injected instructions false authority.

Evidence: Get port details by UN/LOCODE. Returns port name, country, coordinates, type (seaport/river_port/offshore), and

Location: tool port_info · description

low Package has no source repositoryMTC-SUP-011

"voyageintel" declares no repository URL, so its published artifact cannot be compared against reviewable source.

Fix: Prefer packages that link to public, reviewable source.

Location: package voyageintel

What this scan could not see

Versions

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
v1.0.0 latest B 88/100 4 1.7.0 2026-07-23

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: B · 88/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/voyageintel/badge.svg)](https://mcptrustchecker.com/registry/voyageintel)
HTML
<a href="https://mcptrustchecker.com/registry/voyageintel"><img src="https://mcptrustchecker.com/registry/voyageintel/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/voyageintel/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 voyageintel --online --registry pypi

Use the free API → How scoring works

More in Learning & Documentation