Easyship
PYPI · EASYSHIP-MCP · 2 COMPONENTS
Connect Easyship to compare rates, create shipments, buy labels, and track packages globally.
Available components
Last scanned (1 day ago)
Scores higher than 82% of PyPI servers
Category E-commerce
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
- 1 of 21 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 6 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 9485 tokens (~379/item across 25 items; 25 tools + 0 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 43% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 26 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
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.
- 3 Nov 26 +15
- Provenance: unverified → fail ▼ security
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 0
- Provenance: fail → unverified ▼ security
- Package version: 0.6.2 → 0.6.7 functional
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 0
- Package version: 0.6.6 → 0.6.7 functional
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 0
- Package version: 0.6.2 → 0.6.6 functional
- 24 Oct 26 −1
- Stability: pass → 0.93 functional
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 4 Nov 2026 · Analysed pypi/easyship-mcp@0.6.7
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
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 21 packages
| Packages resolved | 21 |
|---|---|
| Stale | 1 |
| 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 →
analytics_couriers_by_volume Analytics Couriers By Volume (analytics_couriers_by_volume) ~208
Retrieves the couriers the account has shipped with, ordered by shipment volume. Returns `total_shipments_count` and `couriers` array (each with `name`, `shipments_count`, `percentage`). Use for: "Which courier do I use most?", "Show courier breakdown", courier usage analysis. **Date range:** Both dates are required; a common window is the 90 days ending today. Required authorization scope: `public.analytics:read` Args: from_date: Start date in YYYY-MM-DD format. to_date: End date in YYYY-MM-DD format. Returns: Couriers with shipment counts and percentage of total volume, ordered by volume.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | yes | Start of date range in YYYY-MM-DD format, e.g. '2024-01-01'. |
| to_date | string | yes | End of date range in YYYY-MM-DD format, e.g. '2024-12-31'. |
Structured output declared, but exposes no named fields.
No examples provided.
analytics_destinations_by_volume Analytics Destinations By Volume (analytics_destinations_by_volume) ~212
Retrieves the account's shipping destinations ordered by shipment volume. Use for any question about where shipments are going or which destination countries are most common. Returns `total_shipments_count`, `shipments_count_by_zone` (zone name + count), and `shipments_count_by_country` (country name, alpha2 code, count, percentage). **Date range:** Both dates are required; a common window is the 90 days ending today. Required authorization scope: `public.analytics:read` Args: from_date: Start date in YYYY-MM-DD format. to_date: End date in YYYY-MM-DD format. Returns: Shipping destinations with shipment counts by zone and by country, ordered by volume.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | yes | Start of date range in YYYY-MM-DD format, e.g. '2024-01-01'. |
| to_date | string | yes | End of date range in YYYY-MM-DD format, e.g. '2024-12-31'. |
Structured output declared, but exposes no named fields.
No examples provided.
analytics_sale_channels Analytics Sale Channels (analytics_sale_channels) ~202
Retrieve shipment volume by sales channel (e.g. Shopify, WooCommerce, API, manual). Returns `total_shipments_count` and `channels` array (each with `name`, `shipments_count`, `percentage`). Use for: "Which sales channel has the most shipments?", "Show me channel breakdown." **Date range:** Both dates are required; a common window is the 90 days ending today. Required authorization scope: `public.analytics:read` Args: from_date: Start date in YYYY-MM-DD format. to_date: End date in YYYY-MM-DD format. Returns: Sales channels with shipment counts and percentage of total volume.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | yes | Start of date range in YYYY-MM-DD format, e.g. '2024-01-01'. |
| to_date | string | yes | End of date range in YYYY-MM-DD format, e.g. '2024-12-31'. |
Structured output declared, but exposes no named fields.
No examples provided.
analytics_shipment_status Analytics Shipment Status (analytics_shipment_status) ~217
Retrieve shipment status distribution: how many shipments are in each status. Returns `in_progress_shipments_count`, `completed_shipments_count`, and `in_progress_shipments` array (each with `status` and `count`). Possible statuses: Label Pending, Label Rejected, Label Ready, Pickup/Drop-off in Progress, In Transit to Customer, Failed Delivery Attempt, Exception. **Date range:** Both dates are required; a common window is the 90 days ending today. Required authorization scope: `public.analytics:read` Args: from_date: Start date in YYYY-MM-DD format. to_date: End date in YYYY-MM-DD format. Returns: Shipment counts by status (in-progress breakdown + completed total).
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | yes | Start of date range in YYYY-MM-DD format, e.g. '2024-01-01'. |
| to_date | string | yes | End of date range in YYYY-MM-DD format, e.g. '2024-12-31'. |
Structured output declared, but exposes no named fields.
No examples provided.
analytics_shipments Analytics Shipments (analytics_shipments) ~217
Retrieve shipment volume overview: total shipment count and daily shipment counts over time. Returns `total_shipments_count` and `shipments_count_by_date` (a time series with daily totals and a `max` peak value). Covers total shipment counts for a period and daily volume trends. It does not break volume down by destination, status, courier, or sales channel. **Date range:** Both dates are required; a common window is the 90 days ending today. Required authorization scope: `public.analytics:read` Args: from_date: Start date in YYYY-MM-DD format. to_date: End date in YYYY-MM-DD format. Returns: Total shipment count and daily shipment count time series for the date range.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | yes | Start of date range in YYYY-MM-DD format, e.g. '2024-01-01'. |
| to_date | string | yes | End of date range in YYYY-MM-DD format, e.g. '2024-12-31'. |
Structured output declared, but exposes no named fields.
No examples provided.
analytics_shipped Analytics Shipped (analytics_shipped) ~213
Retrieves data for shipments that have already been shipped (labels generated) within a date range. Returns `has_ever_shipped` (boolean) and `currency` info: whether the account has shipped anything (e.g. "Have I ever shipped anything?", "Did I ship anything last month?"). It does not return counts or individual shipments. **Date range:** Both dates are required; a common window is the 90 days ending today. Required authorization scope: `public.analytics:read` Args: from_date: Start date in YYYY-MM-DD format. to_date: End date in YYYY-MM-DD format. Returns: Shipped shipment data including whether the account has ever shipped and currency info.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | yes | Start of date range in YYYY-MM-DD format, e.g. '2024-01-01'. |
| to_date | string | yes | End of date range in YYYY-MM-DD format, e.g. '2024-12-31'. |
Structured output declared, but exposes no named fields.
No examples provided.
cancel_pickup Cancel Pickup (cancel_pickup) ~71
Cancel a pickup. Required authorization scope: `public.pickup:write` Args: easyship_pickup_id: The Easyship pickup ID. Returns: Confirmation of the cancelled pickup, or an error.
| Name | Type | Req | Description |
|---|---|---|---|
| easyship_pickup_id | string | yes | The Easyship pickup ID. |
Structured output declared, but exposes no named fields.
No examples provided.
cancel_shipment Cancel Shipment (cancel_shipment) ~132
Cancel a shipment that has been shipped. Required authorization scope: `public.shipment:write` > You can cancel your shipment after it has been shipped only if its label failed to be generated or if the label is already generated, but the shipment is not yet in transit. Args: easyship_shipment_id: The Easyship shipment ID, e.g. "ESSG10006001". Returns: Confirmation of the cancelled shipment, or an error.
| Name | Type | Req | Description |
|---|---|---|---|
| easyship_shipment_id | string | yes | The Easyship shipment ID, e.g. 'ESSG10006001'. |
Structured output declared, but exposes no named fields.
No examples provided.
create_label Create Label (create_label) ~514
Create a label for an existing shipment and retrieve it synchronously. Buys a label for a shipment that already exists. This is a dedicated endpoint that finalizes the shipment, books it with the courier, and returns the label and shipping documents in one synchronous call. `update_shipment` with `buy_label` performs the same purchase as part of a wider update. Required authorization scope: `public.label:write` **Typical use:** Buying or regenerating a label for an existing shipment ID where `label_state` is `not_created` or similar. Successful responses include `shipping_documents` with `category` values such as `label`, `packing_slip`, and `commercial_invoice`; with `format` `url`, entries include `url` fields. If the response includes `support_reply_hint`, `support_email`, or `support_email_link`, the API is noting verification limits on labels—those fields contain Easyship-provided support guidance. Args: easyship_shipment_id: The Easyship shipment ID, e.g. "ESUS323672208". courier_service_id: UUID of the courier service to use. Omit to keep the shipment's current courier or let Easyship select a courier automatically. format: Document format. One of: "url", "pdf", "png", "zpl". Default "url" (returns clickable links). label: Label page size. One of: "4x6", "A4", "A5". Default "4x6". commercial_invoice: Commercial invoice page size. One of: "4x6", "A4". Default "A4". packing_slip: Packing slip page size. One of: "4x6", "A4", "none". Default "4x6". remarks: Custom commercial invoice remarks (max 70 chars). Overrides company-level remarks. Returns: The full shipment object with `shipping_documents` containing label/invoice/packing slip URLs. If identity verification affects label purchase, the payload may include `support_email`, `support_email_link`, and `support_reply_hint`.
| Name | Type | Req | Description |
|---|---|---|---|
| commercial_invoice | string | – | – |
| courier_service_id | – | – | – |
| easyship_shipment_id | string | yes | The Easyship shipment ID, e.g. 'ESSG10006001'. |
| format | string | – | – |
| label | string | – | – |
| packing_slip | string | – | – |
| remarks | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
create_pickup Create Pickup (create_pickup) ~408
Schedule a courier pickup for one or more shipments. **Requirements:** - All shipments use the **same courier** and have labels that are pending or generated. - `courier_service_id` is that courier's `courier_service.id` on the shipments. - Either `time_slot_id` (from `get_pickup_slots`) or both `selected_from_time` and `selected_to_time`. Books a real courier collection. Required authorization scope: `public.pickup:write` Args: courier_service_id: UUID of the shipments' courier service (`courier_service.id` on the shipment). selected_date: Pickup date in YYYY-MM-DD format. easyship_shipment_ids: List of Easyship shipment IDs to include, e.g. ["ESSG10006001", "ESSG10006002"]. All must use the same courier. time_slot_id: UUID of a time slot from `get_pickup_slots`. Provide this OR `selected_from_time`/`selected_to_time`. selected_from_time: Pickup window start time (e.g. "09:00"). Required if `time_slot_id` is not provided. selected_to_time: Pickup window end time (e.g. "17:00"). Required if `time_slot_id` is not provided. Returns: The created pickup object with confirmation details, or an error.
| Name | Type | Req | Description |
|---|---|---|---|
| courier_service_id | string | yes | UUID of the shipments' courier service: `courier_service.id` in the `get_shipment` or `list_shipments` response. |
| easyship_shipment_ids | array | yes | List of Easyship shipment IDs to include in this pickup, e.g. ['ESSG10006001']. |
| selected_date | string | yes | Requested pickup date in YYYY-MM-DD format, e.g. '2024-03-15'. |
| selected_from_time | – | – | – |
| selected_to_time | – | – | – |
| time_slot_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
create_shipment Create Shipment (create_shipment) ~1,698
Create a new shipment and optionally buy a label in one call. Required authorization scope: `public.shipment:write` (and `public.label:write` if buying a label). **Required address details:** contact names, emails, and phones for both addresses, plus company name for the origin. **Parcel line items:** Every object in `parcels[].items[]` needs at least one of `category` (Easyship product category slug) or `hs_code`. The Easyship API rejects the request if both are missing on any item. `category` / `hs_code` describe the actual goods; the API does not infer them. ## Buying a label vs creating a draft - **Label purchase:** `buy_label: true` and `buy_label_synchronous: true` in `shipping_settings` buy the label in the same call. With `format: "url"` in `printing_options`, the response includes HTTPS URLs under `shipping_documents`. This charges the account. - **Draft only:** with `buy_label` omitted or `false`, the shipment is created in draft state and the label can be bought later. ## Courier selection - **Automatic:** with `courier_settings.courier_service_id` omitted, the API selects a courier. - **Specific courier:** a `courier_service_id` (as returned by `get_rates`) in `courier_settings.courier_service_id`, with `allow_fallback: false`, buys with exactly that courier service. ## Reading the label from the response When `buy_label: true` and `buy_label_synchronous: true`, the response includes a `shipping_documents` array. Entries use `category` (e.g. `label`, `packing_slip`, `commercial_invoice`) and, when `format` is `url`, an `url` field. Example: ```json "shipping_documents": [ { "category": "label", "format": "url", "url": "https://...", "page_size": "4x6" }, { "category": "packing_slip", "format": "url", "url": "https://...", "page_size": "4x6" }, { "category": "commercial_invoice", ... } ] ``` ## Identity / KYC and labels If the response includes `support_email`, `support_email_link`, or `support_reply_hint`, the payload is noting account…
| Name | Type | Req | Description |
|---|---|---|---|
| shipment_data | object | yes | Full payload for creating a shipment. Required top-level fields: - destination_address, origin_address, parcels destination_address — required sub-fields: contact_name, contact_email, contact_p… |
Structured output declared, but exposes no named fields.
No examples provided.
delete_shipment Delete Shipment (delete_shipment) ~97
Delete a shipment that has not yet been shipped. Required authorization scope: `public.shipment:write` Args: easyship_shipment_id: The Easyship shipment ID, e.g. "ESSG10006001". Returns: Confirmation of the deleted shipment, or an error.
| Name | Type | Req | Description |
|---|---|---|---|
| easyship_shipment_id | string | yes | The Easyship shipment ID, e.g. 'ESSG10006001'. |
Structured output declared, but exposes no named fields.
No examples provided.
get_pickup Get Pickup (get_pickup) ~180
Retrieve details of a specific pickup. Required authorization scope: `public.pickup:write` (note: the API requires write scope even for this read operation). Args: easyship_pickup_id: The Easyship pickup ID. include_contact_details: Set to true only when the user explicitly asked for the recipient's contact email or phone. Defaults to false, which omits them. Returns: Full pickup details, or an error.
| Name | Type | Req | Description |
|---|---|---|---|
| easyship_pickup_id | string | yes | The Easyship pickup ID. |
| include_contact_details | boolean | – | Include the recipient's contact email and phone in the response. Defaults to false, which withholds them. Set to true only when the user explicitly asked for contact details; leave it false for routi… |
Structured output declared, but exposes no named fields.
No examples provided.
get_pickup_slots Get Pickup Slots (get_pickup_slots) ~186
Retrieve available pickup time slots for a courier. Returns the dates and time windows a courier can collect from the origin address. Each window's `time_slot_id` is accepted by `create_pickup`. Required authorization scope: `public.pickup:read` Args: courier_service_id: UUID of the shipment's courier service (`courier_service.id` on the shipment). origin_address_id: Origin address ID to check pickup availability for. Optional — defaults to the account's primary address. Returns: Available pickup slots grouped by date, each with time windows containing `time_slot_id`, `from_time`, and `to_time`.
| Name | Type | Req | Description |
|---|---|---|---|
| courier_service_id | string | yes | UUID of the shipment's courier service: `courier_service.id` in the `get_shipment` or `list_shipments` response. |
| origin_address_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_rates Get Rates (get_rates) ~691
Get available shipping rates (courier options with prices and delivery times) for a parcel. Returns the courier options available for a parcel between two countries, each with its price, estimated delivery time, and ranking fields the caller can sort by. **Required inputs:** origin country, destination country, weight, and box dimensions. **Accuracy:** Rates are only as accurate as the weight and dimensions supplied. They are estimates when based on generic postal codes or standard box dimensions. Exact rates can change with a full address and precise box measurements. Each item should include either `item_category` or `item_hs_code` for accurate customs and duty estimates.
| Name | Type | Req | Description |
|---|---|---|---|
| destination_city | – | – | Destination city. Recommended for US, CA, MX, AU. |
| destination_country_alpha2 | string | yes | ISO 3166-1 alpha-2 destination country code, e.g. 'SG', 'DE', 'JP'. |
| destination_line_1 | – | – | Destination street address line 1. Some couriers need this for accurate rates. |
| destination_postal_code | – | – | Destination postal code. Required for most countries. |
| destination_state | – | – | Destination state/province. Use 2-letter abbreviation for US/CA. |
| height | number | yes | Box height in cm, e.g. 15. |
| incoterms | – | – | "DDU" (buyer pays duties on delivery) or "DDP" (seller pre-pays duties). Optional. |
| item_category | – | – | Easyship product category slug (e.g. "fashion", "mobile_phones", "documents"). Provide this or `item_hs_code` for accurate duty estimates. The full category list is managed by the Easyship catalog an… |
| item_declared_currency | string | – | ISO-4217 currency code for customs value. Example: "USD", "EUR", "GBP". |
| item_declared_customs_value | number | – | Declared customs value per item in the currency specified. Must be > 0 unless category is "documents". Example: 25.0 |
| item_description | string | – | Short description of what is being shipped. Example: "Cotton T-Shirts" |
| item_hs_code | – | – | Harmonized System code for the item. Provide this or `item_category` for accurate duty estimates. |
| item_quantity | integer | – | Number of items in the parcel. Default 1. |
| length | number | yes | Box length in cm, e.g. 30. |
| origin_city | – | – | Origin city. Recommended for US, CA, MX, AU for accurate rates. |
| origin_country_alpha2 | string | yes | ISO 3166-1 alpha-2 origin country code, e.g. 'US', 'HK', 'GB'. |
| origin_line_1 | – | – | Origin street address line 1. Use "General Delivery" if unknown. |
| origin_postal_code | – | – | Origin postal code. Required for most countries. |
| origin_state | – | – | Origin state/province. Use 2-letter abbreviation for US/CA. |
| output_currency | – | – | ISO-4217 currency for returned prices (e.g. "USD"). Defaults to origin country currency. |
| total_actual_weight | number | yes | Total weight of the parcel in kg including packaging, e.g. 1.5. |
| width | number | yes | Box width in cm, e.g. 20. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_shipment Get Shipment (get_shipment) ~549
Fetch a single shipment by Easyship ID, including parcel data and, on request, its documents. Returns the shipment's state, dates, courier, addresses, and parcel contents. Documents are **not** included by default — set `include_documents: true` when the user asked for the label, commercial invoice, or packing slip. The remaining parameters below only shape those documents and have no effect unless `include_documents` is set. Required authorization scope: `public.shipment:read` > All shipment documents are customisable. You can set: > > - Document format: URL, PDF or PNG > - Label page size: A4, A5 or 4x6 > - Commercial invoice page size: A4 or 4x6 > - Packing slip page size: A4 or 4x6 Args: easyship_shipment_id: The Easyship shipment ID, e.g. "ESSG10006001". label: Label page size: A4, A5, or 4x6. format: Document format: URL, PDF, or PNG. packing_slip: Packing slip page size: none, A4, or 4x6. commercial_invoice: Commercial invoice page size: A4 or 4x6. include_contact_details: Set to true only when the user explicitly asked for the recipient's contact email or phone. Defaults to false, which omits them. include_documents: Set to true only when the user asked for a label or document. Defaults to false, which omits the download links. Returns: Shipment details, including `shipping_documents` when `include_documents` is true.
| Name | Type | Req | Description |
|---|---|---|---|
| commercial_invoice | – | – | – |
| easyship_shipment_id | string | yes | The Easyship shipment ID, e.g. 'ESSG10006001'. |
| format | – | – | – |
| include_contact_details | boolean | – | Include the recipient's contact email and phone in the response. Defaults to false, which withholds them. Set to true only when the user explicitly asked for contact details; leave it false for routi… |
| include_documents | boolean | – | Include download links for the shipment's label and customs documents. Defaults to false. Set to true only when the user asked for a label, invoice, packing slip, or other document — these links are… |
| label | – | – | – |
| packing_slip | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_shipment_documents Get Shipment Documents (get_shipment_documents) ~189
Request a commercial invoice document for a shipment from the API. The MCP transport cannot return raw PDF bytes; the implementation responds with content-type and size metadata only. Downloadable HTTPS URLs for documents are available via `get_shipment` when document `format` is `url`. Required authorization scope: `public.shipment_document:read` Args: easyship_shipment_id: The Easyship shipment ID, e.g. "ESSG10006001". page_size: Page size for the document: "4x6" or "A4". Default: "A4". Returns: Metadata only (content type and size). For downloadable URLs, use `get_shipment` with format="URL".
| Name | Type | Req | Description |
|---|---|---|---|
| easyship_shipment_id | string | yes | The Easyship shipment ID, e.g. 'ESSG10006001'. |
| page_size | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_billing_transactions List Billing Transactions (list_billing_transactions) ~189
Retrieve a list of all billing document's transactions. Pagination of this endpoint is not indexed. `count` on the response body will always be `null`. Required authorization scope: `public.transaction_record:read` Args: billing_document_id: The billing document ID. page: Page number to fetch, minimum: 1. to_date: Filter transactions before this date in YYYY-MM-DD format. per_page: Number of records per page to fetch, minimum: 1, maximum: 100. from_date: Filter transactions since this date in YYYY-MM-DD format. Returns: A paginated list of transaction objects for the specified billing document.
| Name | Type | Req | Description |
|---|---|---|---|
| billing_document_id | string | yes | The billing document ID to list line items for. |
| from_date | – | – | – |
| page | – | – | – |
| per_page | – | – | – |
| to_date | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_pickup_shipments List Pickup Shipments (list_pickup_shipments) ~767
Retrieve a list of pickup's shipments. Required authorization scope: `public.shipment:read` Args: pickup_id: The pickup ID to retrieve shipments for. page: Page number to fetch, minimum: 1. per_page: Number of records per page to fetch, minimum: 1, maximum: 100. return_shipment: Search by whether the shipment is a return shipment or not. label_state: Filter by label status (e.g. "pending", "generated", "failed"). Pass values exactly as returned by the API; the set may change as the platform evolves. pickup_state: Filter by pickup status (e.g. "requested", "completed", "cancelled"). Pass values exactly as returned by the API; the set may change as the platform evolves. created_at_to: Search for shipments created before this date: ISO8601 date format. updated_at_to: Search for shipments updated before this date: ISO8601 date format. delivery_state: Filter by delivery status (e.g. "in_transit_to_customer", "delivered", "exception"). Pass values exactly as returned by the API; the set may change as the platform evolves. shipment_state: Filter by shipment lifecycle state (e.g. "created", "cancelled"). created_at_from: Search for shipments created since this date: ISO8601 date format. updated_at_from: Search for shipments updated since this date: ISO8601 date format. warehouse_state: For eFulfilment only. Filter by warehouse state (e.g. "pending", "packed", "shipped"). Pass values exactly as returned by the API. label_paid_at_to: Search for shipments where the labels were paid for before this date: ISO8601 date format. label_paid_at_from: Search for shipments where the labels were paid for since this date: ISO8601 date format. label_generated_at_to: Search for labels generated before this date: ISO8601 date format. origin_country_alpha2: Search by the shipment origin country code: Alpha-2 format (ISO 3166-1). platform_order…
| Name | Type | Req | Description |
|---|---|---|---|
| created_at_from | – | – | – |
| created_at_to | – | – | – |
| delivery_state | – | – | – |
| destination_country_alpha2 | – | – | – |
| include_contact_details | boolean | – | Include the recipient's contact email and phone in the response. Defaults to false, which withholds them. Set to true only when the user explicitly asked for contact details; leave it false for routi… |
| label_generated_at_from | – | – | – |
| label_generated_at_to | – | – | – |
| label_paid_at_from | – | – | – |
| label_paid_at_to | – | – | – |
| label_state | – | – | – |
| origin_country_alpha2 | – | – | – |
| page | – | – | – |
| per_page | – | – | – |
| pickup_id | string | yes | The Easyship pickup ID to list shipments for. |
| pickup_state | – | – | – |
| platform_order_number | – | – | – |
| return_shipment | – | – | – |
| shipment_state | – | – | – |
| updated_at_from | – | – | – |
| updated_at_to | – | – | – |
| warehouse_state | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_pickups List Pickups (list_pickups) ~308
Retrieve a list of pickups. Required authorization scope: `public.pickup:read` Args: page: Page number to fetch, minimum: 1. per_page: Number of records per page to fetch, minimum: 1, maximum: 100. courier: Filter by courier name (e.g. "DHL Express", "USPS"). Pass the courier name exactly as returned by the API; the available set changes as couriers are added or removed. pickup_date: Filter by pickup date in YYYY-MM-DD format. shipment_id: Filter by shipment ID. pickup_state: Filter by pickup state (e.g. "requested", "completed", "cancelled"). Pass the state string exactly as returned by the API. include_contact_details: Set to true only when the user explicitly asked for the recipient's contact email or phone. Defaults to false, which omits them. Returns: A paginated list of pickup objects matching the filter criteria.
| Name | Type | Req | Description |
|---|---|---|---|
| courier | – | – | – |
| include_contact_details | boolean | – | Include the recipient's contact email and phone in the response. Defaults to false, which withholds them. Set to true only when the user explicitly asked for contact details; leave it false for routi… |
| page | – | – | – |
| per_page | – | – | – |
| pickup_date | – | – | – |
| pickup_state | – | – | – |
| shipment_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_shipments List Shipments (list_shipments) ~905
Find and filter shipments, returning a summary of each one. Cancelled shipments are excluded by default (`shipment_state="created"`); `"cancelled"` returns only cancelled ones and `"all"` returns both. Each result carries the shipment ID, lifecycle states, dates, weight, courier, order reference, and tracking numbers, plus origin and destination country. Street addresses, parcel contents, documents, and rates are not included in this summary; they are part of the single-shipment detail (`get_shipment`). Covers finding shipments by filter (state, courier, country, date range, order number), listing or counting matching shipments, and looking up a shipment's ID or current status. Aggregate counts over time are available from the analytics endpoints. Required authorization scope: `public.shipment:read` Args: page: Page number to fetch, default: `1` per_page: Number of records per page to fetch, default: `20` label_state: Filter by label status (e.g. "pending", "generated", "failed"). Pass values exactly as returned by the API; the set may change as the platform evolves. pickup_state: Filter by pickup status (e.g. "requested", "completed", "cancelled"). Pass values exactly as returned by the API; the set may change as the platform evolves. created_at_to: Search for shipments created before this date: ISO8601 date format. updated_at_to: Search for shipments updated before this date: ISO8601 date format. delivery_state: Filter by delivery status (e.g. "in_transit_to_customer", "delivered", "exception"). Pass values exactly as returned by the API; the set may change as the platform evolves. shipment_state: "created" (default, excludes cancelled), "cancelled", or "all". created_at_from: Search for shipments created since this date: ISO8601 date format. updated_at_from: Search for shipments updated since this date: ISO8601 date format. warehouse_state: For eFulfilment only. Filt…
| Name | Type | Req | Description |
|---|---|---|---|
| created_at_from | – | – | – |
| created_at_to | – | – | – |
| delivery_state | – | – | – |
| destination_country_alpha2 | – | – | – |
| easyship_shipment_id | – | – | – |
| include_contact_details | boolean | – | Include the recipient's contact email and phone in the response. Defaults to false, which withholds them. Set to true only when the user explicitly asked for contact details; leave it false for routi… |
| label_generated_at_from | – | – | – |
| label_generated_at_to | – | – | – |
| label_paid_at_from | – | – | – |
| label_paid_at_to | – | – | – |
| label_state | – | – | – |
| origin_country_alpha2 | – | – | – |
| page | – | – | – |
| per_page | – | – | – |
| pickup_state | – | – | – |
| platform_order_number | – | – | – |
| return_shipment | – | – | – |
| shipment_state | string | – | – |
| updated_at_from | – | – | – |
| updated_at_to | – | – | – |
| warehouse_state | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_transactions List Transactions (list_transactions) ~271
Retrieve a list of all transactions within range. Pagination of this endpoint is not indexed. `count` on the response body will always be `null`. Required authorization scope: `public.transaction_record:read` Args: page: Page number to fetch, minimum: 1. transaction_type: Filter by transaction type (e.g. "shipment", "pickup", "payment"). to_date: Filter transactions before this date in YYYY-MM-DD format. per_page: Number of records per page to fetch, minimum: 1, maximum: 100. from_date: Filter transactions since this date in YYYY-MM-DD format. adjustment: Filter by adjustment transactions. days_from_now: Filter transactions from this many days ago, minimum: 1. easyship_shipment_id: Filter by Easyship shipment ID, e.g. "ESSG10006001". Must match pattern ^ES\w{2}\d{7,}$. Returns: A paginated list of transaction objects matching the filter criteria.
| Name | Type | Req | Description |
|---|---|---|---|
| adjustment | – | – | – |
| days_from_now | – | – | – |
| easyship_shipment_id | – | – | – |
| from_date | – | – | – |
| page | – | – | – |
| per_page | – | – | – |
| to_date | – | – | – |
| transaction_type | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
track_shipment Track Shipment (track_shipment) ~183
Track a shipment and get its current status plus checkpoint history. At least one of `easyship_shipment_id` or `platform_order_number` is required; omitting both returns an error from this tool. Returns the latest status, estimated delivery date, and a list of tracking checkpoints showing the shipment's journey.
| Name | Type | Req | Description |
|---|---|---|---|
| easyship_shipment_id | – | – | The Easyship shipment ID, e.g. "ESSG10006001" or "ESHK10017799". You get this when creating a shipment via the API or from the Easyship dashboard. **Required if `platform_order_number` is not provide… |
| platform_order_number | – | – | Your store's order number, e.g. "#1042". Use this if you don't have the Easyship shipment ID. **Required if `easyship_shipment_id` is not provided.** |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
update_shipment Update Shipment (update_shipment) ~366
Update an existing shipment's details. Required authorization scope: `public.shipment:write`. The `shipment_data` dict follows the same schema as `create_shipment` — include only the fields you want to change. See `create_shipment` docstring for the full payload schema. If you include **`parcels`**, each line item should still have `category` or `hs_code` — the Easyship API requires at least one per item. Args: easyship_shipment_id: Easyship Shipment ID, e.g. "ESSG10006001". shipment_data: Partial shipment payload — same schema as create_shipment, include only fields to update. Common updates: destination_address, parcels, courier_settings, shipping_settings, incoterms. Returns: The updated shipment object from the Easyship API. If identity verification affects label purchase, the payload may include `support_email`, `support_email_link`, and `support_reply_hint`.
| Name | Type | Req | Description |
|---|---|---|---|
| easyship_shipment_id | string | yes | The Easyship shipment ID, e.g. 'ESSG10006001'. |
| shipment_data | object | yes | Partial payload for patching a shipment — include only the top-level keys to change. All top-level fields are optional; omit any key you are not changing. destination_address — if provided, require… |
Structured output declared, but exposes no named fields.
No examples provided.
validate_address Validate Address (validate_address) ~336
Validate a shipping address and save it to the Easyship address book. Works for both US domestic and international addresses. If `country_alpha2` is "US" or omitted, uses the domestic validation endpoint. Otherwise, uses the international validation endpoint. Required authorization scope: - `public.address_validation_domestic:write` for US addresses. - `public.address_validation:write` for international addresses. > This API requires an updated contract with Easyship. Contact your account manager or Easyship Support Team. Args: line_1: Address line 1 (street address). city: City name. country_alpha2: Country code in Alpha-2 format (ISO 3166-1). Omit or use "US" for US domestic validation. state: State or province. Required for AU, CA, CN, ID, MX, MY, TH, US, VN. line_2: Address line 2 (apartment, suite, etc.). postal_code: Postal or ZIP code. company_name: Company name. replace_with_validation_result: Whether to replace the address with the validation result. Default: false. Returns: Address validation result with suggested corrections, or an error.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City name, e.g. 'San Francisco'. |
| company_name | – | – | – |
| country_alpha2 | – | – | – |
| line_1 | string | yes | Street address line 1, e.g. '1 Infinite Loop'. |
| line_2 | – | – | – |
| postal_code | – | – | – |
| replace_with_validation_result | – | – | – |
| state | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Easyship MCP server?
Easyship runs locally as a PyPI package, launched with uvx easyship-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 · easyship-mcp
claude mcp add com-easyship-mcp -- uvx easyship-mcp
What is the Easyship MCP server?
Easyship is an MCP server listed in the public MCP registry as com.easyship/mcp. Connect Easyship to compare rates, create shipments, buy labels, and track packages globally. This page covers its PyPI package (easyship-mcp).
Is the Easyship MCP server safe to use?
Easyship scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. 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 Easyship MCP server expose?
Easyship exposes 25 tools: get_rates, track_shipment, create_shipment, update_shipment, list_shipments, and 20 more. Their descriptions and schemas cost roughly 9,309 tokens of context every time the server is loaded.
Is the Easyship MCP server still maintained?
Easyship is still listed as active in the MCP registry. We last reached this channel on 4 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 Easyship MCP server under?
Easyship declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.