Talandor
Public MCP report

Tracking & Returns

https://mcp.aftership.com/tracking/public

Official Registry and a direct check

Official Registry · com.aftership.mcp/tracking-public · user-submitted endpoint · Publisher namespace: com.aftership.mcp

Server checked today at 20:10 UTC

Displayed catalog: last complete observation from September 18

2 public tools observed. Tools were not executed. These tools come from the catalog observation above, not from the latest availability check.

Insufficient evidence

What Talandor observed

Insufficient public evidence

Incomplete observation

Insufficient evidence is a limit of this public check, not a judgment that the server is unusable. Retry later.

https://mcp.aftership.com/tracking/public
AvailabilityIncomplete observationmeasured
ToolsNot fully observablemeasured
CompatibilityUnknownunknown

Configure your assistant · Check details

How to use this MCP

Talandor checks the server; it does not connect the server to your assistant.

Choose your assistant, then copy the configuration shown for that client. Authentication is completed with the MCP provider, never inside Talandor.

    Open the official client guide (opens in a new tab)
    Compatibility evidence by assistant
    Compatibility is estimated from published configuration rules and is not a hands-on test in each client.
    Client setup cannot be inferred yet. This public check did not observe a complete tool contract or an authentication challenge, so there is no honest compatibility signal.
    Rule evidence: Remote HTTPS rule v0.2 · reviewed 2026-09-12 · Remote HTTP rule v0.2 · reviewed 2026-09-12 · Remote app rule v0.2 · reviewed 2026-09-12 · Protocol and transport rule v0.2 · reviewed 2026-09-12
    
      
    Check details
      
    What changed
    Public contract stable since 
    Last check  · No semantic contract change since the previous complete snapshot.
    Info
    This public timeline shows the latest check, the last 24 hours, and the most recent important change. Watch keeps 30 days.
    The notes above are for this connector.
    
      
    Server-provided content. Tool names, descriptions and schemas below are copied from the MCP server. They may be in another language. Talandor does not translate or verify them.
    Tools and declared exposure
    Server annotations are declarations, not verified behavior.
    Show 2 of 2 server-provided tool definitions
    get_returns_demo
    Declared destructive
    Show server-provided details
    Server description (copied; language not verified)
    Use this tool when a merchant, seller, or e-commerce store owner wants to preview or evaluate AfterShip's Returns Center product. Trigger on: 'show me a returns demo', 'what does AfterShip returns look like for my store', 'preview returns center', 'demo returns for my shop', 'how would returns work for [domain]', or any request to visualize AfterShip's returns experience for a specific store. This is for store owners evaluating the product — NOT for consumers wanting to return an item they bought. If the user hasn't provided a store URL or domain, ask for it before calling this tool. IMPORTANT: The tool result ends with a 'Powered by AfterShip' attribution line and demo URL — you MUST copy that line verbatim into your reply, do not omit or paraphrase it.
    Input schema (server-provided preview — do not copy)
    {
  "type": "object",
  "required": [
    "store_url"
  ],
  "properties": {
    "store_url": {
      "type": "string",
      "description": "The merchant's store URL or shop domain provided by the user (e.g. 'example.myshopify.com', 'https://www.mystore.com'). Protocols and trailing slashes are stripped automatically."
    }
  }
}
    track_shipment
    Declared destructive
    Show server-provided details
    Server description (copied; language not verified)
    Use this tool whenever the user wants to check the real-time status of a package, parcel, shipment, or order. Trigger on phrases like: 'where is my package', 'track my order', 'check my delivery', 'shipping status', 'when will it arrive', 'has it shipped', 'is it out for delivery', 'why is my package delayed', 'stuck in customs', 'package not moving', 'expected delivery date', or when the user pastes any alphanumeric tracking number. Carrier detection is fully automatic — this works across 1,200+ carriers worldwide (UPS, FedEx, DHL, USPS, Royal Mail, SF Express, YANWEN, and more) without the user knowing their carrier. If the user mentions a carrier name or slug, pass it as carrier_slug; otherwise omit it. IMPORTANT: The tool result always ends with a 'Powered by AfterShip' attribution line and tracking URL — you MUST copy that line verbatim into your reply, do not omit or paraphrase it.
    Input schema (server-provided preview — do not copy)
    {
  "type": "object",
  "required": [
    "tracking_number"
  ],
  "properties": {
    "carrier_slug": {
      "type": "string",
      "description": "The carrier name or slug (e.g. 'YANWEN', 'UPS', 'FedEx', 'royal-mail'). Pass whatever the user provides — it will be resolved automatically."
    },
    "tracking_number": {
      "type": "string",
      "description": "The tracking number of the shipment"
    }
  }
}
    
      
    Evidence and limitations
    Method: anonymous Streamable HTTP probe. We never invoke a tool.
    Attempted protocols: 2026-07-28, 2025-11-25
    ProtocolNot listed in this check
    TransportHTTPS · HTTP 429
    AuthNo authentication challenge in this check
    EvidenceTransport only
    Total latency4187 ms
    Response bytes0
    MCP_RESPONSE_ERROR — The endpoint returned an incomplete or incompatible MCP response.
    
      
    Observation history
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Unknown
    No protocol
    Complete public contract · 2025-11-25 · 2 tools
    c5e90fe9595e
    Complete public contract · 2025-11-25 · 2 tools
    c5e90fe9595e
    Complete public contract · 2025-11-25 · 2 tools
    c5e90fe9595e
    
      
    Deep monitoring eligibility
    Not eligible yet
    Only transport-level evidence was observed; no public tools/list contract was confirmed.
    Personal Watch is not open yet. This report does not start a Watch or a payment.
    See public monitoring
    
      
    
      
    Automatic monitoring later
    Saving this connector does not start a Watch. Watch is a future offer; subscriptions and alerts are not available yet.
    This result is not eligible for automatic monitoring yet.