Remote MCP · Endpoint

com.filetypeconverters/converter MCP server

No. com.filetypeconverters/converter answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://filetypeconverters.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.filetypeconverters/converter
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
60 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Convert files between 44 formats: documents, spreadsheets, images, ebooks, email and subtitles.
Listing
From the official MCP registry (active).
Recent checks of com.filetypeconverters/converter
CheckedResultHandshake
1 hour agoHandshake completed60 ms
18 hours agoHandshake completed46 ms
2 days agoHandshake completed110 ms
3 days agoHandshake completed57 ms
4 days agoHandshake completed49 ms
5 days agoHandshake completed237 ms
6 days agoHandshake completed55 ms
7 days agoHandshake completed57 ms
10 days agoHandshake completed55 ms
13 days agoHandshake completed73 ms
15 days agoHandshake completed62 ms
17 days agoHandshake completed44 ms
19 days agoHandshake completed48 ms
21 days agoHandshake completed56 ms
23 days agoHandshake completed45 ms
25 days agoHandshake completed81 ms
27 days agoHandshake completed63 ms
28 days agoHandshake completed61 ms
29 days agoHandshake completed48 ms

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

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