https://docs.goshippo.com/mcp ↗
Official Shippo MCP server: compare multi-carrier rates, buy labels, track packages, and validate addresses from a prompt.
shippo-mcp is a remote MCP server published at docs.goshippo.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 838 ms, a delay an agent will notice. It offers a narrow, focused set of 3 tools. On the protocol side it speaks the 2026-07-28 stateless spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
search_shippo_api_documentation — Overly verbose name with redundant 'Shippo API Documentation' repetitionquery_docs_filesystem_shippo_api_documentation — Description truncated mid-sentence, making purpose unclearquery_docs_filesystem_shippo_api_documentation — Functionally overlaps with search_shippo_api_documentation toolRisk: 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/goshippo-shippo-mcp)<a href="https://mcpmetrics.io/servers/goshippo-shippo-mcp"><img src="https://mcpmetrics.io/badge/goshippo/shippo-mcp/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 | Dual-era | 200 | 838 | 200 | 836 | 2026-07-28 |
| 2026-09-11 15:07:20 | Dual-era | 200 | 1055 | 200 | 1093 | 2026-07-28 |
| 2026-09-11 13:13:33 | Dual-era | 200 | 558 | 200 | 1993 | 2026-07-28 |
| 2026-09-11 11:20:19 | Dual-era | 200 | 911 | 200 | 496 | 2026-07-28 |
| 2026-09-11 09:28:19 | Dual-era | 200 | 435 | 200 | 1114 | 2026-07-28 |
| 2026-09-10 21:16:35 | Auth-gated | 401 | 407 | 401 | 408 | — |
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.