Remote MCP · Endpoint

ELD Hub MCP server

No. ELD Hub answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

https://goeldhub.com/mcp

The last check completed an MCP handshake.

Registry name
com.goeldhub/eldhub
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
537 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
FMCSA-registered ELD for small fleets: pricing, ELD comparisons, Highway check and signup.
Listing
From the official MCP registry (active).
Recent checks of ELD Hub
CheckedResultHandshake
33 minutes agoHandshake completed537 ms
3 days agoHandshake completed746 ms
13 days agoHandshake completed1.20 s
13 days agoHandshake completed1.10 s
15 days agoHandshake completed911 ms
16 days agoHandshake completed731 ms
17 days agoHandshake completed654 ms
18 days agoHandshake completed880 ms
18 days agoHandshake completed828 ms
20 days agoHandshake completed1.20 s
22 days agoHandshake completed914 ms
25 days agoHandshake completed339 ms
27 days agoHandshake completed1.93 s

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

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