io.github.mnardit/clipboard-mcp

Clipboard MCP

Is the Clipboard MCP server down? Yes. It has given no valid answer since 2026-10-29: install failed.

Cross-platform MCP server for system clipboard access (read, write, watch)

install failed down since 2026-10-29 · probed 2026-11-15 · unchanged since 2026-11-12

not a zip file: [/tmp/mcpcost-stdio-07PvRc/bundle.mcpb]
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes

Bundle: https://github.com/mnardit/clipboard-mcp/releases/download/v0.1.0/clipboard-mcp-linux-x86_64 (MCPB, for a client that installs bundles; probed in a container with the network off)
Host: github.com
Repository: https://github.com/mnardit/clipboard-mcp
Registry: active, updated 2026-03-27 · registry entry

Compare this server with others.

More servers

Other registry entries on github.com, the ones next to this name; all of them.

Google Drive io.github.mmedum/google-drive-mcp · alive
io.github.mmedum/google-mail-mcp · alive
io.github.mmedum/google-sheets-mcp · alive
io.github.mmedum/pipedrive-mcp · needs network
Mazarbul io.github.mo-cmyk/mazarbul · crashed on start
rpfd io.github.molchalih/rpfd · alive
Software Dock io.github.molidestroyer/software-dock · error
Gemini Media io.github.mordor-forge/gemini-media-mcp · alive

Servers that mention clipboard.

com.clipboardo/site · alive
io.pasteapp/paste · alive
io.github.cyanheads/clipboard-mcp-server · crashed on start
io.github.m0rvayne/mcp-osascript · install failed
com.clipboardo/clipboardo-tools · alive
Pastea io.github.pastea-app/pastea-mcp · alive
io.github.hiphopanda/windows-computer-use-mcp · crashed on start
io.github.CSOAI-ORG/clipboard-ai-mcp · needs mcp<2

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.

Atom feed

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.