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/canadapost-mcp

NPM · CANADAPOST-MCP

MCP server for Canada Post: rate quotes, ship MCP: real tools for real work.

Available components

0 this week 65 Trust /100

Last scanned (15 hours ago)

Scores higher than 37% 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 Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 872 tokens (~87/item across 10 items; 10 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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.

  • 8 Nov 26 65

    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/canadapost-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 · 10 exposed · ~872 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
create_shipment ~289

Create a non-contract Canada Post shipment and return its shipment id and tracking pin.

NameTypeReqDescription
destination_citystringyesRecipient city
destination_companystring–Recipient company
destination_line1stringyesRecipient street address
destination_namestringyesRecipient name
destination_phonestring–Recipient phone
destination_postal_codestringyesRecipient postal code, e.g. H2Y1C6
destination_provincestringyesRecipient province code, e.g. QC
height_cmnumber–Height in cm
length_cmnumber–Length in cm
referencestring–Your own customer reference
sender_citystringyesSender city
sender_companystring–Sender company
sender_line1stringyesSender street address
sender_namestringyesSender name
sender_phonestring–Sender phone
sender_postal_codestringyesSender postal code, e.g. K1A0B1
sender_provincestringyesSender province code, e.g. ON
service_codestringyesCanada Post service code, e.g. DOM.EP (Expedited Parcel)
weight_kgnumberyesParcel weight in kilograms
width_cmnumber–Width in cm

No output schema declared.

No examples provided.

find_post_offices ~56

Find Canada Post offices near a Canadian postal code.

NameTypeReqDescription
max_resultsinteger–How many offices to return
postal_codestringyesPostal code to search around, e.g. M5V2T6

No output schema declared.

No examples provided.

get_label ~58

Fetch a shipping artifact for a shipment. Returns the PDF size and content type; the file itself is not inlined.

NameTypeReqDescription
artifact_typestring–Artifact to request
shipment_idstringyesShipment id returned by create_shipment

No output schema declared.

No examples provided.

get_manifest ~51

Get the manifest (end-of-day pickup summary) for a date range.

NameTypeReqDescription
end_datestringyesEnd date as YYYYMMDD
start_datestringyesStart date as YYYYMMDD

No output schema declared.

No examples provided.

get_pickup ~32

Get the status of a booked pickup.

NameTypeReqDescription
pickup_idstringyesPickup id returned by request_pickup

No output schema declared.

No examples provided.

get_rates ~114

Get Canada Post shipping rates between two Canadian postal codes for a parcel.

NameTypeReqDescription
destination_postal_codestringyesDestination postal code, e.g. H2Y1C6
height_cmnumber–Height in cm
length_cmnumber–Length in cm
origin_postal_codestringyesOrigin postal code, e.g. K1A0B1
weight_kgnumberyesParcel weight in kilograms
width_cmnumber–Width in cm

No output schema declared.

No examples provided.

get_shipment ~34

Get the current state of a shipment you created.

NameTypeReqDescription
shipment_idstringyesShipment id returned by create_shipment

No output schema declared.

No examples provided.

get_shipment_details ~39

Get full delivery details for a shipment, including links to its artifacts.

NameTypeReqDescription
shipment_idstringyesShipment id returned by create_shipment

No output schema declared.

No examples provided.

request_pickup ~158

Book a Canada Post pickup at a business address.

NameTypeReqDescription
citystringyesCity
close_timestringyesLatest close time as HH:MM
companystring–Company name if different
instructionsstring–Special instructions for the courier
line1stringyesStreet address
namestringyesBusiness name
phonestringyesContact phone
pickup_datestringyesPickup date as YYYY-MM-DD
pickup_typestringyesPickup service level
postal_codestringyesPostal code
provincestringyesProvince code, e.g. ON
ready_timestringyesEarliest ready time as HH:MM

No output schema declared.

No examples provided.

track_package ~41

Track a Canada Post parcel by its 16-character tracking PIN.

NameTypeReqDescription
pinstringyesTracking PIN, e.g. 1234567890123456

No output schema declared.

No examples provided.

Install

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

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

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

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

io.github.mrfentmen/canadapost-mcp is listed in the public MCP registry as io.github.mrfentmen/canadapost-mcp. MCP server for Canada Post: rate quotes, ship MCP: real tools for real work. This page covers its npm package (canadapost-mcp).

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

io.github.mrfentmen/canadapost-mcp scores 65 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/canadapost-mcp server expose?

io.github.mrfentmen/canadapost-mcp exposes 10 tools: get_rates, track_package, find_post_offices, create_shipment, get_shipment, and 5 more. Their descriptions and schemas cost roughly 872 tokens of context every time the server is loaded.

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

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

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

VerifyMCP ran 15 checks on io.github.mrfentmen/canadapost-mcp, 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.mrfentmen/canadapost-mcp: 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.