eCommerce

srsr.ca

Tracks packages and provides unified shipping timelines and operational event audits for e-commerce orders.

2 endpoints27 known toolsFirst detected August 6, 2026Last detected August 6, 2026

ENDPOINT 1

https://srsr.ca/api/mcp

No auth detected

MCP server metadata

Name: superroute
Version: 2.0.0

Capabilities

tools

Server instructions

Superroute logistics operations. Call get_capabilities first: it reports which tools this connection may use, their risk level, and whether confirm=true or human approval is required. Write tools are gated — read the error text, it tells you the next step.

Known tools 3

track_package

Track a package by its tracking number.

Inferred read-only

otep_tracking

Get the unified OTEP (Open Tracking Event Protocol) timeline for a tracking number — self-delivery, third-party and carrier events normalized into one timeline with one status vocabulary.

Inferred read-only

get_capabilities

List MCP tools available to the current connection, with risk level, required scopes, and whether confirm=true is needed.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.superroute]
url = "https://srsr.ca/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "superroute": {
      "type": "http",
      "url": "https://srsr.ca/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: superroute
Remote MCP URL: https://srsr.ca/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "superroute": {
      "url": "https://srsr.ca/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "superroute": {
      "type": "http",
      "url": "https://srsr.ca/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "superroute",
  "transport": "streamable-http",
  "url": "https://srsr.ca/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://srsr.ca/api/mcp/developer

No auth detected

MCP server metadata

Name: superroute-developer
Version: 2.0.0

Capabilities

tools

Server instructions

Superroute integration reference for developers: REST and GraphQL catalog discovery, integration and webhook guides, webhook delivery debugging, and sample API calls. Management agents that need to operate orders and routes should use the User MCP server at /api/mcp instead.

Known tools 24

track_package

Track a package by tracking number.

Inferred read-only

get_operation_events

Get the full audit trail for orders — every status change, who did it, GPS coordinates, photos.

Inferred read-only

get_shipping_methods

List available shipping carriers/methods.

Inferred read-only

get_shipping_rate

Get a shipping cost quote.

Inferred read-only

create_shipping_label

Create a shipping label — books shipment with carrier, generates tracking numbers.

Potential side effects

get_shipping_label

Get shipping label details and download info for an order.

Inferred read-only

create_order

Create a delivery/pickup order.

Potential side effects

build_route

Build a delivery route — assigns orders to drivers and triggers route optimization.

Inferred read-only

get_build_route_options

Get available options for building routes: routing engines with their balance modes, capacity types, related order types, order sources, and default values.

Inferred read-only

get_api_endpoints

Search the complete Superroute REST API catalog (the same OpenAPI spec that powers /api/documentation) instead of guessing endpoint names.

Inferred read-only

get_graphql_operations

Search the Superroute GraphQL catalog — every query and mutation, grouped by category, each with its REST equivalent, arguments and a ready-to-run document.

Inferred read-only

run_graphql_query

Execute a query or mutation against the Superroute GraphQL endpoint (POST /api/graphql) and return the raw JSON-with-errors response.

Potential side effects

get_otep_tracking

Get a package's tracking history as an OTEP (Open Tracking Event Protocol) document — the normalized What/When/Where/Why event model, with each event carrying its OTEP status code and phase.

Inferred read-only

validate_otep_payload

Run an OTEP document or event through the live conformance validator (POST /api/v1/otep/validate) and get back the rule-by-rule verdict from spec §13.

Potential side effects

check_skill_update

Check if a newer version of the Superroute AI integration skill file is available.

Inferred read-only

get_integration_guide

Get the Superroute integration guide with full API reference, business context for parameters, response interpretation, and capability composition patterns.

Inferred read-only

get_otep_guide

Get the OTEP (Open Tracking Event Protocol) development guide — the What/When/Where/Why event model, the 20 status codes and phases, the normative conformance rules (spec §13), how to map a carrier or platform status vocabulary onto OTEP, how to write a projector to a new output format, and how to validate a payload.

Potential side effects

get_webhook_guide

Get the full Superroute webhooks integration guide: the 7-event catalog (order.created, order.status_change, tracking.event, order.create_async, pod.files_updated, order.deleted, order.cancel_failed), payload shapes, both signature schemes (legacy Signature header + timestamped X-Webhook-Signature-V2 / X-Webhook-Timestamp / X-Webhook-Event-Id) with PHP/Node/Python sample code, the opt-in body event envelope, retry policy, delivery logs, and best practices.

Inferred read-only

verify_webhook_signature

Verify whether an incoming webhook signature is valid.

Inferred read-only

test_webhook_delivery

Fire a real, properly-signed test webhook from Superroute servers to a URL the developer provides.

Inferred read-only

get_webhook_settings

Read the caller's own webhook configuration — every per-event callback URL, the behaviour flags, and whether a signing secret is set (the secret itself comes back masked).

Inferred read-only

update_webhook_settings

Self-serve update of the caller's webhook configuration (PUT /api/v1/webhook-settings).

Potential side effects

get_webhook_delivery_logs

List recorded webhook delivery attempts for the caller — event type, target URL, HTTP status, attempt number, response time, response body, and whether it was a test send.

Potential side effects

replay_webhook_delivery

Re-send a webhook that was already logged, by delivery-log id (get the id from get_webhook_delivery_logs).

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.superroute-developer]
url = "https://srsr.ca/api/mcp/developer"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "superroute-developer": {
      "type": "http",
      "url": "https://srsr.ca/api/mcp/developer"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: superroute-developer
Remote MCP URL: https://srsr.ca/api/mcp/developer

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "superroute-developer": {
      "url": "https://srsr.ca/api/mcp/developer"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "superroute-developer": {
      "type": "http",
      "url": "https://srsr.ca/api/mcp/developer"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "superroute-developer",
  "transport": "streamable-http",
  "url": "https://srsr.ca/api/mcp/developer"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for srsr.ca was fetched 2026-08-11T08:34:30.107Z.

Trust status Trusted

srsr.ca is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.