https://mcp.myshipi.com/api/mcp ↗
Manage shipping workflows by creating labels, tracking packages, and scheduling carrier pickups. Compare live rates from major carriers like FedEx and UPS to optimize costs for every shipment. Organize logistical operations with a centralized address book and detailed shipping analytics.
Shipi is a remote MCP server published at mcp.myshipi.com. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 1,479 ms, a delay an agent will notice. It exposes a broad tool surface of 19 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
create_shipment — Includes NAIAS-specific hardcoded fields without clear parameter definitions.create_naias_label — Overly specific to NAIAS, reducing general usability and clarity.search_shipments — Limited description of parameter requirements (e.g., what filters are supported).Risk: medium
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/shipi-shipi)<a href="https://mcpmetrics.io/servers/shipi-shipi"><img src="https://mcpmetrics.io/badge/shipi/shipi/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-11 16:59:56 | Legacy | 400 | 1478 | 200 | 1544 | 2025-11-25 |
| 2026-09-11 15:07:20 | Legacy | 400 | 1498 | 200 | 1557 | 2025-11-25 |
| 2026-09-11 13:13:33 | Legacy | 400 | 1647 | 200 | 1430 | 2025-11-25 |
| 2026-09-11 11:20:19 | Legacy | 400 | 1394 | 200 | 1639 | 2025-11-25 |
| 2026-09-11 09:28:19 | Legacy | 400 | 1394 | 200 | 1479 | 2025-11-25 |
| 2026-09-10 21:16:35 | Unknown | 404 | 348 | 404 | 340 | — |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.