Multi Carrier Shipping API — Powered By Secureship

secureship6.1kstars

1# Multi Carrier Shipping API — Powered By Secureship

README.mdMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

Install from the publisher. Not a PlugMCP endpoint.

Run on PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README..

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Last checked: 2026-10-26

Stars: 6.1k
Tools: —
Uptime: —

Overview

About Multi Carrier Shipping API — Powered By Secureship

Secureship MCP gives AI assistants access to a multi-carrier shipping API covering rate comparison, label generation, package tracking, pickup scheduling, address book management, shipment history, customs documents, and more — across carriers like UPS, FedEx, Purolator, Canpar, and others. Browse 150+ live endpoint schemas, parameters, and auth details — always current, never stale. Secureship isn't just for shipping with one carrier — it's a multi-carrier shipping platform, and this MCP server gives AI assistants full access to the API documentation for every supported action: compare rates across carriers, generate shipping labels, track packages, schedule pickups, manage address books, review shipment history, produce customs documents, handle invoices, and even perform actions available on the Secureship web dashboard — all through a single API. The MCP documentation server exposes live endpoint metadata pulled directly from the running application — not static docs that go stale. That means AI assistants always get the correct paths, parameters, request bodies, response schemas, and authentication requirements for 150+ endpoints. Read-only, public, no API key needed to browse. Authentication for the actual shipping API uses a simple X-API-KEY header. **Tools exposed:** - SearchDocs — keyword search across all API endpoints - GetEndpointDetail — full schema for a specific endpoint (params, request body, responses, auth) - ListEndpoints — list all endpoints, optionally filtered by category - GetAuthInfo — authentication instructions (X-API-KEY header) **Categories:** Shipping, logistics, e-commerce, carriers, rates, labels, tracking, address book, customs documents, shipment history

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Multi Carrier Shipping API — Powered By Secureship?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Multi Carrier Shipping API — Powered By Secureship need an API key?

No required environment variable is listed on this record.

What transport does Multi Carrier Shipping API — Powered By Secureship use?

Multi Carrier Shipping API — Powered By Secureship runs locally over stdio.

When was Multi Carrier Shipping API — Powered By Secureship last checked?

Last checked 2026-10-26. Secureship MCP gives AI assistants access to a multi-carrier shipping API covering rate comparison, label generation, package tracking, pickup scheduling, address book management, shipment history, customs documents, and more — across carriers like UPS, FedEx, Purolator, Canpar, and others. Browse 150+ live endpoint schemas, parameters, and auth details — always current, never stale. Secureship isn't just for shipping with one carrier — it's a multi-carrier shipping platform, and this MCP server gives AI assistants full access to the API documentation for every supported action: compare rates across carriers, generate shipping labels, track packages, schedule pickups, manage address books, review shipment history, produce customs documents, handle invoices, and even perform actions available on the Secureship web dashboard — all through a single API. The MCP documentation server exposes live endpoint metadata pulled directly from the running application — not static docs that go stale. That means AI assistants always get the correct paths, parameters, request bodies, response schemas, and authentication requirements for 150+ endpoints. Read-only, public, no API key needed to browse. Authentication for the actual shipping API uses a simple X-API-KEY header. **Tools exposed:** - SearchDocs — keyword search across all API endpoints - GetEndpointDetail — full schema for a specific endpoint (params, request body, responses, auth) - ListEndpoints — list all endpoints, optionally filtered by category - GetAuthInfo — authentication instructions (X-API-KEY header) **Categories:** Shipping, logistics, e-commerce, carriers, rates, labels, tracking, address book, customs documents, shipment history

From the publisher

Documentation

README is not crawled yet. No repository on file.