Remote MCP · Endpoint

McpStamp Service Agreement MCP server

No. McpStamp Service Agreement answered an MCP handshake 14 minutes ago.

UpLast checked 14 minutes ago

Server URL

https://mcp.zovo.one/mcp/service-agreement

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/service-agreement
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
148 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Freelance service agreements: scope, deliverables, rate, termination, liability cap, clauses.
Listing
From the official MCP registry (active).
Recent checks of McpStamp Service Agreement
CheckedResultHandshake
14 minutes agoHandshake completed148 ms
9 days agoHandshake completed100 ms
9 days agoHandshake completed46 ms
11 days agoHandshake completed125 ms
12 days agoHandshake completed663 ms
13 days agoHandshake completed73 ms
14 days agoHandshake completed45 ms
15 days agoHandshake completed53 ms
16 days agoHandshake completed83 ms
19 days agoHandshake completed58 ms
22 days agoHandshake completed29 ms
24 days agoHandshake completed38 ms
26 days agoHandshake completed77 ms
28 days agoHandshake completed50 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 Service Agreement and makes no claim about it beyond what these checks measured.