io.github.CloudCorpRecords/hullcheck
NPM · @RENETURCIOS/HULLCHECK · 2 COMPONENTS
Vessel screening by IMO: sanctions, ownership opacity and vetting grades, plus voyage risk scores.
Available components
Last scanned (4 hours ago)
Scores higher than 35% of npm servers
Category Security
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 475 tokens (~67/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: 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.
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.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 53
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@reneturcios/hullcheck@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_vessel ~45
Sanctions status, ownership-opacity score, and A–E vetting grade for one IMO. No API key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| imo | string | yes | The imo for this call. |
No output schema declared.
No examples provided.
find_port ~51
Resolve a port name or country to UN/LOCODEs. No API key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results to return (optional). |
| query | string | yes | Search query text. |
No output schema declared.
No examples provided.
get_screening ~31
Retrieve a stored screening record by id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Identifier of the record to operate on. |
No output schema declared.
No examples provided.
get_usage ~18
Remaining allowance and limits for the configured API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
score_voyage ~187
Route risk between two UN/LOCODEs: score, level, drivers, confidence, missing sources.
| Name | Type | Req | Description |
|---|---|---|---|
| bunker_price_usd_per_tonne | number | – | The bunker price usd per tonne for this call. |
| customer_reference | string | – | The customer reference for this call. |
| destination_locode | string | yes | The destination locode for this call. |
| dwt_tonnes | number | – | The dwt tonnes for this call. |
| fuel_type | string | – | The fuel type for this call. |
| include_geometry | boolean | – | The include geometry for this call. |
| load_condition | string | – | The load condition for this call. |
| origin_locode | string | yes | The origin locode for this call. |
| speed_knots | number | – | The speed knots for this call. |
| vessel_type | string | – | The vessel type for this call. |
No output schema declared.
No examples provided.
screen_vessel ~89
The full screening record for one IMO: every sanctions match with source and confidence, graded vetting factors, record id.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_reference | string | – | The customer reference for this call. |
| imo | string | yes | The imo for this call. |
| include_vetting | boolean | – | The include vetting for this call. |
| vessel_name | string | – | The vessel name for this call. |
No output schema declared.
No examples provided.
screen_vessels ~54
Batch-screen up to 50 IMOs and wait for the results.
| Name | Type | Req | Description |
|---|---|---|---|
| imos | array | yes | The imos for this call. |
| include_vetting | boolean | – | The include vetting for this call. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/hullcheck MCP server?
io.github.CloudCorpRecords/hullcheck runs locally as an npm package, launched with npx -y @reneturcios/hullcheck. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/hullcheck
claude mcp add cloudcorprecords-hullcheck -- npx -y @reneturcios/hullcheck
What is the io.github.CloudCorpRecords/hullcheck MCP server?
io.github.CloudCorpRecords/hullcheck is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/hullcheck. Vessel screening by IMO: sanctions, ownership opacity and vetting grades, plus voyage risk scores. This page covers its npm package (@reneturcios/hullcheck).
Is the io.github.CloudCorpRecords/hullcheck MCP server safe to use?
io.github.CloudCorpRecords/hullcheck scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.CloudCorpRecords/hullcheck MCP server expose?
io.github.CloudCorpRecords/hullcheck exposes 7 tools: check_vessel, find_port, screen_vessel, screen_vessels, get_screening, and 2 more. Their descriptions and schemas cost roughly 475 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/hullcheck MCP server still maintained?
io.github.CloudCorpRecords/hullcheck is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.CloudCorpRecords/hullcheck MCP server under?
io.github.CloudCorpRecords/hullcheck declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.