# Shipcloud MCP by usefulapi (remote · shipcloud.usefulapi.io)

Track shipments and quote shipping; prepare shipments, buy labels and request carrier pickups.

- Trust score: 18/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `shipcloud.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-shipcloud/shipcloud.md), [page](https://verifymcp.io/servers/io-usefulapi-shipcloud/shipcloud)

## Channel facts

- Endpoint: `https://shipcloud.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.7.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Shipcloud MCP by usefulapi server?

Shipcloud MCP by usefulapi is a hosted endpoint at https://shipcloud.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-usefulapi-shipcloud 'https://shipcloud.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-shipcloud": {
      "url": "https://shipcloud.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-shipcloud": {
      "type": "http",
      "url": "https://shipcloud.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-shipcloud]
url = "https://shipcloud.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-shipcloud": {
      "type": "remote",
      "url": "https://shipcloud.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-shipcloud --url 'https://shipcloud.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-shipcloud:
    url: "https://shipcloud.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-shipcloud": {
      "Transport": "http",
      "Url": "https://shipcloud.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-shipcloud -t streamable-http -u 'https://shipcloud.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-shipcloud": {
      "type": "http",
      "url": "https://shipcloud.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-01 (score 18, −46)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-31 (score 64)

First indexed and scored.

## MCP tools (22)

### `shipcloud_get_account` (~59 tokens)

Get account

The shipcloud user behind this API key: id, email, customer number, plan, and the ENVIRONMENT of the key (production = real labels and charges, sandbox = free test labels). Check this before creating labels. GET /me.

### `shipcloud_list_carriers` (~46 tokens)

List carriers

The carriers this account can use, each with its services, package types, additional services and label formats per service. Use the values when creating shipments. GET /carriers.

### `shipcloud_get_default_address` (~67 tokens)

Get a default address

One of the account's saved default addresses: shipping (the default sender), returns (the default recipient of return shipments) or invoice (the invoice address). GET /default_shipping_address, /default_returns_address or /invoice_address.

Input parameters:

- `kind` (string, required): Which default address.

### `shipcloud_list_shipments` (~335 tokens)

List shipments

List shipments (newest first as shipcloud returns them) with carrier, service, price, tracking number, tracking URL, label URL, addresses and tracking events. Filters can be combined. Paged: pass the previous reply's next_page. shipcloud sends no totals, so next_page is a guess (a full page suggests more). GET /shipments.

Input parameters:

- `carrier` (string)
- `carrier_tracking_no` (string): The carrier's tracking number.
- `created_after` (string): ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z.
- `created_before` (string): ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `reference_number` (string): The reference_number given when the shipment was created.
- `service` (string)
- `shipcloud_tracking_no` (string): The shipcloud shipment id / tracking number.
- `shipment_type` (string): prepared = saved without a label; label_created = has a label; tracking_only = imported tracker.
- `source` (string): Where the shipment was created.
- `tracking_status` (string): Only shipments with this tracking status.
- `tracking_status_not` (string): Only shipments WITHOUT this tracking status, e.g. delivered.

### `shipcloud_get_shipment` (~62 tokens)

Get shipment

One shipment by id: addresses, packages with tracking events, price, label URL, tracking URL. Sandbox shipments have no tracking events and price 0. GET /shipments/{id}.

Input parameters:

- `shipment_id` (string, required): The id shipcloud returned.

### `shipcloud_get_shipment_quote` (~159 tokens)

Quote a shipment price

What shipcloud would charge for a shipment (price in EUR excl. VAT). Read-only: nothing is created and nothing is charged. Only works for carrier contracts owned by shipcloud. Use it before shipcloud_create_shipment_with_label. POST /shipment_quotes.

Input parameters:

- `carrier` (string, required): Carrier acronym (shipcloud_list_carriers shows the ones this account can use).
- `from`: Sender; omitted = the account's default sender address.
- `packages` (array, required)
- `service` (string, required): Service (default standard). Which services a carrier offers: shipcloud_list_carriers.
- `to` (required): An address (street, zip_code, city, country are enough), or {id} of a saved address.

### `shipcloud_create_prepared_shipment` (~314 tokens)

Create a prepared shipment (no label)

WRITE: save a shipment in shipcloud WITHOUT buying a label (create_shipping_label=false). Nothing is charged and no carrier is contacted; a prepared shipment can be deleted any time. Returns the shipment id. To buy the label use shipcloud_create_shipment_with_label. POST /shipments.

Input parameters:

- `carrier` (string, required): Carrier acronym (shipcloud_list_carriers shows the ones this account can use).
- `description` (string): Contents. Mandatory for UPS international/non-standard and DHL Express. Shipments that need a customs declaration (outside the EU) are not supported here: create them in the shipcloud backoffice.
- `from` (object): Sender full address. If omitted, shipcloud uses the default sender address of the account.
- `label_format` (string): Label format, e.g. pdf_a6 or zpl2_4x6in_203dpi; carriers support different ones (shipcloud_list_carriers shows them per service).
- `notification_email` (string): shipcloud emails this address on tracking updates.
- `packages` (array, required): The packages (one entry for a single parcel). Several packages: only UPS supports them.
- `reference_number` (string): Your own reference (max 30 characters), searchable later.
- `service` (string): Service (default standard). Which services a carrier offers: shipcloud_list_carriers.
- `to` (object, required): Recipient full address (company or last_name needed). Read a saved address first to copy its fields.

### `shipcloud_create_shipment_with_label` (~519 tokens)

Buy a shipping label (costs money)

WRITE, COSTS MONEY: create a shipment AND buy its shipping label at the carrier (create_shipping_label=true). With a LIVE key this charges the shipcloud account (price in EUR excl. VAT; get it first from shipcloud_get_shipment_quote) and creates a real label; with the sandbox key it is free and fake. A label can only be cancelled before the carrier's cut-off (about 17:00-20:00) with shipcloud_delete_shipment. The request is sent ONCE and never retried: if it times out or fails with a server error, the label may still exist, so check shipcloud_list_shipments with the same reference_number before trying again. An existing-label lookup and same-instance guard reduce duplicates but are not atomic or global: simultaneous requests across Worker instances can buy duplicate labels. Serialize purchases for each reference and check shipcloud after an uncertain result. Requires confirm=true after the user agreed to the purchase; give a unique reference_number. Shipments needing customs papers are not supported here. POST /shipments.

Input parameters:

- `carrier` (string, required): Carrier acronym (shipcloud_list_carriers shows the ones this account can use).
- `confirm` (boolean, required): Must be exactly true. Set it ONLY after the user has explicitly agreed to buy this label and be charged for it. Ask first; do not assume.
- `description` (string): Contents. Mandatory for UPS international/non-standard and DHL Express. Shipments that need a customs declaration (outside the EU) are not supported here: create them in the shipcloud backoffice.
- `from` (object): Sender full address. If omitted, shipcloud uses the default sender address of the account.
- `label_format` (string): Label format, e.g. pdf_a6 or zpl2_4x6in_203dpi; carriers support different ones (shipcloud_list_carriers shows them per service).
- `notification_email` (string): shipcloud emails this address on tracking updates.
- `packages` (array, required): The packages (one entry for a single parcel). Several packages: only UPS supports them.
- `reference_number` (string, required): Your own unique reference (max 30 characters). Required: it is how a possible duplicate is found after a timeout.
- `service` (string): Service (default standard). Which services a carrier offers: shipcloud_list_carriers.
- `to` (object, required): Recipient full address (company or last_name needed). Read a saved address first to copy its fields.

### `shipcloud_delete_shipment` (~138 tokens)

Delete a shipment / cancel its label

WRITE, DESTRUCTIVE: delete a shipment. A prepared shipment (no label) can be deleted any time. For a shipment with a label, shipcloud cancels the label only before the carrier's cut-off (about 17:00-20:00); afterwards it fails. Cannot be undone. Requires confirm=true after the user agreed. DELETE /shipments/{id}.

Input parameters:

- `confirm` (boolean, required): Must be exactly true. Set it ONLY after the user has explicitly agreed to delete this shipment (and cancel its label). Ask first; do not assume.
- `shipment_id` (string, required): The id shipcloud returned.

### `shipcloud_list_trackers` (~49 tokens)

List trackers

List trackers: shipments created OUTSIDE shipcloud that shipcloud tracks by the carrier's tracking number (only for your own carrier contracts), with status and tracking events. GET /trackers.

### `shipcloud_get_tracker` (~41 tokens)

Get tracker

One tracker by id, with status and tracking events. GET /trackers/{id}.

Input parameters:

- `tracker_id` (string, required): The id shipcloud returned.

### `shipcloud_create_tracker` (~97 tokens)

Track a shipment by its tracking number

WRITE: have shipcloud track a parcel that was NOT created with shipcloud, by the carrier's tracking number (only for your own carrier contracts; carriers dhl, dpd, gls, ups). Creates a tracker; no label, no shipping charge. POST /trackers.

Input parameters:

- `carrier` (string, required)
- `carrier_tracking_no` (string, required): The carrier's tracking number.
- `notification_email` (string)

### `shipcloud_list_pickup_requests` (~34 tokens)

List pickup requests

List carrier pickup requests with carrier, pickup time window, address and the shipments included. GET /pickup_requests.

### `shipcloud_get_pickup_request` (~39 tokens)

Get pickup request

One pickup request by id. GET /pickup_requests/{id}.

Input parameters:

- `pickup_request_id` (string, required): The id shipcloud returned.

### `shipcloud_create_pickup_request` (~202 tokens)

Request a carrier pickup

WRITE: order a carrier (dpd, gls, hermes or ups) to pick up parcels at an address in a time window. A real request goes to the carrier and cannot be cancelled through this server; carriers may bill pickups. Without `shipment_ids` the carrier collects all shipments not yet picked up; return shipments cannot be picked up. Requires confirm=true after the user agreed. POST /pickup_requests.

Input parameters:

- `carrier` (string, required)
- `confirm` (boolean, required): Must be exactly true. Set it ONLY after the user has explicitly agreed to order this carrier pickup. Ask first; do not assume.
- `earliest` (string, required): Earliest pickup, ISO 8601 with timezone.
- `latest` (string, required): Latest pickup, ISO 8601 with timezone.
- `pickup_address` (object, required): Where the carrier collects the parcels.
- `shipment_ids` (array): Only these shipments; omitted = all not yet picked up.

### `shipcloud_find_dropoff_locations` (~163 tokens)

Find pickup and drop-off points

Search a carrier's parcel shops, lockers and drop-off points near an address or coordinates (opening hours, distance). Give an address (street, zip_code, city, country) or latitude + longitude. GET /pickup_dropoff_locations.

Input parameters:

- `carriers` (array, required): Carrier acronyms to search.
- `city` (string)
- `country` (string): Uppercase ISO 3166-1 alpha-2 code.
- `latitude` (number)
- `limit` (integer): Max locations (default 10).
- `longitude` (number)
- `radius` (integer): Search radius in meters (default 10000).
- `state` (string)
- `street` (string)
- `zip_code` (string)

### `shipcloud_list_addresses` (~137 tokens)

List saved addresses

List the address book (saved addresses with ids usable as `to` / `from`). Filter by any field. Paged. GET /addresses.

Input parameters:

- `city` (string)
- `company` (string)
- `country` (string)
- `first_name` (string)
- `last_name` (string)
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `street` (string)
- `zip_code` (string)

### `shipcloud_get_address` (~35 tokens)

Get saved address

One saved address by id. GET /addresses/{id}.

Input parameters:

- `address_id` (string, required): The id shipcloud returned.

### `shipcloud_create_address` (~51 tokens)

Save an address

WRITE: save an address in the shipcloud address book (no shipment, no cost). Returns its id. It cannot be removed through this server. POST /addresses.

Input parameters:

- `address` (object, required)

### `shipcloud_list_orders` (~40 tokens)

List orders

List orders sent to shipcloud (order data with line items, used by the Return Portal and linked to shipments by order_id). GET /orders.

### `shipcloud_get_order` (~41 tokens)

Get order

One order by id, with delivery address and line items. GET /orders/{id}.

Input parameters:

- `order_id` (string, required): The id shipcloud returned.

### `shipcloud_list_webhooks` (~44 tokens)

List webhooks

List the webhooks configured in the account: target URL, subscribed event types, deactivated flag. Credentials of a webhook are never shown. GET /webhooks.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-shipcloud/shipcloud#diagnostics

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 18
- 2026-10-31: 64

## Common questions

### What is the Shipcloud MCP by usefulapi server?

Shipcloud MCP by usefulapi is listed in the public MCP registry as io.usefulapi/shipcloud. Track shipments and quote shipping; prepare shipments, buy labels and request carrier pickups. This page covers its hosted endpoint (https://shipcloud.usefulapi.io/mcp).

### Is the Shipcloud MCP by usefulapi server safe to use?

Shipcloud MCP by usefulapi scores 18 out of 100 on VerifyMCP. 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 Shipcloud MCP by usefulapi server expose?

Shipcloud MCP by usefulapi exposes 22 tools: shipcloud_get_account, shipcloud_list_carriers, shipcloud_get_default_address, shipcloud_list_shipments, shipcloud_get_shipment, and 17 more. Their descriptions and schemas cost roughly 2,672 tokens of context every time the server is loaded.

### Does the Shipcloud MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Shipcloud MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Shipcloud MCP by usefulapi server still maintained?

Shipcloud MCP by usefulapi 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.

## Links

- Remote endpoint: https://shipcloud.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/shipcloud/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-shipcloud/shipcloud.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-shipcloud/shipcloud.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-shipcloud/shipcloud