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
How to connect
Same URL, five paste targets. Ready surface · Auth required. Not a safe-to-install badge. Handshake this URL
Paste into Settings → MCP or .cursor/mcp.json.
{
"mcpServers": {
"secureship-docs": {
"url": "https://docs--secureship.run.tools"
}
}
}
Paste into .vscode/mcp.json.
{
"mcpServers": {
"secureship-docs": {
"url": "https://docs--secureship.run.tools"
}
}
}
Settings → Connectors → Add → Custom → Web. Paste the URL. Enable in a new chat.
Claude → Settings → Connectors → Add → Custom → Web
Name: Multi-Carrier Shipping API — powered by Secureship
URL: https://docs--secureship.run.tools
OAuth only if this server requires it.
Save, start a new chat, enable the connector.
Developer mode custom connector. ChatGPT cannot reach localhost.
Settings → Apps & Connectors → Advanced → Developer mode ON
Create custom connector
Name: Multi-Carrier Shipping API — powered by Secureship
MCP server URL: https://docs--secureship.run.tools
Auth: none unless the server requires OAuth
New chat → + → Developer mode → enable the connector
Register the HTTPS URL, then claude mcp list.
claude mcp add --transport http secureship-docs \
https://docs--secureship.run.tools
Pass on session/new as mcpServers when the agent advertised HTTP MCP.
[
{
"type": "http",
"name": "secureship-docs",
"url": "https://docs--secureship.run.tools"
}
]
Paste into a README or docs site. The widget loads snippets from Influzer — still not a SAFE badge.
Same handshake clock as this listing (overlay / warm / seed; live tools/list only if that is missing). Indigo is live_ok, amber is auth_required, gray is unreachable. Not a SAFE badge. Stdio listings have no badge.
[](https://www.influzer.ai/mcp/probe?url=https%3A%2F%2Fdocs--secureship.run.tools)
<div data-influzer-install="secureship-docs"></div>
<script async src="https://www.influzer.ai/embed/install.js"></script>
https://www.influzer.ai/embed/mcp/secureship-docs.md
JSON: https://www.influzer.ai/api/v1/install/secureship-docs
Recipes using this server
No published recipes yet for this server.
Listing quality
Observable facts from our catalog and daily probe — not a safe-to-install badge.
- Surface
- Ready surface
- Auth gate
- Auth gate
- Tools source
- tools/list (live)
Observable catalog + probe facts — not a safe-to-install badge. How we verify.
Verification summary
Stored signals only. Not a safety score.
- Verification grade
- B (75)
- Last verified
- Status
- Auth required
- Response time
- 0 ms
- Auth
- Auth gate
- Transport
- http, HTTPS
- Tools indexed
- 4
- 30-day uptime
- 100% of 6 samples over 6 days
Probe history
- · auth_required · 0 ms
- · auth_required · 0 ms
- · auth_required · 0 ms
- · auth_required · 0 ms
- · auth_required · 0 ms
Tools
(4)-
get_endpoint_detailGet the full schema for a specific Secureship API endpoint — all parameters, request body fields, response format, and authentication requirements. Use after SearchDocs identifies the right endpoint. Authentication uses the X-API-KEY header.
-
get_auth_infoGet Secureship API authentication instructions. Call this FIRST before generating any code examples with authentication headers. Secureship uses X-API-KEY header authentication, NOT Bearer tokens.
-
search_docsSearch Secureship API documentation. Use when you need to find endpoints for a specific task (e.g. 'create a shipment', 'get rates', 'address book'). Returns matching endpoints with method, path, summary, and tags. Follow up with GetEndpointDetail to get full parameter schemas. IMPORTANT: Secureship API uses the X-API-KEY header for authentication (NOT Bearer token). Pass your API key as: X-API-KEY: your-api-key
-
list_endpointsList all Secureship API endpoints, optionally filtered by category. Categories include: carriers, shipment, history, address-book, auth, account, users, invoices, pickups, documents, integrations, settings, dashboard. Use for discovery when you don't know which endpoint to search for.
Tool source: tools/list (live) · last probed 2026-11-04