Remote MCP · Endpoint

ThrustLab MCP server

No. ThrustLab answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://thrustlab.com/mcp

The last check completed an MCP handshake.

Registry name
com.thrustlab/thrustlab
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
620 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Simulate electric UAV powertrains and search a public motor, propeller and battery database.
Listing
From the official MCP registry (active).
Recent checks of ThrustLab
CheckedResultHandshake
3 hours agoHandshake completed620 ms
3 days agoHandshake completed560 ms
13 days agoHandshake completed369 ms
14 days agoHandshake completed405 ms
15 days agoHandshake completed351 ms
16 days agoHandshake completed356 ms
18 days agoHandshake completed364 ms
18 days agoHandshake completed336 ms
19 days agoHandshake completed347 ms
21 days agoHandshake completed368 ms
22 days agoHandshake completed339 ms
25 days agoHandshake completed389 ms
27 days agoHandshake completed351 ms
30 days agoHandshake completed426 ms

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

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