Remote MCP · Endpoint

McpStamp Job Cards MCP server

No. McpStamp Job Cards answered an MCP handshake 23 minutes ago.

UpLast checked 23 minutes ago

Server URL

https://mcp.zovo.one/mcp/job-card

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/job-card
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
371 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Job cards for on-site crews: labour hours and materials per job, client signature, totals.
Listing
From the official MCP registry (active).
Recent checks of McpStamp Job Cards
CheckedResultHandshake
23 minutes agoHandshake completed371 ms
8 days agoHandshake completed761 ms
9 days agoHandshake completed63 ms
11 days agoHandshake completed45 ms
12 days agoHandshake completed83 ms
13 days agoHandshake completed600 ms
14 days agoHandshake completed24 ms
15 days agoHandshake completed77 ms
16 days agoHandshake completed185 ms
19 days agoHandshake completed139 ms
21 days agoHandshake completed33 ms
24 days agoHandshake completed41 ms
26 days agoHandshake completed44 ms
28 days agoHandshake completed116 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 Job Cards and makes no claim about it beyond what these checks measured.