Usps Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 26, 2026

USPS shipping, tracking, address validation, and label creation.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Local MCP server that connects an assistant to the USPS API for shipping, package tracking, address validation and label creation.

What you can do
  • Track shipments and look up delivery status through the USPS API
  • Validate and standardize USPS addresses
  • Create shipping labels and handle shipping-related requests
  • Use a configurable USPS API base URL, defaulting to the official endpoint
When to use it
Useful when an assistant needs to check USPS package status, clean up or verify US addresses, or prepare shipping labels without leaving the chat.
Requirements
Runs as a local stdio process installed from the npm package usps-mcp, so Node.js is needed. Requires USPS API credentials: USPS_API_KEY, plus USPS_USERNAME and USPS_PASSWORD for basic auth. USPS_API_URL is optional and defaults to the official USPS API endpoint. Network access to USPS is required.
Before you install
The server needs USPS account credentials, including the secrets USPS_API_KEY and USPS_PASSWORD, which are passed as environment variables; keep them out of shared configs. Label creation and other shipping actions may incur real postage charges and create records with USPS, so review actions before they run. Address and shipment details are sent to the USPS API.

Installation

In SourceWeft

  1. Open Usps Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestOct 17, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.