17TRACK MCP by usefulapi
REMOTE · 17TRACK.USEFULAPI.IO
Track parcels across 3000+ carriers with 17TRACK: register numbers, read tracking events and quota.
Available components
Last scanned (23 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 16 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 Usability78
- 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 1309 tokens (~145/item across 9 items; 9 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +2
- 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 59
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 16 Oct 2026 · Probed https://17track.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 17track.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://17track.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://17track.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://17track.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://17track.usefulapi.io/mcp |
| Authorisation server | https://17track.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://17track.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/17track/ |
| http (plaintext) | http://17track.usefulapi.io/mcp | Inconclusive | 302 | http://17track.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 →
track17_change_carrier Change the carrier of a number ~83
WRITE: assign a different carrier to registered tracking numbers (up to 10 per call), for example when auto-detection picked the wrong one. A number can change carrier at most 5 times, and a successful change can be charged as one shipment (see track17_get_quota). POST /changecarrier.
| Name | Type | Req | Description |
|---|---|---|---|
| changes | array | yes | – |
No output schema declared.
No examples provided.
track17_change_tag Change the tag of a number ~104
WRITE: set the tag (your own label, max 100 characters) of a registered tracking number. It replaces the old tag. Free. POST /changeinfo.
| Name | Type | Req | Description |
|---|---|---|---|
| carrier | integer | – | Carrier code; needed if the number is tracked under several carriers. |
| number | string | yes | Tracking number (5-50 letters, digits or hyphens). |
| tag | string | yes | The new tag (max 100 characters; an empty string clears it). |
No output schema declared.
No examples provided.
track17_get_quota Get tracking quota ~57
The account's tracking quota: total, used, remaining, used today, the daily registration limit (0 = no limit) and the free e-mail quota. Each registered tracking number uses 1 quota. POST /getquota.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
track17_get_tracking Get tracking details ~118
Full tracking details (status, sub-status, milestones, every carrier event with time and location, estimated delivery) for up to 10 numbers that are ALREADY registered on this account. Free: it does not use quota. A number that is not registered comes back in `rejected` — register it first with track17_register_numbers, or use track17_realtime_lookup. POST /gettrackinfo.
| Name | Type | Req | Description |
|---|---|---|---|
| numbers | array | yes | Registered numbers, each with an optional carrier code (needed if the number is tracked under several carriers). |
No output schema declared.
No examples provided.
track17_list_tracking_numbers List registered tracking numbers ~254
Search the tracking numbers registered on this account (40 per page) with their carrier, status, registration and last-update times, and latest event. Filter by number(s), carrier, tracking state, package status or registration date. Free: it does not use quota. POST /gettracklist.
| Name | Type | Req | Description |
|---|---|---|---|
| carrier | integer | – | 17TRACK numeric carrier code (for example 3011 = China Post, 100003 = FedEx). Full list: https://res.17track.net/asset/carrier/info/apicarrier.all.json |
| data_origin | string | – | How the number was added. |
| numbers | array | – | Only these tracking numbers (up to 200). |
| order_by | string | – | Sort order. |
| package_status | string | – | Only packages in this main status. |
| page_no | integer | – | Page number, from 1 (omit for the first page). Use the reply's next_page. |
| register_time_from | string | – | Registered on or after this date (yyyy-mm-dd). |
| register_time_to | string | – | Registered on or before this date (yyyy-mm-dd). |
| tracking_status | string | – | Only numbers currently being tracked, or stopped. |
No output schema declared.
No examples provided.
track17_realtime_lookup Real-time lookup of one number ~239
WRITE (uses quota): look up ONE tracking number directly at the carrier right now, without registering it. Costs 1 quota per call (standard: carrier data up to 3 hours old). If the number is already registered, a changed result is also pushed to the account. Not supported for USPS, Royal Mail, Australia Post, Direct Freight Express, DHL eCommerce US and DHL Global Forwarding; some accounts are not enabled for real-time lookups. POST /getRealTimeTrackInfo.
| Name | Type | Req | Description |
|---|---|---|---|
| carrier | integer | – | 17TRACK numeric carrier code (for example 3011 = China Post, 100003 = FedEx). Full list: https://res.17track.net/asset/carrier/info/apicarrier.all.json |
| destination_postal_code | string | – | Recipient postal code, for carriers that require it. |
| number | string | yes | Tracking number (5-50 letters, digits or hyphens). |
| phone_number_last_4 | string | – | Last 4 digits of the recipient phone, for carriers that require it. |
| ship_date | string | – | A date, yyyy-mm-dd. |
No output schema declared.
No examples provided.
track17_register_numbers Register tracking numbers ~121
WRITE (uses quota): start tracking up to 10 tracking numbers per call. Each ACCEPTED number costs 1 quota from this account (see track17_get_quota); rejected numbers cost nothing. Deleting and re-registering a number costs again. 17TRACK then updates the status itself every 6-12 hours; read it with track17_get_tracking. The carrier is detected automatically unless a carrier code is given. No e-mail notifications are enabled. POST /register.
| Name | Type | Req | Description |
|---|---|---|---|
| numbers | array | yes | 1-10 numbers to register. |
No output schema declared.
No examples provided.
track17_retrack Restart tracking of stopped numbers ~56
WRITE: restart tracking of stopped numbers (up to 10 per call). Each number can be restarted only ONCE in its lifetime, so a second restart is rejected. POST /retrack.
| Name | Type | Req | Description |
|---|---|---|---|
| numbers | array | yes | – |
No output schema declared.
No examples provided.
track17_stop_tracking Stop tracking numbers ~69
WRITE: stop tracking registered numbers (up to 10 per call). The numbers stay in the account for 90 days with their history and can be restarted ONCE each with track17_retrack. Stopping does not refund quota. POST /stoptrack.
| Name | Type | Req | Description |
|---|---|---|---|
| numbers | array | yes | – |
No output schema declared.
No examples provided.
How do I install the 17TRACK MCP by usefulapi server?
17TRACK MCP by usefulapi is a hosted endpoint at https://17track.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 · 17track.usefulapi.io
claude mcp add --transport http io-usefulapi-17track 'https://17track.usefulapi.io/mcp'
What is the 17TRACK MCP by usefulapi server?
17TRACK MCP by usefulapi is listed in the public MCP registry as io.usefulapi/17track. Track parcels across 3000+ carriers with 17TRACK: register numbers, read tracking events and quota. This page covers its hosted endpoint (https://17track.usefulapi.io/mcp).
Is the 17TRACK MCP by usefulapi server safe to use?
17TRACK 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 17TRACK MCP by usefulapi server expose?
17TRACK MCP by usefulapi exposes 9 tools: track17_get_quota, track17_list_tracking_numbers, track17_get_tracking, track17_realtime_lookup, track17_register_numbers, and 4 more. Their descriptions and schemas cost roughly 1,101 tokens of context every time the server is loaded.
Does the 17TRACK MCP by usefulapi server require authentication?
Yes. 17TRACK 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 17TRACK MCP by usefulapi server still maintained?
17TRACK MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.