Remote MCP · Endpoint

Odometry Mileage Log MCP server

No. Odometry Mileage Log answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://mileage-log.zovo.one/mcp

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/odometry-mileage-log
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
341 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Mileage log and reimbursement
Listing
From the official MCP registry (active).
Recent checks of Odometry Mileage Log
CheckedResultHandshake
44 minutes agoHandshake completed341 ms
3 days agoHandshake completed41 ms
13 days agoHandshake completed575 ms
13 days agoHandshake completed398 ms
15 days agoHandshake completed497 ms
15 days agoHandshake completed308 ms
17 days agoHandshake completed601 ms
18 days agoHandshake completed422 ms
18 days agoHandshake completed326 ms
20 days agoHandshake completed469 ms
22 days agoHandshake completed333 ms
25 days agoHandshake completed459 ms
27 days agoHandshake completed414 ms

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