Remote MCP · Endpoint

io.github.theluckystrike/pdf-merger MCP server

No. io.github.theluckystrike/pdf-merger answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.zovo.one/mcp/pdf-merger

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/pdf-merger
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
726 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Merge PDFs from your AI chat: combine, order pages, output one clean PDF. All data is local.
Listing
From the official MCP registry (active).
Recent checks of io.github.theluckystrike/pdf-merger
CheckedResultHandshake
1 hour agoHandshake completed726 ms
1 day agoHandshake completed35 ms
2 days agoHandshake completed71 ms
3 days agoHandshake completed45 ms
4 days agoHandshake completed42 ms
5 days agoHandshake completed37 ms
6 days agoHandshake completed36 ms
9 days agoHandshake completed66 ms
12 days agoHandshake completed25 ms
14 days agoHandshake completed35 ms
16 days agoHandshake completed72 ms
18 days agoHandshake completed45 ms
20 days agoHandshake completed65 ms
23 days agoHandshake completed93 ms
25 days agoHandshake completed31 ms
26 days agoHandshake completed31 ms
28 days agoHandshake completed42 ms
29 days agoHandshake completed109 ms

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

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/pdf-merger and makes no claim about it beyond what these checks measured.