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.

Pirate Ship by Cotlet

PYPI · PIRATE-SHIP-API-MCP · 3 COMPONENTS

Labels, rates and tracking for small shippers.

+15 this week 78 Trust /100

Last scanned (5 hours ago)

Scores higher than 77% of PyPI 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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 36 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency84
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to cotletdev/pirate-ship-api-mcp-server). View diagnostics → Pass
  • License check failed: the license (PolyForm-Noncommercial-1.0.0) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 8 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 6589 tokens (~124/item across 53 items; 51 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 60% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 53 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.

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.

  • 5 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 29 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 25 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 24 Oct 26 63

    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 5 Nov 2026 · Analysed pypi/pirate-ship-api-mcp@1.0.3

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo cotletdev/pirate-ship-api-mcp-server
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/cotletdev/pirate-ship-api-mcp-server/.github/workflows/publish.yml@refs/tags/v1.0.3
Rekor log index 3440922953
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:04623b98f9f1bbf4c94bb9323326a70676ddee4b6487890051f024d82d9013b4

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 36 packages
Packages resolved 36
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 51 exposed · ~6,473 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
update_tracking_email_settings ~81

Turns default tracking emails on or off and sets their delay after purchase. Changes only what you pass and returns the settings as get_tracking_email_settings does.

NameTypeReqDescription
delaystring–When the email goes out after purchase; +24 hours is next day 9:00 AM.
enabledboolean–Send tracking emails on new labels by default.

No output schema declared.

No examples provided.

Install

How do I install the Pirate Ship by Cotlet MCP server?

Pirate Ship by Cotlet runs locally as a PyPI package, launched with uvx pirate-ship-api-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · pirate-ship-api-mcp

# add to Claude Code
claude mcp add dev-cotlet-pirate-ship -- uvx pirate-ship-api-mcp
Common questions

What is the Pirate Ship by Cotlet MCP server?

Pirate Ship by Cotlet is an MCP server listed in the public MCP registry as dev.cotlet/pirate-ship. Labels, rates and tracking for small shippers. This page covers its PyPI package (pirate-ship-api-mcp).

Is the Pirate Ship by Cotlet MCP server safe to use?

Pirate Ship by Cotlet scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 Pirate Ship by Cotlet MCP server expose?

Pirate Ship by Cotlet exposes 51 tools: change_ship_date, create_batch, create_batch_from_orders, create_email_template, create_saved_package, and 46 more. Their descriptions and schemas cost roughly 6,473 tokens of context every time the server is loaded.

Is the Pirate Ship by Cotlet MCP server still maintained?

Pirate Ship by Cotlet 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 Pirate Ship by Cotlet MCP server under?

Pirate Ship by Cotlet declares the PolyForm-Noncommercial-1.0.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.