Remote MCP · Endpoint

McpStamp Maintenance Log MCP server

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

UpLast checked 20 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/maintenance-log
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
62 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Equipment maintenance log: service entries with cost, full history, and what is due or overdue.
Listing
From the official MCP registry (active).
Recent checks of McpStamp Maintenance Log
CheckedResultHandshake
20 minutes agoHandshake completed62 ms
8 days agoHandshake completed89 ms
9 days agoHandshake completed44 ms
11 days agoHandshake completed551 ms
12 days agoHandshake completed732 ms
13 days agoHandshake completed589 ms
14 days agoHandshake completed904 ms
15 days agoHandshake completed29 ms
16 days agoHandshake completed33 ms
19 days agoHandshake completed872 ms
21 days agoHandshake completed1.18 s
24 days agoHandshake completed685 ms
26 days agoHandshake completed135 ms
28 days agoHandshake completed560 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 Maintenance Log and makes no claim about it beyond what these checks measured.