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.

io.github.CloudCorpRecords/partshoal

NPM · @RENETURCIOS/PARTSHOAL · 2 COMPONENTS

Marine spare-parts catalogue: OEM brands, models and compatible part numbers, with quotes.

70 Trust /100

Last scanned (21 hours ago)

Scores higher than 41% of npm servers

Category E-commerce

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 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
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 470 tokens (~78/item across 6 items; 6 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 16 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Nov 26 55

    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 21 Nov 2026 · Analysed npm/@reneturcios/partshoal@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 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~470 tokens

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 →

Tool Tokens
get_manifest ~33

Site, contact details, endpoints, tools, limits and disclaimer for Dolphin Industrial Parts. Availability and price are quoted per application.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_brands ~37

List the OEM brands and equipment families for which Dolphin Industrial Parts quotes compatible parts, with model counts. Availability and price are quoted per application.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_catalog ~61

Page through catalog parts for one equipment family, 100 per page. Returns part numbers and descriptions with paging info. Availability and price are quoted per application.

NameTypeReqDescription
familystringyesEquipment family slug.
pageinteger–1-based page number.

No output schema declared.

No examples provided.

list_models ~62

List the equipment models and series quoted for one OEM brand (for example IMO, Moatti, Alfa Laval). Use list_brands for brand names. Availability and price are quoted per application.

NameTypeReqDescription
brandstringyesOEM brand name as returned by list_brands.

No output schema declared.

No examples provided.

lookup_part ~88

Look up a part number: exact match, then prefix match, then a format-based guess of brand and family (not a confirmed match). Returns matching parts, how to order and the quote form URL. Parts are compatible alternatives, not OEM parts. Availability and price are quoted per application.

NameTypeReqDescription
part_numberstringyesPart number, for example 223401-28 or P190123.

No output schema declared.

No examples provided.

request_quote ~189

Prepare a parts quote request (part numbers, quantities, equipment type, make, model, serial, country, notes). It never submits anything: it returns the cleaned request, the quote form URL and contact details so the customer can send it. Quotes are in USD within 1 business day. Availability and price are quoted per application.

NameTypeReqDescription
countrystring–Ship-to country.
descriptionstring–Part description.
equipment_typestring–For example Pump, Separator / Centrifuge, Fresh Water Generator.
makestring–Equipment make.
modelstring–Equipment model.
notesstring–Anything that helps identify the part.
part_numberstring–Single part number (use parts for several).
partsarray–Parts to quote.
quantityinteger–Quantity.
serialstring–Serial number.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/partshoal MCP server?

io.github.CloudCorpRecords/partshoal runs locally as an npm package, launched with npx -y @reneturcios/partshoal mcp. 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/partshoal

# add to Claude Code
claude mcp add cloudcorprecords-partshoal -- npx -y @reneturcios/partshoal mcp
Common questions

What is the io.github.CloudCorpRecords/partshoal MCP server?

io.github.CloudCorpRecords/partshoal is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/partshoal. Marine spare-parts catalogue: OEM brands, models and compatible part numbers, with quotes. This page covers its npm package (@reneturcios/partshoal).

Is the io.github.CloudCorpRecords/partshoal MCP server safe to use?

io.github.CloudCorpRecords/partshoal scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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/partshoal MCP server expose?

io.github.CloudCorpRecords/partshoal exposes 6 tools: lookup_part, list_brands, list_models, list_catalog, request_quote, get_manifest. Their descriptions and schemas cost roughly 470 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/partshoal MCP server still maintained?

io.github.CloudCorpRecords/partshoal is still listed as active in the MCP registry. We last reached this channel on 21 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/partshoal MCP server under?

io.github.CloudCorpRecords/partshoal declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.CloudCorpRecords/partshoal MCP server?

VerifyMCP ran 15 checks on io.github.CloudCorpRecords/partshoal, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/partshoal: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.