# 17TRACK MCP by usefulapi (remote · 17track.usefulapi.io)

Track parcels across 3000+ carriers with 17TRACK: register numbers, read tracking events and quota.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `17track.usefulapi.io`: 64/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-17track/17track.md), [page](https://verifymcp.io/servers/io-usefulapi-17track/17track)

## Channel facts

- Endpoint: `https://17track.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add --transport http io-usefulapi-17track 'https://17track.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-17track": {
      "url": "https://17track.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-17track": {
      "type": "http",
      "url": "https://17track.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-17track]
url = "https://17track.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-17track": {
      "type": "remote",
      "url": "https://17track.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-17track --url 'https://17track.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-17track:
    url: "https://17track.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-17track": {
      "Transport": "http",
      "Url": "https://17track.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-17track -t streamable-http -u 'https://17track.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-17track": {
      "type": "http",
      "url": "https://17track.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 63, +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.

### 2026-10-14 (score 62, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] 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

### 2026-10-13 (score 60, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 59)

First indexed and scored.

## MCP tools (9)

### `track17_get_quota` (~57 tokens)

Get tracking quota

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.

### `track17_list_tracking_numbers` (~254 tokens)

List registered tracking numbers

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.

Input parameters:

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

### `track17_get_tracking` (~118 tokens)

Get tracking details

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.

Input parameters:

- `numbers` (array, required): Registered numbers, each with an optional carrier code (needed if the number is tracked under several carriers).

### `track17_realtime_lookup` (~239 tokens)

Real-time lookup of one number

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.

Input parameters:

- `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, required): 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.

### `track17_register_numbers` (~121 tokens)

Register tracking numbers

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.

Input parameters:

- `numbers` (array, required): 1-10 numbers to register.

### `track17_change_carrier` (~83 tokens)

Change the carrier of a number

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.

Input parameters:

- `changes` (array, required)

### `track17_change_tag` (~104 tokens)

Change the tag of a number

WRITE: set the tag (your own label, max 100 characters) of a registered tracking number. It replaces the old tag. Free. POST /changeinfo.

Input parameters:

- `carrier` (integer): Carrier code; needed if the number is tracked under several carriers.
- `number` (string, required): Tracking number (5-50 letters, digits or hyphens).
- `tag` (string, required): The new tag (max 100 characters; an empty string clears it).

### `track17_stop_tracking` (~69 tokens)

Stop tracking numbers

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.

Input parameters:

- `numbers` (array, required)

### `track17_retrack` (~56 tokens)

Restart tracking of stopped numbers

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.

Input parameters:

- `numbers` (array, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-17track/17track#diagnostics

## Score history

- 2026-10-17: 64
- 2026-10-16: 63
- 2026-10-15: 63
- 2026-10-14: 62
- 2026-10-13: 60
- 2026-10-12: 59

## Common questions

### 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 64 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 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://17track.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/17track/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-17track/17track.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-17track/17track.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-17track/17track