Remote MCP · Endpoint

EvaFarm — GPU render nodes MCP server

Yes, as of 1 hour ago: the request timed out.

DownLast checked 1 hour ago

Server URL

https://evafarmstore.ru/mcp

The last check failed: the request timed out.

Registry name
ru.evafarmstore/evafarm
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
5 tools
Uptime, last 30 days
93.3% from 15 checks
Described by its publisher as
Render farm GPU nodes: live availability, installed DCC apps and engines, per-minute cost.
Listing
From the official MCP registry (active).
Recent checks of EvaFarm — GPU render nodes
CheckedResultHandshake
1 hour agoFailed - the request timed out—
1 day agoHandshake completed548 ms
2 days agoHandshake completed1.28 s
2 days agoHandshake completed445 ms
4 days agoHandshake completed475 ms
7 days agoHandshake completed509 ms
9 days agoHandshake completed815 ms
12 days agoHandshake completed392 ms
14 days agoHandshake completed545 ms
16 days agoHandshake completed567 ms
18 days agoHandshake completed518 ms
20 days agoHandshake completed444 ms
22 days agoHandshake completed383 ms
24 days agoHandshake completed488 ms
25 days agoHandshake completed440 ms

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

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 EvaFarm — GPU render nodes and makes no claim about it beyond what these checks measured.