io.github.lplplp101/windows-print-mcp
Windows Print
Is the Windows Print MCP server down? Yes. It has given no valid answer since 2026-11-06: install failed.
Print PDF files to local printers on a Windows PC (page ranges, copies, duplex, B&W).
install failed down since 2026-11-06 · probed 2026-11-15 · unchanged since 2026-11-10
npm error notsup Valid os: win32 npm error notsup Actual os: linux npm error A complete log of this run can be found in: /root/.npm/_logs/2026-11-06T08_36_42_4
- Run it
- npx -y windows-print-mcp@1.0.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/lplplp101/print-mcp
- Registry
- active, updated 2026-11-05 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.lovepivix/weather · alive
- devpulse io.github.loxhness/devpulse-mcp · alive
- io.github.lozit/mcp-freestyle · alive
- io.github.lozit/mcp-standardnotes · crashed on start
- MCP Sidecar io.github.lsequeiraa/mcp-sidecar · needs env
- x402 government-data search io.github.lspain1994/x402-datasets-mcp · alive
- Virtual Filesystem io.github.lu-zhengda/virtual-fs · alive
- io.github.luarss/alternativespe-mcp · alive
Servers that mention windows.
- ai.agentlookups/overassessed · alive
- ai.kaiv/version-truth · alive
- Cellarion app.cellarion/cellarion · needs auth
- SentinelX MCP app.sentinelx/sentinelx · needs auth
- Antevo Trademark ch.antevo/trademark · alive
- Microsoft Windows Security Updates (MSRC CVRF) — buy per-query in-session (msrcwatch) com.a2awire/data-windows-security-update-microsoft-cvrf · alive
- Skopia com.datatreehaus/skopia-floor-plan-layout · not MCP
- Glasswarp com.glasswarp/mcp-server · alive
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-11-06, 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.