Remote MCP · Endpoint

PDF to Markdown MCP server

No. PDF to Markdown answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://pdfmd.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.pdfmd/pdf-to-markdown
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
221 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Convert public PDF links into Markdown with page counts and explicit excerpt limits.
Listing
From the official MCP registry (active).
Recent checks of PDF to Markdown
CheckedResultHandshake
43 minutes agoHandshake completed221 ms
3 days agoHandshake completed86 ms
13 days agoHandshake completed158 ms
13 days agoHandshake completed857 ms
15 days agoHandshake completed1.22 s
15 days agoHandshake completed161 ms
17 days agoHandshake completed116 ms
18 days agoHandshake completed194 ms
18 days agoHandshake completed146 ms
20 days agoHandshake completed365 ms
22 days agoHandshake completed119 ms
25 days agoHandshake completed184 ms
27 days agoHandshake completed124 ms
29 days agoHandshake completed176 ms

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

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 PDF to Markdown and makes no claim about it beyond what these checks measured.