Remote MCP · Endpoint

Haulroll MCP server

No. Haulroll answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://haulroll-api.cybermaxtools.com/mcp?via=mcp-registry

The last check completed an MCP handshake.

Registry name
dev.workers.cybermax-tools.cybermax/haulroll-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
137 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
FMCSA carrier vetting API + MCP: authority, insurance, OOS. Keys $19/mo; 50 free calls/day.
Listing
From the official MCP registry (active).
Recent checks of Haulroll
CheckedResultHandshake
2 hours agoHandshake completed137 ms
1 day agoHandshake completed78 ms
2 days agoHandshake completed79 ms
2 days agoHandshake completed82 ms
4 days agoHandshake completed93 ms
7 days agoHandshake completed123 ms
9 days agoHandshake completed95 ms
12 days agoHandshake completed435 ms
14 days agoHandshake completed103 ms
16 days agoHandshake completed106 ms
18 days agoHandshake completed101 ms
20 days agoHandshake completed77 ms
22 days agoHandshake completed79 ms
24 days agoHandshake completed73 ms
25 days agoHandshake completed57 ms

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

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