Remote MCP · Endpoint

io.github.theluckystrike/contract-clause-library-proposal-template-docx MCP server

No. io.github.theluckystrike/contract-clause-library-proposal-template-docx answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.zovo.one/mcp/clauses

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/contract-clause-library-proposal-template-docx
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
60 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
A personal library of reusable contract and proposal clauses, assembled into a real Word .docx.
Listing
From the official MCP registry (active).
Recent checks of io.github.theluckystrike/contract-clause-library-proposal-template-docx
CheckedResultHandshake
2 hours agoHandshake completed60 ms
2 days agoHandshake completed41 ms
4 days agoHandshake completed163 ms
6 days agoHandshake completed38 ms
7 days agoHandshake completed171 ms
9 days agoHandshake completed183 ms
10 days agoHandshake completed478 ms
11 days agoHandshake completed538 ms
14 days agoHandshake completed31 ms
15 days agoHandshake completed125 ms
17 days agoHandshake completed27 ms
18 days agoHandshake completed37 ms
19 days agoHandshake completed25 ms
21 days agoHandshake completed31 ms
21 days agoHandshake completed29 ms
22 days agoHandshake completed41 ms
23 days agoHandshake completed24 ms

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

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 io.github.theluckystrike/contract-clause-library-proposal-template-docx and makes no claim about it beyond what these checks measured.