Remote MCP · Endpoint

io.github.theluckystrike/docx MCP server

No. io.github.theluckystrike/docx answered an MCP handshake 14 minutes ago.

UpLast checked 14 minutes ago

Server URL

https://mcp.zovo.one/mcp/docx-editor

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/docx
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
35 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Create real Word .docx files from your AI chat: proposals, quotes, contracts, statements of work.
Listing
From the official MCP registry (active).
Recent checks of io.github.theluckystrike/docx
CheckedResultHandshake
14 minutes agoHandshake completed35 ms
9 days agoHandshake completed53 ms
9 days agoHandshake completed29 ms
11 days agoHandshake completed1.04 s
12 days agoHandshake completed35 ms
13 days agoHandshake completed102 ms
14 days agoHandshake completed33 ms
15 days agoHandshake completed26 ms
16 days agoHandshake completed59 ms
19 days agoHandshake completed61 ms
22 days agoHandshake completed35 ms
24 days agoHandshake completed83 ms
26 days agoHandshake completed53 ms
28 days agoHandshake completed65 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 io.github.theluckystrike/docx and makes no claim about it beyond what these checks measured.