Remote MCP · Endpoint
FreightUtils MCP Server MCP server
No. FreightUtils MCP Server answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://www.freightutils.com/api/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.SoapyRED/freightutils
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 800 ms
- Tools exposed
- 26 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Neutral freight reference + validation layer for AI agents: ADR, HS, UN/LOCODE, freight math
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 800 ms |
| 1 day ago | Handshake completed | 296 ms |
| 2 days ago | Handshake completed | 559 ms |
| 3 days ago | Handshake completed | 283 ms |
| 4 days ago | Handshake completed | 475 ms |
| 5 days ago | Handshake completed | 268 ms |
| 6 days ago | Handshake completed | 365 ms |
| 8 days ago | Handshake completed | 293 ms |
| 11 days ago | Handshake completed | 286 ms |
| 13 days ago | Handshake completed | 277 ms |
| 15 days ago | Handshake completed | 290 ms |
| 18 days ago | Handshake completed | 574 ms |
| 20 days ago | Handshake completed | 295 ms |
| 22 days ago | Handshake completed | 452 ms |
| 24 days ago | Handshake completed | 318 ms |
| 26 days ago | Handshake completed | 425 ms |
| 27 days ago | Handshake completed | 370 ms |
| 28 days ago | Handshake completed | 389 ms |
| 29 days ago | Handshake completed | 380 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 FreightUtils MCP Server and makes no claim about it beyond what these checks measured.