API & MCP documentation
Multi-carrier package tracking for Muse.
Demo gateway: parcels are stubs — timelines are hashed from the tracking number; no UPS, USPS, FedEx, or DHL API is called. Watch is an in-memory flag, not a carrier notification.
Connecting
- MCP endpoint
https://api.muse.telep.io/mcp/shipsignal— streamable HTTP, JSON-RPC 2.0. Methods:initialize,tools/list,tools/call.- REST base
https://api.muse.telep.io/v1/shipsignal- OpenAPI
https://api.muse.telep.io/v1/shipsignal/openapi.json— exact request/response shapes for every REST route.- Auth
Authorization: Bearer <api-key>on every call. Calls are scoped to the key.
MCP tools
check_credentials
Validate the ShipSignal aggregator key. Does not register a tracking number. Demo mode skips the provider.
Takes no parameters.
track_package
Track a package. Demo mode hashes a timeline and calls no carrier. test/live mode calls AfterShip, Shippo, or EasyPost. Shippo lookups are read-only. AfterShip may register the number and EasyPost may create a tracker. No postage is purchased.
| Parameter | Type | Required | Description |
|---|---|---|---|
trackingNumber | string | yes | — |
origin | string | no | — |
destination | string | no | — |
list_parcels
List ShipSignal stub parcels created with this API key.
Takes no parameters.
refresh_parcel
Refresh a parcel. Demo mode recomputes the hash timeline. test/live mode asks the configured provider again.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | yes | — |
watch_parcel
Mark a stub parcel as watched. No carrier webhooks are registered.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | yes | — |
unwatch_parcel
Stop watching a stub parcel.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | yes | — |
get_account
Stub ShipSignal account for this API key. No real usage is billed.
Takes no parameters.
Example: list tools over MCP
curl -X POST https://api.muse.telep.io/mcp/shipsignal -H "Authorization: Bearer $TELEP_API_KEY" -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" -d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list",
"params": {}
}'REST example
Create via POST https://api.muse.telep.io/v1/shipsignal/parcels:
curl -X POST https://api.muse.telep.io/v1/shipsignal/parcels -H "Authorization: Bearer $TELEP_API_KEY" -H "Content-Type: application/json" -d '{"trackingNumber":"example"}'Every REST route is described exactly in the OpenAPI document.
Demo status
Demo gateway: parcels are stubs — timelines are hashed from the tracking number; no UPS, USPS, FedEx, or DHL API is called. Watch is an in-memory flag, not a carrier notification.
Pricing: See the ShipSignal product for current pricing. Nothing is billed while the gateway is a stub.
Related
- ShipSignal overview — https://muse.telep.io/connectors/shipsignal
- Privacy policy
- Terms of service