EvaFarm — GPU render nodes
REMOTE · EVAFARMSTORE.RU
Render farm GPU nodes: live availability, installed DCC apps and engines, per-minute cost.
Available components
Last scanned (13 hours ago)
Scores higher than 82% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Cloud Infrastructure
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 684 tokens (~136/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
- Tool “list_nodes” rewrote its description, which is the text the model reads security
- Tool “service_status” rewrote its description, which is the text the model reads security
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Probed https://evafarmstore.ru/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=evafarmstore.ru | CN=YE1,O=Let's Encrypt,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 54e98f8c247dc0a727cb05ee35d555dc245 |
| SANs: evafarmstore.ru | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of evafarmstore.ru. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ru. | present | 26734 | 8 | Verified |
| evafarmstore.ru. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://telegram.org https://oauth.telegram.org; connect-src 'self' https://evafarmstore.ru wss://evafarmstore.ru https://oauth.telegram.org; img-src 'self' data: blob: https:; style-src 'self' 'unsafe-inline'; font-src 'self' data:; frame-src https://oauth.telegram.org; frame-ancestors https://web.telegram.org https://desktop-app.telegram.org https://macos-app.telegram.org; base-uri 'self'; form-action 'self' https://oauth.telegram.org; |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://evafarmstore.ru/mcp | Verified | 200 | |
| http (plaintext) | http://evafarmstore.ru/mcp | HTTPS enforced | 301 | https://evafarmstore.ru/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
estimate_cost Estimate rental cost ~211
Price a rental the way EvaFarm bills it: per active minute, rounded up, no minimum; node preparation is not billed. Give a duration (hours and/or minutes) or a render (frames × seconds_per_frame measured on that kind of node). With a node label the estimate uses its rate; without one it prices every hardware configuration in the catalog. nodes_count > 1 splits the frames evenly across that many identical nodes.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Price currency. Default RUB. |
| frames | integer | – | Number of frames to render. |
| hours | number | – | Rental duration in hours (may be combined with minutes). |
| minutes | number | – | Rental duration in minutes. |
| node | string | – | Node label to price, e.g. "NODE_03". Omit to compare all configurations. |
| nodes_count | integer | – | Identical nodes rendering in parallel. Default 1. |
| seconds_per_frame | number | – | Render time of one frame on that node, in seconds. |
No output schema declared.
No examples provided.
get_node Node details ~66
Full details of one node by its label, e.g. "NODE_03" (also accepts "3" or "node 3").
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Price currency. Default RUB. |
| label | string | yes | Node label, e.g. "NODE_03". |
No output schema declared.
No examples provided.
list_nodes List render nodes ~160
The EvaFarm node catalog with live status (available / busy / reserved / maintenance / ai — busy with an AI workload until `status_until`, not for rent), hardware, hourly price and installed software and render engines. Filter to find a machine for a job.
| Name | Type | Req | Description |
|---|---|---|---|
| available_only | boolean | – | Only nodes free to rent right now. |
| currency | string | – | Price currency. Default RUB. |
| engine | string | – | Required render engine, e.g. "redshift", "octane", "cycles". |
| gpu | string | – | GPU model substring, e.g. "4090" or "5090". |
| software | string | – | Required application, e.g. "cinema4d", "blender", "houdini". |
No output schema declared.
No examples provided.
rental_guide How renting works ~65
How to start renting on EvaFarm: sign-in, projects and wallets, billing rules, connecting via AnyDesk/RustDesk, teams, privacy, and the links to the app, the site and support.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language of the guide. Default en. |
No output schema declared.
No examples provided.
service_status Availability summary ~27
How many nodes are available, busy, reserved, in maintenance or busy with AI right now.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the EvaFarm — GPU render nodes MCP server?
EvaFarm — GPU render nodes is a hosted endpoint at https://evafarmstore.ru/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · evafarmstore.ru
claude mcp add --transport http ru-evafarmstore-evafarm 'https://evafarmstore.ru/mcp'
What is the EvaFarm — GPU render nodes MCP server?
EvaFarm — GPU render nodes is an MCP server listed in the public MCP registry as ru.evafarmstore/evafarm. Render farm GPU nodes: live availability, installed DCC apps and engines, per-minute cost. This page covers its hosted endpoint (https://evafarmstore.ru/mcp).
Is the EvaFarm — GPU render nodes MCP server safe to use?
EvaFarm — GPU render nodes scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the EvaFarm — GPU render nodes MCP server expose?
EvaFarm — GPU render nodes exposes 5 tools: list_nodes, get_node, estimate_cost, service_status, rental_guide. Their descriptions and schemas cost roughly 529 tokens of context every time the server is loaded.
Does the EvaFarm — GPU render nodes MCP server require authentication?
No. We connected to EvaFarm — GPU render nodes without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the EvaFarm — GPU render nodes MCP server still maintained?
EvaFarm — GPU render nodes is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.