17TRACK MCP server

Track parcels across 3000+ carriers with 17TRACK: register numbers, read tracking events and quota. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.

Claude claude.ai · Desktop

  1. Open Customize → Connectors, then click + Add → Add custom connector.
  2. Enter the name 17TRACK and this URL, then click Add:
    https://17track.usefulapi.io/mcp
  3. Claude opens the login page: enter your 17TRACK Security Key.
  4. In a chat, click + → Connectors and turn on 17TRACK.

Team and Enterprise: an Owner adds the connector for the organization first.

Claude Code

Run this command, then run /mcp in Claude Code to log in:

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

Cursor

Add to Cursor or add this to ~/.cursor/mcp.json:

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

VS Code

Add to VS Code or add this to .vscode/mcp.json:

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

Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.

live13 toolsFree 100 tool calls / monthPro $9/mo · $90/yr

Before you connect

The login page asks for your 17TRACK Security Key.

Find it in the 17TRACK API dashboard under Settings → Security Key. Registering a number uses your own tracking quota. Do not enable an IP whitelist for this key: this hosted server has no fixed IP address. Your key is used only to call the 17TRACK API on your behalf; it is never shown to anyone.

Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your 17TRACK Security Key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.

Tools 13

ToolTypeWhat it does
track17_get_quotaread
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_numbersread
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.
track17_get_trackingread
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.
track17_realtime_lookupwrite
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.
track17_register_numberswrite
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.
track17_change_carrierwrite
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.
track17_change_tagwrite
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.
track17_stop_trackingwrite
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.
track17_retrackwrite
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.
track17_usage_statusmeta
Usage status (free-tier meter)
Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter.
track17_request_featuremeta
Request a missing feature
Tell usefulapi that the user needs something the 17TRACK tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter.
track17_upgrademeta
Upgrade to Pro (unlimited)
Subscribe to the Pro plan for UNLIMITED 17TRACK tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter.
track17_cancel_subscriptionmeta
Cancel the Pro subscription
Cancel the caller's 17TRACK Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run track17_upgrade later to undo the cancel before the period ends. Does not count against the meter.

Pricing

PlanPriceLimit
Free$0100 tool calls / month
Proper user$9/mo · $90/yrUnlimited

Pro covers this 17TRACK server only. Subscribe with track17_upgrade (it returns a Stripe Checkout link). Cancel any time with track17_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running track17_upgrade before then undoes the cancel. Or write to [email protected].

FAQ

Is this an official 17TRACK product?

No. usefulapi is an independent service. It is not affiliated with or endorsed by 17TRACK. The server calls the 17TRACK API with your own 17TRACK access, so it sees only the data that your account can see.

What do I need to connect?

The login page asks for your 17TRACK Security Key. See Before you connect for where to find it.

Do I put my 17TRACK key or an Authorization header in the client config?

No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your 17TRACK Security Key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.

How do you keep my 17TRACK credentials?

The login stores them encrypted in the authorization grant of your connection. The server uses them to call the 17TRACK API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in 17TRACK.

Can the AI change my 17TRACK data?

Yes, if you approve it. 6 of the 9 17TRACK tools can create or change data. The other 3 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.

What does it cost?

The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this 17TRACK server only. Run track17_usage_status to see how many calls you used.

How do I subscribe or cancel?

Ask the AI to run track17_upgrade: it returns a Stripe Checkout link. To cancel, run track17_cancel_subscription. Pro continues to the end of the paid period.

What if a 17TRACK tool that I need is missing?

Tell the AI what you wanted to do. It can send the request with track17_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.

Which AI clients can I use?

Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.

This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.

More Documents & Delivery MCP servers

AnvilApi2PdfDocRaptorDocumensoDropbox SignDrupalEasyPostGitBookKnowledgeOwlLobOptimoRouteOrdoroShipdaySpoke DispatchStarshipitTookanTrack-PODTrackingMore

All Documents & Delivery servers →