Remote MCP · Endpoint

McpStamp Mileage Log MCP server

No. McpStamp Mileage Log answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/mileage-log
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
88 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Log drives by purpose, apply your own dated rates, get deductible totals and a CSV for taxes.
Listing
From the official MCP registry (active).
Recent checks of McpStamp Mileage Log
CheckedResultHandshake
20 minutes agoHandshake completed88 ms
8 days agoHandshake completed96 ms
9 days agoHandshake completed71 ms
11 days agoHandshake completed1.23 s
12 days agoHandshake completed71 ms
13 days agoHandshake completed543 ms
14 days agoHandshake completed182 ms
14 days agoHandshake completed103 ms
16 days agoHandshake completed85 ms
19 days agoHandshake completed1.01 s
21 days agoHandshake completed200 ms
24 days agoHandshake completed842 ms
26 days agoHandshake completed40 ms
28 days agoHandshake completed39 ms

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

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