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.mrfentmen/shipengine-mcp

NPM · SHIPENGINE-MCP

MCP server for ShipEngine: carriers, rate quo MCP: real tools for real work.

Available components

+3 this week 70 Trust /100

Last scanned (17 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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 932 tokens (~42/item across 22 items; 22 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 22 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
What we tested

Checks we ran (16)

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

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.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 64

    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/shipengine-mcp@1.0.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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 22 exposed · ~932 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
cancel_shipment ~42

Cancel a shipment that has not been labelled yet. This is destructive: the shipment cannot be restored afterwards.

NameTypeReqDescription
shipment_idstringyesShipEngine shipment id

No output schema declared.

No examples provided.

create_label ~52

Purchase a label. This spends real money on the connected carrier account.

NameTypeReqDescription
labelobjectyesShipEngine label body: shipment, or shipment_id/rate_id plus label_format, label_layout and label_download_type

No output schema declared.

No examples provided.

create_shipment ~60

Create a shipment record from a carrier, service, addresses, packages and optional label options.

NameTypeReqDescription
shipmentobjectyesShipEngine shipment body: carrier_id, service_code, ship_to, ship_from, packages[] as defined by their OpenAPI spec

No output schema declared.

No examples provided.

estimate_rates ~51

Estimate rates without creating a shipment, from carrier, service, addresses and package weight.

NameTypeReqDescription
requestobjectyesShipEngine estimate body: carrier_ids, from_*, to_*, weight, dimensions where known

No output schema declared.

No examples provided.

get_batch ~33

Get one label batch by its batch id, including processing errors.

NameTypeReqDescription
batch_idstringyesShipEngine batch id

No output schema declared.

No examples provided.

get_carrier ~40

Get one carrier account by its ShipEngine carrier id.

NameTypeReqDescription
carrier_idstringyesShipEngine carrier id, e.g. se-123456

No output schema declared.

No examples provided.

get_rate ~35

Look up a single quoted rate by its rate id.

NameTypeReqDescription
rate_idstringyesRate id from get_rates or estimate_rates

No output schema declared.

No examples provided.

get_rates ~46

Quote live shipping rates for a shipment across the connected carriers.

NameTypeReqDescription
shipmentobjectyesShipEngine rate request body: shipment_id, or ship_to/ship_from/packages/weight details

No output schema declared.

No examples provided.

get_shipment ~31

Get one shipment by its ShipEngine shipment id.

NameTypeReqDescription
shipment_idstringyesShipEngine shipment id

No output schema declared.

No examples provided.

get_shipment_rates ~32

List the rates already quoted for an existing shipment.

NameTypeReqDescription
shipment_idstringyesShipEngine shipment id

No output schema declared.

No examples provided.

list_batches ~44

List label batches in the account.

NameTypeReqDescription
pageinteger–Page number, starting at 1
page_sizeinteger–Results per page (max 100)

No output schema declared.

No examples provided.

list_carrier_packages ~31

List the package types a carrier account accepts.

NameTypeReqDescription
carrier_idstringyesShipEngine carrier id

No output schema declared.

No examples provided.

list_carrier_services ~38

List the shipping services a carrier account offers (ground, express, international...).

NameTypeReqDescription
carrier_idstringyesShipEngine carrier id

No output schema declared.

No examples provided.

list_carriers ~26

List the carrier accounts connected to this ShipEngine account, with balance and account number.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_labels ~44

List purchased labels in the account.

NameTypeReqDescription
pageinteger–Page number, starting at 1
page_sizeinteger–Results per page (max 100)

No output schema declared.

No examples provided.

list_shipments ~47

List shipments in the account, newest first.

NameTypeReqDescription
pageinteger–Page number, starting at 1
page_sizeinteger–Results per page (max 100)

No output schema declared.

No examples provided.

list_warehouses ~23

List the warehouses (ship-from locations) configured in the account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

recognize_address ~52

Parse a free-form address string into structured address fields.

NameTypeReqDescription
addressobjectyesShipEngine recognize request body, e.g. { text: '525 S Winchester Blvd, San Jose, CA 95128' }

No output schema declared.

No examples provided.

track_label ~31

Get tracking status and event history for a purchased label.

NameTypeReqDescription
label_idstringyesShipEngine label id

No output schema declared.

No examples provided.

track_package ~64

Track any package by carrier code and tracking number, without needing a ShipEngine label.

NameTypeReqDescription
carrier_codestringyesShipEngine carrier code, e.g. ups, fedex, usps, dhl_express
tracking_numberstringyesCarrier tracking number

No output schema declared.

No examples provided.

validate_address ~64

Validate one or more US/international addresses and get ShipEngine's normalized version plus status messages.

NameTypeReqDescription
addressesarrayyesArray of ShipEngine address objects, e.g. [{ name, address_line1, city_locality, state_province, postal_code, country_code }]

No output schema declared.

No examples provided.

void_label ~46

Void a purchased label so it cannot be used. This is destructive and may be refused by the carrier after the void window closes.

NameTypeReqDescription
label_idstringyesShipEngine label id

No output schema declared.

No examples provided.

Install

How do I install the io.github.mrfentmen/shipengine-mcp server?

io.github.mrfentmen/shipengine-mcp runs locally as an npm package, launched with npx -y shipengine-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 · shipengine-mcp

# add to Claude Code
claude mcp add mrfentmen-shipengine-mcp -- npx -y shipengine-mcp
Common questions

What is the io.github.mrfentmen/shipengine-mcp server?

io.github.mrfentmen/shipengine-mcp is listed in the public MCP registry as io.github.mrfentmen/shipengine-mcp. MCP server for ShipEngine: carriers, rate quo MCP: real tools for real work. This page covers its npm package (shipengine-mcp).

Is the io.github.mrfentmen/shipengine-mcp server safe to use?

io.github.mrfentmen/shipengine-mcp scores 70 out of 100 on VerifyMCP. We recorded 1 known advisory against 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.mrfentmen/shipengine-mcp server expose?

io.github.mrfentmen/shipengine-mcp exposes 22 tools: list_carriers, get_carrier, list_carrier_services, list_carrier_packages, validate_address, and 17 more. Their descriptions and schemas cost roughly 932 tokens of context every time the server is loaded.

Is the io.github.mrfentmen/shipengine-mcp server still maintained?

io.github.mrfentmen/shipengine-mcp 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.mrfentmen/shipengine-mcp server under?

io.github.mrfentmen/shipengine-mcp 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.mrfentmen/shipengine-mcp server?

VerifyMCP ran 16 checks on io.github.mrfentmen/shipengine-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.