Remote MCP · Endpoint

txtreel MCP server

No. txtreel answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://txtreel.com/mcp

The last check completed an MCP handshake.

Registry name
com.txtreel/txtreel
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
374 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free iMessage, WhatsApp, Instagram DM and Reddit chat videos (1080x1920 MP4) and screenshots.
Website
https://txtreel.com/
Listing
From the official MCP registry (active).
Recent checks of txtreel
CheckedResultHandshake
1 hour agoHandshake completed374 ms
2 days agoHandshake completed330 ms
4 days agoHandshake completed386 ms
6 days agoHandshake completed362 ms
8 days agoHandshake completed336 ms
10 days agoHandshake completed351 ms
12 days agoHandshake completed371 ms
14 days agoHandshake completed336 ms
15 days agoHandshake completed332 ms
16 days agoHandshake completed413 ms
17 days agoHandshake completed335 ms
20 days agoHandshake completed335 ms
22 days agoHandshake completed364 ms
23 days agoHandshake completed393 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with txtreel and makes no claim about it beyond what these checks measured.