Remote MCP · Endpoint

Haulest MCP server

No. Haulest answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://haulest.com/mcp

The last check completed an MCP handshake.

Registry name
com.haulest/haulest
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
290 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Moving cost ranges, reviewed movers, licence checks, guides, and quote requests.
Listing
From the official MCP registry (active).
Recent checks of Haulest
CheckedResultHandshake
1 hour agoHandshake completed290 ms
1 day agoHandshake completed262 ms
1 day agoHandshake completed240 ms
3 days agoHandshake completed102 ms
5 days agoHandshake completed115 ms
8 days agoHandshake completed106 ms
10 days agoHandshake completed142 ms
12 days agoHandshake completed115 ms
14 days agoHandshake completed217 ms
16 days agoHandshake completed122 ms
18 days agoHandshake completed99 ms
20 days agoHandshake completed108 ms
22 days agoHandshake completed95 ms
24 days agoHandshake completed198 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

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 Haulest and makes no claim about it beyond what these checks measured.