Remote MCP · Endpoint

McpStamp Onboarding MCP server

No. McpStamp Onboarding answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://mcp.zovo.one/mcp/onboarding

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/onboarding
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
231 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
New-hire onboarding plans from role templates: tasks with due dates, progress, overdue items.
Listing
From the official MCP registry (active).
Recent checks of McpStamp Onboarding
CheckedResultHandshake
19 minutes agoHandshake completed231 ms
9 days agoHandshake completed1.15 s
9 days agoHandshake completed638 ms
11 days agoHandshake completed537 ms
12 days agoHandshake completed786 ms
13 days agoHandshake completed1.20 s
14 days agoHandshake completed94 ms
15 days agoHandshake completed83 ms
16 days agoHandshake completed65 ms
19 days agoHandshake completed749 ms
21 days agoHandshake completed75 ms
24 days agoHandshake completed50 ms
26 days agoHandshake completed39 ms
28 days agoHandshake completed192 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 Onboarding and makes no claim about it beyond what these checks measured.