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.

Shipcloud MCP by usefulapi

REMOTE · SHIPCLOUD.USEFULAPI.IO

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

18 Trust /100

Last scanned (23 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 4 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

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.

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.

  • 1 Nov 26 −46
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 31 Oct 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 4 Nov 2026 · Probed https://shipcloud.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d9be3287b0fde9630e825ba1f79bff3f
SANs: usefulapi.io, *.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of shipcloud.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 302

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://shipcloud.usefulapi.io/mcp Redirected 302 https://usefulapi.io/shipcloud/
http (plaintext) http://shipcloud.usefulapi.io/mcp Inconclusive 302 http://shipcloud.usefulapi.io/mcp
MCP tools · 22 exposed · ~2,672 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
shipcloud_create_address ~51

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.

NameTypeReqDescription
addressobjectyes–

No output schema declared.

No examples provided.

shipcloud_create_pickup_request ~202

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.

NameTypeReqDescription
carrierstringyes–
confirmbooleanyesMust be exactly true. Set it ONLY after the user has explicitly agreed to order this carrier pickup. Ask first; do not assume.
earlieststringyesEarliest pickup, ISO 8601 with timezone.
lateststringyesLatest pickup, ISO 8601 with timezone.
pickup_addressobjectyesWhere the carrier collects the parcels.
shipment_idsarray–Only these shipments; omitted = all not yet picked up.

No output schema declared.

No examples provided.

shipcloud_create_prepared_shipment ~314

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.

NameTypeReqDescription
carrierstringyesCarrier acronym (shipcloud_list_carriers shows the ones this account can use).
descriptionstring–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.
fromobject–Sender full address. If omitted, shipcloud uses the default sender address of the account.
label_formatstring–Label format, e.g. pdf_a6 or zpl2_4x6in_203dpi; carriers support different ones (shipcloud_list_carriers shows them per service).
notification_emailstring–shipcloud emails this address on tracking updates.
packagesarrayyesThe packages (one entry for a single parcel). Several packages: only UPS supports them.
reference_numberstring–Your own reference (max 30 characters), searchable later.
servicestring–Service (default standard). Which services a carrier offers: shipcloud_list_carriers.
toobjectyesRecipient full address (company or last_name needed). Read a saved address first to copy its fields.

No output schema declared.

No examples provided.

shipcloud_create_shipment_with_label ~519

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.

NameTypeReqDescription
carrierstringyesCarrier acronym (shipcloud_list_carriers shows the ones this account can use).
confirmbooleanyesMust 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.
descriptionstring–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.
fromobject–Sender full address. If omitted, shipcloud uses the default sender address of the account.
label_formatstring–Label format, e.g. pdf_a6 or zpl2_4x6in_203dpi; carriers support different ones (shipcloud_list_carriers shows them per service).
notification_emailstring–shipcloud emails this address on tracking updates.
packagesarrayyesThe packages (one entry for a single parcel). Several packages: only UPS supports them.
reference_numberstringyesYour own unique reference (max 30 characters). Required: it is how a possible duplicate is found after a timeout.
servicestring–Service (default standard). Which services a carrier offers: shipcloud_list_carriers.
toobjectyesRecipient full address (company or last_name needed). Read a saved address first to copy its fields.

No output schema declared.

No examples provided.

shipcloud_create_tracker ~97

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.

NameTypeReqDescription
carrierstringyes–
carrier_tracking_nostringyesThe carrier's tracking number.
notification_emailstring––

No output schema declared.

No examples provided.

shipcloud_delete_shipment ~138

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}.

NameTypeReqDescription
confirmbooleanyesMust 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_idstringyesThe id shipcloud returned.

No output schema declared.

No examples provided.

shipcloud_find_dropoff_locations ~163

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.

NameTypeReqDescription
carriersarrayyesCarrier acronyms to search.
citystring––
countrystring–Uppercase ISO 3166-1 alpha-2 code.
latitudenumber––
limitinteger–Max locations (default 10).
longitudenumber––
radiusinteger–Search radius in meters (default 10000).
statestring––
streetstring––
zip_codestring––

No output schema declared.

No examples provided.

shipcloud_get_account ~59

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

shipcloud_get_address ~35

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

NameTypeReqDescription
address_idstringyesThe id shipcloud returned.

No output schema declared.

No examples provided.

shipcloud_get_default_address ~67

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.

NameTypeReqDescription
kindstringyesWhich default address.

No output schema declared.

No examples provided.

shipcloud_get_order ~41

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

NameTypeReqDescription
order_idstringyesThe id shipcloud returned.

No output schema declared.

No examples provided.

shipcloud_get_pickup_request ~39

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

NameTypeReqDescription
pickup_request_idstringyesThe id shipcloud returned.

No output schema declared.

No examples provided.

shipcloud_get_shipment ~62

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}.

NameTypeReqDescription
shipment_idstringyesThe id shipcloud returned.

No output schema declared.

No examples provided.

shipcloud_get_shipment_quote ~159

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.

NameTypeReqDescription
carrierstringyesCarrier acronym (shipcloud_list_carriers shows the ones this account can use).
from––Sender; omitted = the account's default sender address.
packagesarrayyes–
servicestringyesService (default standard). Which services a carrier offers: shipcloud_list_carriers.
to–yesAn address (street, zip_code, city, country are enough), or {id} of a saved address.

No output schema declared.

No examples provided.

shipcloud_get_tracker ~41

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

NameTypeReqDescription
tracker_idstringyesThe id shipcloud returned.

No output schema declared.

No examples provided.

shipcloud_list_addresses ~137

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

NameTypeReqDescription
citystring––
companystring––
countrystring––
first_namestring––
last_namestring––
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page, 1-100 (default 25).
streetstring––
zip_codestring––

No output schema declared.

No examples provided.

shipcloud_list_carriers ~46

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

shipcloud_list_orders ~40

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

shipcloud_list_pickup_requests ~34

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

shipcloud_list_shipments ~335

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.

NameTypeReqDescription
carrierstring––
carrier_tracking_nostring–The carrier's tracking number.
created_afterstring–ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z.
created_beforestring–ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page, 1-100 (default 25).
reference_numberstring–The reference_number given when the shipment was created.
servicestring––
shipcloud_tracking_nostring–The shipcloud shipment id / tracking number.
shipment_typestring–prepared = saved without a label; label_created = has a label; tracking_only = imported tracker.
sourcestring–Where the shipment was created.
tracking_statusstring–Only shipments with this tracking status.
tracking_status_notstring–Only shipments WITHOUT this tracking status, e.g. delivered.

No output schema declared.

No examples provided.

shipcloud_list_trackers ~49

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

shipcloud_list_webhooks ~44

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

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.

remote · shipcloud.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-shipcloud 'https://shipcloud.usefulapi.io/mcp'
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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.