io.github.theluckystrike/documents
io.github.theluckystrike/documents
Is the io.github.theluckystrike/documents MCP server down? Yes. It has given no valid answer since 2026-10-29: install failed.
Generate real Word documents from your AI chat: proposals, quotes, contracts, SOWs.
install failed down since 2026-10-29 · probed 2026-11-15 · unchanged since 2026-11-12
the bundle does not match the SHA-256 in the registry entry
- Bundle
- https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/docx.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
- Host
- github.com
- Repository
- https://github.com/theluckystrike/mcp-servers
- Website
- https://mcp.zovo.one/s/docx
- Registry
- active, updated 2026-10-14 · registry entry
Compare this server with others.
More servers
Other registry entries on github.com, the ones next to this name; all of them.
- io.github.theluckystrike/currency · install failed
- io.github.theluckystrike/delegacja · install failed
- io.github.theluckystrike/delivery-schedule · install failed
- io.github.theluckystrike/deposit · install failed
- io.github.theluckystrike/docx · install failed
- io.github.theluckystrike/dunning · install failed
- io.github.theluckystrike/duplicate-invoice-check · alive
- io.github.theluckystrike/estimates · install failed
Servers that mention documents.
- AutEng MCP - Markdown Publishing & Document Share Links ai.auteng/mcp · alive
- ai.extend/extend · needs auth
- ai.ezel/ezel · needs auth
- ai.filegraph/document-processing · not found
- FinStat ai.finstat/finstat · needs auth
- Klaaro ai.klaaro/klaaro · needs auth
- ai.waystation/office · paid (402)
- DataSnipe MCP app.datasnipe/datasnipe-mcp · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-29, in every probe since then.
- npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.