Remote MCP · Endpoint

Tensorust MCP server

No. Tensorust answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://mcp.tensorust.com/mcp

The last check completed an MCP handshake.

Registry name
com.tensorust/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
103 ms
Tools exposed
52 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Dated LLM and GPU prices, real crates.io downloads, Cargo.lock audits, research, free dev tools
Listing
From the official MCP registry (active).
Recent checks of Tensorust
CheckedResultHandshake
4 hours agoHandshake completed103 ms
3 days agoHandshake completed137 ms
12 days agoHandshake completed317 ms
13 days agoHandshake completed148 ms
14 days agoHandshake completed119 ms
15 days agoHandshake completed304 ms
16 days agoHandshake completed136 ms
17 days agoHandshake completed148 ms
18 days agoHandshake completed149 ms
20 days agoHandshake completed219 ms
22 days agoHandshake completed125 ms
25 days agoHandshake completed102 ms

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

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