Remote MCP · Endpoint

PDF to Word Converter (Tanod) MCP server

No. PDF to Word Converter (Tanod) answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://tanod.dev/mcp/pdf-to-word

The last check completed an MCP handshake.

Registry name
dev.tanod/pdf-to-word
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
519 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
PDF in, editable Word (.docx) out, with a download link for the converted file.
Listing
From the official MCP registry (active).
Recent checks of PDF to Word Converter (Tanod)
CheckedResultHandshake
4 hours agoHandshake completed519 ms
10 days agoHandshake completed873 ms
11 days agoHandshake completed335 ms
11 days agoHandshake completed431 ms
13 days agoHandshake completed318 ms
14 days agoHandshake completed321 ms
15 days agoHandshake completed310 ms
16 days agoHandshake completed319 ms
17 days agoHandshake completed303 ms
19 days agoHandshake completed436 ms
22 days agoHandshake completed336 ms
24 days agoHandshake completed306 ms
27 days agoHandshake completed317 ms
29 days agoHandshake completed317 ms

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

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 Word Converter (Tanod) and makes no claim about it beyond what these checks measured.