developer-tools

17TRACK Package Tracking

by iamfiro

Track USPS and US mail packages globally with 17TRACK's USPS tracking service—easy carrier ID and real-time delivery sta

Integrates with 17TRACK API to provide global package tracking across multiple carriers with fuzzy search for carrier identification and delivery status monitoring for e-commerce and customer service workflows.

github stars

3

Supports global carriersAutomatic carrier detectionRequires 17TRACK API token

best for

  • / E-commerce businesses tracking customer orders
  • / Customer service teams handling shipping inquiries
  • / Personal package tracking automation
  • / Logistics and fulfillment operations

capabilities

  • / Track packages from multiple carriers worldwide
  • / Auto-detect carrier from tracking number
  • / Monitor delivery status and location updates
  • / Specify carriers manually when needed
  • / Query package history and timeline

what it does

Tracks packages globally across multiple shipping carriers using the 17TRACK API. Automatically detects carriers from tracking numbers and monitors delivery status.

about

17TRACK Package Tracking is a community-built MCP server published by iamfiro that provides AI assistants with tools and capabilities via the Model Context Protocol. Track USPS and US mail packages globally with 17TRACK's USPS tracking service—easy carrier ID and real-time delivery sta It is categorized under developer tools.

how to install

You can install 17TRACK Package Tracking in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

license

MIT

17TRACK Package Tracking is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.

readme

Parcel Tracking MCP Server

A Model Context Protocol (MCP) server for tracking parcel deliveries using the 17track.net API.

Features

  • Track parcel deliveries from various carriers
  • Automatic carrier detection
  • Support for manual carrier specification
  • Built with TypeScript and MCP SDK

Prerequisites

  • Node.js (v16 or higher)
  • npm or yarn
  • 17track.net API token

Installation

Install the package via npm:

npm install -g parcel-tracking-mcp-server

Or install locally:

npm install parcel-tracking-mcp-server

Configuration

Create a config.json file in your working directory with your 17track.net API token:

{
  "apiToken": "your-17track-api-token-here"
}

Note: The server looks for config.json in the current working directory where you run the command.

Getting a 17track.net API Token

  1. Visit 17track.net
  2. Sign up for an account
  3. Navigate to the API section
  4. Generate your API token
  5. Add it to your config.json file

Usage

Running the Server

If installed globally:

parcel-tracking-mcp-server

If installed locally:

npx parcel-tracking-mcp-server

Or if you're using it as a dependency in your project:

node node_modules/parcel-tracking-mcp-server/dist/index.js

MCP Client Configuration

To use this server with MCP clients (like Claude Desktop), add it to your MCP configuration:

{
  "mcpServers": {
    "parcel-tracking": {
      "command": "npx",
      "args": ["parcel-tracking-mcp-server"]
    }
  }
}

Or if installed globally:

{
  "mcpServers": {
    "parcel-tracking": {
      "command": "parcel-tracking-mcp-server"
    }
  }
}

Available Tools

tracking-delivery

Track a parcel delivery by providing a tracking number.

Parameters:

  • number (required): The tracking number of the parcel
  • carrier (optional): The carrier of the parcel (defaults to 'auto' for automatic detection)

Example:

// Track with automatic carrier detection
await trackingDelivery({
  number: "1234567890"
});

// Track with specific carrier
await trackingDelivery({
  number: "1234567890",
  carrier: "ups"
});

Supported Carriers

The server supports automatic carrier detection, but you can also specify carriers manually. Common carriers include:

  • UPS
  • FedEx
  • DHL
  • USPS
  • China Post
  • And many more (check 17track.net documentation for full list)

API Response Format

The server returns tracking information in JSON format, including:

  • Tracking status
  • Delivery progress
  • Timestamps
  • Location updates
  • Carrier information

Error Handling

The server includes comprehensive error handling:

  • API connection errors
  • Invalid tracking numbers
  • Missing configuration
  • Network timeouts

Development

Project Structure

├── index.ts          # Main server implementation
├── config.json       # Configuration file (create this)
├── package.json      # Dependencies and scripts
└── README.md         # This file

Dependencies

  • @modelcontextprotocol/sdk - MCP SDK for building servers
  • zod - Schema validation
  • node-fetch - HTTP requests (if needed for older Node.js versions)

License

MIT License

Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Submit a pull request

Support

For issues related to:

Changelog

v1.0.0

  • Initial release
  • Basic parcel tracking functionality
  • Support for automatic and manual carrier detection
  • Error handling and logging

FAQ

What is the 17TRACK Package Tracking MCP server?
17TRACK Package Tracking is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
How do MCP servers relate to agent skills?
Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
How are reviews shown for 17TRACK Package Tracking?
This profile displays 10 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.
MCP server reviews

Ratings

4.510 reviews
  • Shikha Mishra· Oct 10, 2024

    17TRACK Package Tracking is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.

  • Piyush G· Sep 9, 2024

    We evaluated 17TRACK Package Tracking against two servers with overlapping tools; this profile had the clearer scope statement.

  • Chaitanya Patil· Aug 8, 2024

    Useful MCP listing: 17TRACK Package Tracking is the kind of server we cite when onboarding engineers to host + tool permissions.

  • Sakshi Patil· Jul 7, 2024

    17TRACK Package Tracking reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Ganesh Mohane· Jun 6, 2024

    I recommend 17TRACK Package Tracking for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

  • Oshnikdeep· May 5, 2024

    Strong directory entry: 17TRACK Package Tracking surfaces stars and publisher context so we could sanity-check maintenance before adopting.

  • Dhruvi Jain· Apr 4, 2024

    17TRACK Package Tracking has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Rahul Santra· Mar 3, 2024

    According to our notes, 17TRACK Package Tracking benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.

  • Pratham Ware· Feb 2, 2024

    We wired 17TRACK Package Tracking into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

  • Yash Thakker· Jan 1, 2024

    17TRACK Package Tracking is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.