Remote MCP · Endpoint

Thruact MCP server

No. Thruact answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://thruact.com/mcp

The last check completed an MCP handshake.

Registry name
com.thruact/thruact
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
117 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Name the job, not the vendor. Routes a provider, fails over, catalog off the tool list.
Listing
From the official MCP registry (active).
Recent checks of Thruact
CheckedResultHandshake
1 hour agoHandshake completed117 ms
2 days agoHandshake completed122 ms
4 days agoHandshake completed192 ms
5 days agoHandshake completed128 ms
7 days agoHandshake completed149 ms
8 days agoHandshake completed128 ms
9 days agoHandshake completed123 ms
12 days agoHandshake completed115 ms
13 days agoHandshake completed114 ms
15 days agoHandshake completed204 ms
16 days agoHandshake completed127 ms
17 days agoHandshake completed118 ms
19 days agoHandshake completed125 ms
20 days agoHandshake completed121 ms
20 days agoHandshake completed203 ms
21 days agoHandshake completed126 ms
22 days agoHandshake completed227 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 Thruact and makes no claim about it beyond what these checks measured.