TrackingMore MCP by usefulapi
REMOTE · TRACKINGMORE.USEFULAPI.IO
Track parcels with TrackingMore: detect couriers, create and read trackings, delivery status.
Available components
Last scanned (7 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
Category E-commerce
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2383 tokens (~340/item across 7 items; 7 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.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 8 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
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.0.0 → 1.1.0 functional
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 58
First indexed and scored.
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 17 Oct 2026 · Probed https://trackingmore.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 trackingmore.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 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://trackingmore.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://trackingmore.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://trackingmore.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://trackingmore.usefulapi.io/mcp |
| Authorisation server | https://trackingmore.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://trackingmore.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/trackingmore/ |
| http (plaintext) | http://trackingmore.usefulapi.io/mcp | Inconclusive | 302 | http://trackingmore.usefulapi.io/mcp |
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 →
trackingmore_create_tracking Register a shipment for tracking ~552
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.
| Name | Type | Req | Description |
|---|---|---|---|
| courier_code | string | yes | TrackingMore courier code, e.g. usps, ups, dhl (see trackingmore_list_couriers / trackingmore_detect_courier). |
| customer_email | string | – | Recipient email (TrackingMore can send delivery notifications to it when enabled in the account). |
| customer_name | string | – | Recipient name. |
| customer_sms | string | – | Recipient mobile number, with country code. |
| destination_country_iso2 | string | – | Destination country, ISO 3166 alpha-2. |
| label | string | – | Label to group shipments. It must be a label you created in the TrackingMore dashboard first, otherwise TrackingMore refuses it (meta 4131). |
| language | string | – | Language code for status text, e.g. en. |
| logistics_channel | string | – | Logistics channel / service name. |
| note | string | – | Free-text note. |
| order_date | string | – | Order date, e.g. 2026-10-01T10:00:00+00:00. |
| order_id | string | – | Your order id in the shop system. |
| order_number | string | – | Your order number for this shipment. |
| origin_country_iso2 | string | – | Origin country, ISO 3166 alpha-2. |
| recipient_postcode | string | – | Recipient postcode. |
| title | string | – | Short title for the shipment. |
| tracking_courier_account | string | – | Courier account (needed by some couriers). |
| tracking_destination_country | string | – | Destination country for couriers that need it, ISO 3166 alpha-2. |
| tracking_key | string | – | Tracking key / phone suffix (needed by some couriers). |
| tracking_number | string | yes | The shipment's tracking number. |
| tracking_origin_country | string | – | Origin country for couriers that need it, ISO 3166 alpha-2. |
| tracking_postal_code | string | – | Recipient postal code (needed by some couriers). |
| tracking_ship_date | string | – | Ship date, yyyymmdd (needed by some couriers). |
No output schema declared.
No examples provided.
trackingmore_delete_tracking Delete a tracking ~87
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | TrackingMore tracking id (the `id` field of a tracking from trackingmore_list_trackings or trackingmore_create_tracking). |
No output schema declared.
No examples provided.
trackingmore_detect_courier Detect courier from a tracking number ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tracking_number | string | yes | The shipment's tracking number. |
No output schema declared.
No examples provided.
trackingmore_get_tracking Get a shipment's tracking ~159
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=.
| Name | Type | Req | Description |
|---|---|---|---|
| courier_code | string | – | TrackingMore courier code, e.g. usps, ups, dhl (see trackingmore_list_couriers / trackingmore_detect_courier). |
| lang | string | – | Language for status text, e.g. en. |
| tracking_number | string | yes | The shipment's tracking number. |
No output schema declared.
No examples provided.
trackingmore_list_couriers List supported couriers ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Courier country, ISO 3166 alpha-2, e.g. US. |
| limit | integer | – | Most couriers returned, 1-200 (default 50). |
| offset | integer | – | Skip this many matches (paging; default 0). |
| search | string | – | Case-insensitive text in the courier name or code, e.g. 'dhl'. |
No output schema declared.
No examples provided.
trackingmore_list_trackings List trackings ~661
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.
| Name | Type | Req | Description |
|---|---|---|---|
| archived_status | string | – | Archive filter: true = archived trackings, tracking = trackings that are not archived. |
| courier_code | string | – | TrackingMore courier code, e.g. usps, ups, dhl (see trackingmore_list_couriers / trackingmore_detect_courier). |
| created_date_max | string | – | A date (yyyy-mm-dd, taken as 00:00:00 UTC) or an ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00+00:00 or 2026-10-01T00:00:00Z. Sent to TrackingMore as YYYY-MM-DDTHH:MM:SS+HH:MM. |
| created_date_min | string | – | A date (yyyy-mm-dd, taken as 00:00:00 UTC) or an ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00+00:00 or 2026-10-01T00:00:00Z. Sent to TrackingMore as YYYY-MM-DDTHH:MM:SS+HH:MM. |
| delivery_status | string | – | pending, notfound, transit, pickup, delivered, undelivered, exception, expired or inforeceived. |
| lang | string | – | Language for status text, e.g. en. |
| limit | integer | – | Trackings per page, 1-200 (default 40). Sent as items_amount. |
| page | integer | – | Page number, from 1 (default 1). Sent as pages_amount. |
| tracking_numbers | string | – | One to 40 tracking numbers, comma-separated (TrackingMore refuses more than 40 per call). |
| updated_date_max | string | – | A date (yyyy-mm-dd, taken as 00:00:00 UTC) or an ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00+00:00 or 2026-10-01T00:00:00Z. Sent to TrackingMore as YYYY-MM-DDTHH:MM:SS+HH:MM. |
| updated_date_min | string | – | A date (yyyy-mm-dd, taken as 00:00:00 UTC) or an ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00+00:00 or 2026-10-01T00:00:00Z. Sent to TrackingMore as YYYY-MM-DDTHH:MM:SS+HH:MM. |
No output schema declared.
No examples provided.
trackingmore_update_tracking Update a tracking's details ~476
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_email | string | – | Recipient email (TrackingMore can send delivery notifications to it when enabled in the account). |
| customer_name | string | – | Recipient name. |
| customer_sms | string | – | Recipient mobile number, with country code. |
| destination_country_iso2 | string | – | Destination country, ISO 3166 alpha-2. |
| id | string | yes | TrackingMore tracking id (the `id` field of a tracking from trackingmore_list_trackings or trackingmore_create_tracking). |
| label | string | – | Label to group shipments. It must be a label you created in the TrackingMore dashboard first, otherwise TrackingMore refuses it (meta 4131). |
| language | string | – | Language code for status text, e.g. en. |
| logistics_channel | string | – | Logistics channel / service name. |
| note | string | – | Free-text note. |
| order_date | string | – | Order date, e.g. 2026-10-01T10:00:00+00:00. |
| order_id | string | – | Your order id in the shop system. |
| order_number | string | – | Your order number for this shipment. |
| origin_country_iso2 | string | – | Origin country, ISO 3166 alpha-2. |
| recipient_postcode | string | – | Recipient postcode. |
| title | string | – | Short title for the shipment. |
| tracking_courier_account | string | – | Courier account (needed by some couriers). |
| tracking_destination_country | string | – | Destination country for couriers that need it, ISO 3166 alpha-2. |
| tracking_key | string | – | Tracking key / phone suffix (needed by some couriers). |
| tracking_origin_country | string | – | Origin country for couriers that need it, ISO 3166 alpha-2. |
| tracking_postal_code | string | – | Recipient postal code (needed by some couriers). |
| tracking_ship_date | string | – | Ship date, yyyymmdd (needed by some couriers). |
No output schema declared.
No examples provided.
How do I install the TrackingMore MCP by usefulapi server?
TrackingMore MCP by usefulapi is a hosted endpoint at https://trackingmore.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 · trackingmore.usefulapi.io
claude mcp add --transport http io-usefulapi-trackingmore 'https://trackingmore.usefulapi.io/mcp'
What is the TrackingMore MCP by usefulapi server?
TrackingMore MCP by usefulapi is listed in the public MCP registry as io.usefulapi/trackingmore. Track parcels with TrackingMore: detect couriers, create and read trackings, delivery status. This page covers its hosted endpoint (https://trackingmore.usefulapi.io/mcp).
Is the TrackingMore MCP by usefulapi server safe to use?
TrackingMore MCP by usefulapi scores 63 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 TrackingMore MCP by usefulapi server expose?
TrackingMore MCP by usefulapi exposes 7 tools: trackingmore_list_couriers, trackingmore_detect_courier, trackingmore_list_trackings, trackingmore_get_tracking, trackingmore_create_tracking, and 2 more. Their descriptions and schemas cost roughly 2,166 tokens of context every time the server is loaded.
Does the TrackingMore MCP by usefulapi server require authentication?
Yes. TrackingMore 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 TrackingMore MCP by usefulapi server still maintained?
TrackingMore MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.