Remote MCP · Endpoint

org.filetourl/mcp MCP server

No. org.filetourl/mcp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://filetourl.org/api/mcp

The last check completed an MCP handshake.

Registry name
org.filetourl/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
719 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Upload a file and get a public shareable URL via API or MCP.
Listing
From the official MCP registry (active).
Recent checks of org.filetourl/mcp
CheckedResultHandshake
1 hour agoHandshake completed719 ms
2 days agoHandshake completed813 ms
4 days agoHandshake completed274 ms
5 days agoHandshake completed949 ms
7 days agoHandshake completed758 ms
8 days agoHandshake completed709 ms
9 days agoHandshake completed897 ms
12 days agoHandshake completed824 ms
13 days agoHandshake completed1.38 s
15 days agoHandshake completed817 ms
17 days agoHandshake completed715 ms
18 days agoHandshake completed566 ms
19 days agoHandshake completed739 ms
20 days agoHandshake completed2.27 s
21 days agoHandshake completed896 ms
21 days agoHandshake completed999 ms
23 days agoHandshake completed991 ms

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

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