Skip to main content

Zhiyong Parcel Tracking

dev.zhiyong/uniuni-trackingVersion 1.0.8

Track parcel status and scan history; currently supports UniUni only.

Status

Responds436 msAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 14:29 UTC
Latency
436 ms
Remotes responding
1 of 1
Sign-in
No sign-in
Hosting
Hosted outside the EU (detected)
Registry data as of
Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://delivery.zhiyong.dev/mcpResponds436 ms
No sign-in

Claude Code

claude mcp add --transport http uniuni-tracking https://delivery.zhiyong.dev/mcp

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: uniuni-tracking
Remote MCP server URL: https://delivery.zhiyong.dev/mcp

Cursor

{
  "mcpServers": {
    "uniuni-tracking": {
      "url": "https://delivery.zhiyong.dev/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"uniuni-tracking","type":"http","url":"https://delivery.zhiyong.dev/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

1 tools

Tools of Zhiyong Parcel Tracking
Read-only
Idempotent
Open world
track_parcelFor a user-requested parcel, package, shipment, order-delivery, or waybill lookup. Required tracking_number: 5–64 letters, digits, or hyphens. If the user supplied exactly one valid number, call this tool and deliver the actual result. carrier is optional and defaults to UniUni, the only supported carrier today; additional carriers are planned but not available yet. A named unsupported carrier returns unsupported_carrier without querying UniUni. language is optional (en or zh), default en. Inspect isError and structuredContent.outcome rather than HTTP status alone. Distinguish found outcomes (delivered/in_transit), not_found, invalid, unsupported_carrier, rate_limited, carrier_error, and configuration_error. Event times are carrier-local; locations are approximate. Precise addresses, coordinates, staff, internal IDs, and raw carrier payloads are excluded. No separate lookup-authorization flag is required. Lookup inputs and filtered results are logged for up to 30 days or 1,000 records. Full MCP/A2A request sequence and result-handling workflow: https://delivery.zhiyong.dev/agent-workflow.json.NoYesNoYes

Details

Registry status
Active
Published
Oct 12, 2026
Updated
Oct 12, 2026
Repository
Not given
Categories
Uncategorized
GDPR
Not declared

Are you the operator? Claim this listing