Remote MCP · Endpoint
ShippingRates MCP Server MCP server
Yes, as of 1 hour ago: the server returned an HTTP error.
DownLast checked 1 hour ago
Server URL
https://mcp.shippingrates.org/mcp/
The last check failed: the server returned an HTTP error.
- Registry name
- io.github.vinaybhosle/shippingrates-mcp-server
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 26 tools
- Uptime, last 30 days
- 88.2% from 17 checks
- Described by its publisher as
- Ocean shipping intelligence: D&D, freight rates, vessel schedules, port data. 24 tools, 6 carriers.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Failed - the server returned an HTTP error | — |
| 4 days ago | Handshake completed | 769 ms |
| 5 days ago | Handshake completed | 764 ms |
| 7 days ago | Handshake completed | 901 ms |
| 8 days ago | Handshake completed | 754 ms |
| 9 days ago | Handshake completed | 834 ms |
| 12 days ago | Handshake completed | 767 ms |
| 13 days ago | Handshake completed | 779 ms |
| 15 days ago | Handshake completed | 771 ms |
| 17 days ago | Handshake completed | 738 ms |
| 18 days ago | Handshake completed | 763 ms |
| 19 days ago | Handshake completed | 1.20 s |
| 20 days ago | Handshake completed | 779 ms |
| 20 days ago | Handshake completed | 820 ms |
| 21 days ago | Handshake completed | 793 ms |
| 23 days ago | Handshake completed | 728 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 17.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with ShippingRates MCP Server and makes no claim about it beyond what these checks measured.