Talandor
Public MCP report

Tracking & Returns

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

Both

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

Last observed

Insufficient evidence
Can I use it?

Insufficient public evidence

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
Tools2
AuthNot listed in this check
ProtocolNot listed in this check
EvidenceTransport only
Latency1545 ms

See the measured evidence

Client fit

Compatibility is inferred from published configuration rules and is not manually verified 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.

Show compatibility evidence

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

What changed

Public contract is no longer observable since
· A complete public contract was observed earlier. The latest check did not re-observe it. This is a limit of evidence, not a quality judgment.
Warning

A Watch would follow availability and the last known public contract, and alert only if a change may affect the selected client.

Show 2 quieter observations
Public contract stable since
Last compared · No semantic contract change since the previous complete snapshot.
Info
Public contract stable since
Last compared · No semantic contract change since the previous complete snapshot.
Info
Evidence and limitations

Method: anonymous Streamable HTTP probe. We never invoke a tool.

Attempted protocols: 2026-07-28

ProtocolNot listed in this check
TransportHTTPS · HTTP 404
AuthNo authentication challenge in this check
EvidenceTransport only
Total latency1545 ms
Response bytes0

MCP_RESPONSE_ERROR — The endpoint returned an incomplete or incompatible MCP response.

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"
    }
  }
}

How to use this MCP

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

Choose your client below, then copy the endpoint or configuration. Authentication is completed with the MCP provider, never inside Talandor.

Open the official client guide (opens in a new tab)

      
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
Operational
2025-11-25 · 2 tools
Operational
2025-11-25 · 2 tools
Operational
2025-11-25 · 2 tools
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

      
Watch · 9 €/month
Watch is not available for this evidence
This result does not yet expose a complete public contract or a qualified authentication surface, so there is nothing honest to watch yet. A Watch needs a complete public contract or a qualified authentication surface before it can monitor meaningful changes.
Full WatchAvailability, protocol, auth and public tool contract changes
Surface WatchAvailability, TLS, protocol and auth surface — no private tool diff
Watch checkout is not open. This page does not start a payment. You can sign in from the header; that creates an account, not a Watch. Opening date: not announced yet. Hosted checkout remains closed.
See Watch price, terms and refunds