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.

Shippit MCP by usefulapi

REMOTE · SHIPPIT.USEFULAPI.IO

Get Shippit quotes, track and manage orders; create, label, book and cancel shipments on approval.

61 Trust /100

Last scanned (5 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 25 Oct 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 Security78
Transport & Reachability0
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2258 tokens (~188/item across 12 items; 12 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 Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 75% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 25 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.1.0 → 1.1.3 functional
  • 24 Oct 26 61

    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 25 Oct 2026 · Probed https://shippit.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 shippit.usefulapi.io. — Not signed

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

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 302

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://shippit.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Bearer realm="OAuth", resource_metadata="https://shippit.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://shippit.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://shippit.usefulapi.io/mcp
Authorisation server https://shippit.usefulapi.io

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://shippit.usefulapi.io/mcp Redirected 302 https://usefulapi.io/shippit/
http (plaintext) http://shippit.usefulapi.io/mcp Inconclusive 302 http://shippit.usefulapi.io/mcp
MCP tools · 12 exposed · ~1,960 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
shippit_book_orders ~157

WRITE: book labelled orders with their carriers for pickup (the Shippit 'book' step). Shippit returns one manifest per carrier; the carrier then collects and bills the parcels. Orders must have been labelled first (shippit_label_order). The call fails as a whole when a tracking number is unknown; otherwise each manifest reports success or an error per order. Booked orders can no longer be edited. Requires confirm: true. A reply where every manifest failed is an error. POST /book.

NameTypeReqDescription
confirmbooleanyesMust be true. Booking commits the orders to carrier pickup and charges; ask the user to confirm first.
tracking_numbersarrayyesTracking numbers of the labelled orders to book.

No output schema declared.

No examples provided.

shippit_cancel_order ~143

WRITE: cancel a Shippit order by tracking number (the order ends in state cancelled and cannot be revived; for some carriers Shippit also sends a cancellation request to the carrier). Shippit refuses with a 422 and the reason when the order can no longer be cancelled, for example once the carrier has it. Requires confirm: true. DELETE /orders/{tracking_number}.

NameTypeReqDescription
confirmbooleanyesMust be true. A cancelled order cannot be recovered; ask the user to confirm first.
tracking_numberstringyesThe Shippit tracking number of the order (returned by shippit_create_order; usually starts with PP).

No output schema declared.

No examples provided.

shippit_create_order ~601

WRITE: create a domestic shipping order in Shippit. Shippit then allocates a carrier (your account rules, or the carrier named in courier_allocation) and, unless suppress_communications is true, emails the recipient tracking notifications. Requires confirm: true. Standard, express and click-and-collect orders are only booked with the carrier later, by shippit_label_order and shippit_book_orders (priority and on-demand orders, which book inside the create request, are not supported here). validate defaults to true: the order is not saved when the suburb and postcode do not match (a suggested address is returned instead). Creating twice creates two orders. International orders (customs data) are not supported here. POST /orders.

NameTypeReqDescription
authority_to_leavestring–Whether the parcel may be left unattended.
confirmbooleanyesMust be true. The order is real: it can email the customer and, for a named on-demand carrier, book it at once. Ask the user to confirm first.
courier_allocationstring–A specific carrier keyword, e.g. CouriersPlease (see the Shippit carriers list). Instead of courier_type.
courier_typestring–Service level (default standard). Give this or courier_allocation.
customer_emailstringyesThe customer's email (Shippit sends tracking notifications here unless suppressed).
customer_first_namestringyes–
customer_last_namestring––
customer_mobilestring––
delivery_addressstringyes–
delivery_companystring––
delivery_country_codestring–Two-letter country code (default: the merchant's home country, usually AU).
delivery_instructionsstring–Instructions for the driver, at most 55 characters.
delivery_postcodestringyes–
delivery_statestringyesState. Australian orders use NSW, VIC, QLD, WA, SA, TAS, ACT or NT.
delivery_suburbstringyes–
featuresarray–Carrier add-on services; some need prior approval from Shippit.
parcelsarrayyesThe parcels (qty and weight are the minimum; leave qty out when you also send products).
productsarray–Optional line items for the packing slip.
receiver_contact_numberstring––
receiver_namestring–Name of the person receiving it, if different from the customer.
retailer_invoicestring–Your order number, printed on the label and packing slip.
retailer_referencestring––
suppress_communicationsboolean–true = Shippit sends no tracking notifications to the customer for this order (default false: it does).
tagsarray–Your own labels for filtering.
validateboolean–Reject the order if suburb and postcode do not match (default true).

No output schema declared.

No examples provided.

shippit_estimate_delivery_dates ~151

Estimated delivery window (earliest, latest, confidence and a ready-to-show text) per service level (standard, express) between two postcodes, optionally limited to some carriers. Returns an empty list if no carrier is enabled. POST /estimated_delivery_dates.

NameTypeReqDescription
couriersarray–Carrier keywords to estimate for, e.g. CouriersPlease (default: all enabled).
from_postcodestringyesOrigin (pickup) postcode.
preparation_timestring–Lead time before pickup as DD:HH:MM, e.g. 01:05:30.
service_levelsarray––
to_postcodestringyesDestination postcode.

No output schema declared.

No examples provided.

shippit_get_manifest_document ~97

The booking manifest document for a manifest id (from shippit_book_orders or shippit_get_order): carrier, order count, tracking numbers and a pre-signed PDF URL valid for 7 days. A 422 means the manifest is still generating: retry shortly. GET /book/{manifest_id}/document.

NameTypeReqDescription
manifest_idintegeryesThe Shippit manifest id (not the carrier's manifest number).

No output schema declared.

No examples provided.

shippit_get_merchant ~48

The Shippit merchant account behind this API key: store and company name, contact, preparation time, website and the home (pickup) address with country. GET /merchant.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

shippit_get_operating_hours ~54

The store operating hours per weekday (open flag, start and end of the working day) that Shippit uses for pickup and delivery estimates. GET /merchants/settings/locations/operating_hours.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

shippit_get_order ~97

One Shippit order by tracking number: state, courier and price allocated, delivery address, receiver, parcels, products, references and (once booked) manifest id and number. There is no list-orders endpoint in the Shippit API. GET /orders/{tracking_number}.

NameTypeReqDescription
tracking_numberstringyesThe Shippit tracking number of the order (returned by shippit_create_order; usually starts with PP).

No output schema declared.

No examples provided.

shippit_get_quotes ~312

Ask the carriers enabled on the account for a price and delivery estimate to a destination, for given parcels. Nothing is booked and nothing is charged. Set return_all_quotes to see every carrier instead of only the cheapest or fastest. A 200 can hold per-carrier errors (success false) and a quote of 0 means that carrier cannot take the parcel. Dangerous goods cannot be quoted. POST /quotes.

NameTypeReqDescription
authority_to_leavestring–Whether the parcel may be left unattended.
dropoff_addressstring–Street address (required for on-demand quotes).
dropoff_country_codestring–Two-letter country code (default: the merchant's home country, usually AU).
dropoff_postcodestringyes–
dropoff_statestring–State. Australian orders use NSW, VIC, QLD, WA, SA, TAS, ACT or NT.
dropoff_suburbstringyes–
dutiable_amountnumber–Declared customs value (required for international quotes).
featuresarray–Carrier add-on services, e.g. white_glove.
order_datestring–Delivery date, yyyy-mm-dd (required for priority quotes).
parcelsarrayyesThe parcels to quote.
product_currencystring––
return_all_quotesboolean–Return the quotes of all carriers (default: only the cheapest or fastest).
service_levelsarray–Only quote these service levels.

No output schema declared.

No examples provided.

shippit_get_tracking ~78

The status history of an order (status, date, time, who changed it) and the public tracking page URL to give the recipient. GET /orders/{tracking_number}/tracking.

NameTypeReqDescription
tracking_numberstringyesThe Shippit tracking number of the order (returned by shippit_create_order; usually starts with PP).

No output schema declared.

No examples provided.

shippit_label_order ~159

WRITE: confirm an order for shipping and fetch its label. This is the Shippit 'label' step: it finalises the carrier and price (the order moves to Ready to Ship) and returns the carrier, tracking and consignment details plus pre-signed PDF URLs (valid 7 days) for the shipping label, packing slip and any customs documents. A 422 means the order is still processing or has no valid carrier or quote: retry shortly or read the error. Labelling is the step before shippit_book_orders. GET /orders/{tracking_number}/label.

NameTypeReqDescription
tracking_numberstringyesThe Shippit tracking number of the order (returned by shippit_create_order; usually starts with PP).

No output schema declared.

No examples provided.

shippit_list_webhooks ~63

The tracking webhooks configured on the account (at most 6): url, the order states that trigger each, whether address or receiver details are hidden, enabled flag. Custom header values are masked by Shippit. GET /merchants/webhooks.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Shippit MCP by usefulapi server?

Shippit MCP by usefulapi is a hosted endpoint at https://shippit.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 · shippit.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-shippit 'https://shippit.usefulapi.io/mcp'
Common questions

What is the Shippit MCP by usefulapi server?

Shippit MCP by usefulapi is listed in the public MCP registry as io.usefulapi/shippit. Get Shippit quotes, track and manage orders; create, label, book and cancel shipments on approval. This page covers its hosted endpoint (https://shippit.usefulapi.io/mcp).

Is the Shippit MCP by usefulapi server safe to use?

Shippit MCP by usefulapi scores 61 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 Shippit MCP by usefulapi server expose?

Shippit MCP by usefulapi exposes 12 tools: shippit_get_merchant, shippit_get_operating_hours, shippit_list_webhooks, shippit_get_quotes, shippit_estimate_delivery_dates, and 7 more. Their descriptions and schemas cost roughly 1,960 tokens of context every time the server is loaded.

Does the Shippit MCP by usefulapi server require authentication?

Yes. Shippit MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Shippit MCP by usefulapi server still maintained?

Shippit MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.