Skip to content

TrackingMore MCP by usefulapi

by usefulapi.io · remote · no sign-in to list tools · v1.3.3 · published by io.usefulapi

Track parcels with TrackingMore: detect couriers, create and read trackings, delivery status.

Deletes · 3
CompareRegistry entry

7 tools: 3 can delete or cancel things and 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http trackingmore https://trackingmore.usefulapi.io/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

7 tools

Deletes or cancels 3Claude Code: deny
  • trackingmore_create_trackingWRITE: register ONE shipment so TrackingMore starts tracking it.No findings

    Why it is in this group

    • The name "trackingmore_create_tracking" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: register ONE shipment so TrackingMore starts tracking it. This uses one credit of the account's plan (credits beyond the plan are billed by TrackingMore as overage): confirm with the user before creating, and never create trackings in bulk. Fails with 'Tracking No. already exists' if it is already registered. Needs the tracking number and the courier code (use trackingmore_detect_courier if unknown). Some couriers need extra fields (postal code, ship date, key). Returns the new tracking with its id. POST /trackings/create.

    Annotations the server declares

    • title: Register a shipment for tracking
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • trackingmore_delete_trackingWRITE (destructive): permanently remove one tracking from the TrackingMore account by id.No findings

    Why it is in this group

    • The name "trackingmore_delete_tracking" says "delete": a word for removing or ending something.
    • The description says "permanently remove".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE (destructive): permanently remove one tracking from the TrackingMore account by id. Its checkpoint history is lost; registering the shipment again later uses another credit. Confirm with the user first. DELETE /trackings/delete/{id}.

    Annotations the server declares

    • title: Delete a tracking
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • trackingmore_update_trackingWRITE: change the descriptive fields of a registered tracking (order number, customer name/email, title, note, label, language, postal code, ship date ...).No findings

    Why it is in this group

    • The name "trackingmore_update_tracking" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: change the descriptive fields of a registered tracking (order number, customer name/email, title, note, label, language, postal code, ship date ...). Only the fields you pass change; the tracking number and courier cannot be changed here. PUT /trackings/update/{id}.

    Annotations the server declares

    • title: Update a tracking
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Only reads 4Claude Code: allow
  • trackingmore_detect_courierFind which couriers a tracking number most likely belongs to (returns matching courier codes and names).No findings

    Why it is in this group

    • The description's first verb is "find": a word for reading.
    Description, as the server wrote it
    Find which couriers a tracking number most likely belongs to (returns matching courier codes and names). Use the code with trackingmore_create_tracking. Does not create anything. POST /couriers/detect.

    Annotations the server declares

    • title: Detect courier
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • trackingmore_get_trackingThe full tracking record of one shipment already registered in the account, including every checkpoint (origin_info / destination_info trackinfo with date, status, details and loca…No findings

    Why it is in this group

    • The name "trackingmore_get_tracking" says "get": a word for reading.
    Description, as the server wrote it
    The full tracking record of one shipment already registered in the account, including every checkpoint (origin_info / destination_info trackinfo with date, status, details and location). Look it up by tracking number; add courier_code if the number is used by several couriers. A number that was never registered is not found: register it with trackingmore_create_tracking first. GET /trackings/get?tracking_numbers=.

    Annotations the server declares

    • title: Get a shipment's tracking
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • trackingmore_list_couriersList the carriers TrackingMore supports with their courier_code, name, country, website, phone and the extra fields some of them need.No findings

    Why it is in this group

    • The name "trackingmore_list_couriers" says "list": a word for reading.
    Description, as the server wrote it
    List the carriers TrackingMore supports with their courier_code, name, country, website, phone and the extra fields some of them need. The full list is long (1,000+), so filter with `search` (matches name or code) and/or `country`; replies hold at most `limit` couriers. GET /couriers/all.

    Annotations the server declares

    • title: List supported couriers
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • trackingmore_list_trackingsList the shipments already registered in the TrackingMore account, newest first as the API returns them: id, tracking number, courier, delivery_status (pending, notfound, transit, …No findings

    Why it is in this group

    • The name "trackingmore_list_trackings" says "list": a word for reading.
    Description, as the server wrote it
    List the shipments already registered in the TrackingMore account, newest first as the API returns them: id, tracking number, courier, delivery_status (pending, notfound, transit, pickup, delivered, undelivered, exception, expired, inforeceived), latest event and milestone dates. Checkpoint lists are left out (use trackingmore_get_tracking for one shipment's full history). Filters: tracking numbers, courier, delivery status, created/updated date range. GET /trackings/get.

    Annotations the server declares

    • title: List trackings
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.3.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http trackingmore https://trackingmore.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__trackingmore__trackingmore_list_couriers",
      "mcp__trackingmore__trackingmore_detect_courier",
      "mcp__trackingmore__trackingmore_list_trackings",
      "mcp__trackingmore__trackingmore_get_tracking"
    ],
    "ask": [],
    "deny": [
      "mcp__trackingmore__trackingmore_create_tracking",
      "mcp__trackingmore__trackingmore_update_tracking",
      "mcp__trackingmore__trackingmore_delete_tracking"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as trackingmore. Review it before you use it.