Server Details
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.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
4 toolsGetAuthInfoInspect
Get 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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
GetEndpointDetailInspect
Get 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.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Endpoint path, e.g. /v1/shipment/in-progress or /v1/carriers/rates | |
| method | Yes | HTTP method: GET, POST, PUT, PATCH, or DELETE |
ListEndpointsInspect
List 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.
| Name | Required | Description | Default |
|---|---|---|---|
| category | Yes | Optional category filter, e.g. 'carriers' or 'address-book'. Omit to list all endpoints. |
SearchDocsInspect
Search 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
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Natural language or keyword query, e.g. 'create label', 'track package', 'address book' |
Verify Ownership
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.
Last verification attempt failed.
Sign in to verify ownershipControl your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!