StudioTV LLM VRAM Calculator
REMOTE · STUDIOTVAI.COM
Does an LLM fit on your GPU? VRAM, KV cache and GPU count for any Hugging Face model.
Available components
Last scanned (52 minutes ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
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 Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 587 tokens (~195/item across 3 items; 3 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 Management83
- Stability observed for 25 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://studiotvai.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=studiotvai.com | CN=WE1,O=Google Trust Services,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 4c4bc93e1c71829e136901ec4b34649a |
| SANs: studiotvai.com, *.studiotvai.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of studiotvai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| studiotvai.com. | 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; preload |
| content-security-policy | default-src 'self' https: data: blob:; script-src 'self' 'unsafe-inline' blob: https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline' https:; img-src 'self' https: data: blob:; font-src 'self' https: data:; connect-src 'self' https: wss:; worker-src 'self' blob:; child-src 'self' blob:; frame-src 'self' blob:; frame-ancestors 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; upgrade-insecure-requests; |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://studiotvai.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://studiotvai.com/api/mcp | HTTPS enforced | 301 | https://studiotvai.com/api/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_vram Does this LLM fit on this GPU? ~301
GPU memory, number of GPUs, speed and rental cost to run an open LLM. Works for the models listed at https://studiotvai.com/api/models.json and any Hugging Face model id or link. Uses the real KV cache of each architecture (sliding window, hybrid linear attention, MLA).
| Name | Type | Req | Description |
|---|---|---|---|
| concurrent_requests | integer | – | Requests served at the same time, each with its own KV cache. Default 1. |
| context | integer | – | Tokens per request (prompt + output). Default 8192. |
| engine | string | – | Serving engine. Default: vllm on data-center GPUs, llamacpp elsewhere. |
| gpu | string | – | GPU id or name, e.g. "rtx-4090", "H100", "mac-m4-max-128". Default h100. List: https://studiotvai.com/api/gpus.json |
| gpu_count | integer|string | – | Number of GPUs, or "auto" (default) for the fewest that fit. |
| kv_cache | string | – | KV cache precision. Default bf16. |
| model | string | yes | Model name or id ("Llama 3.3 70B", "qwen3.8-27b"), Hugging Face id ("Qwen/Qwen3-32B") or link. |
| weights | string | – | Weight format. Default: the official checkpoint (native) or BF16. |
No output schema declared.
No examples provided.
gpu_prices GPU rental prices ~69
Cheapest on-demand price per GPU-hour from AWS, Google Cloud, Azure, RunPod, Vast.ai, Oracle Cloud, OVHcloud, Scaleway, Verda, Akash and UpCloud, checked every hour.
| Name | Type | Req | Description |
|---|---|---|---|
| gpu | string | – | GPU id or name. Omit for every GPU. |
No output schema declared.
No examples provided.
models_that_fit Which LLMs fit on this GPU? ~169
Every listed open model that fits on the given GPU(s), largest first, with the most faithful weight format that fits.
| Name | Type | Req | Description |
|---|---|---|---|
| concurrent_requests | integer | – | Requests served at the same time, each with its own KV cache. Default 1. |
| context | integer | – | Tokens per request (prompt + output). Default 8192. |
| engine | string | – | Serving engine. Default: vllm on data-center GPUs, llamacpp elsewhere. |
| gpu | string | yes | GPU id or name, e.g. "rtx-4090". |
| gpu_count | integer | – | Default 1. |
| kv_cache | string | – | KV cache precision. Default bf16. |
| weights | string | – | Weight format. Default: the official checkpoint (native) or BF16. |
No output schema declared.
No examples provided.
How do I install the StudioTV LLM VRAM Calculator MCP server?
StudioTV LLM VRAM Calculator is a hosted endpoint at https://studiotvai.com/api/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 · studiotvai.com
claude mcp add --transport http com-studiotvai-llm-vram 'https://studiotvai.com/api/mcp'
What is the StudioTV LLM VRAM Calculator MCP server?
StudioTV LLM VRAM Calculator is an MCP server listed in the public MCP registry as com.studiotvai/llm-vram. Does an LLM fit on your GPU? VRAM, KV cache and GPU count for any Hugging Face model. This page covers its hosted endpoint (https://studiotvai.com/api/mcp).
Is the StudioTV LLM VRAM Calculator MCP server safe to use?
StudioTV LLM VRAM Calculator scores 83 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 StudioTV LLM VRAM Calculator MCP server expose?
StudioTV LLM VRAM Calculator exposes 3 tools: estimate_vram, models_that_fit, gpu_prices. Their descriptions and schemas cost roughly 539 tokens of context every time the server is loaded.
Does the StudioTV LLM VRAM Calculator MCP server require authentication?
No. We connected to StudioTV LLM VRAM Calculator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the StudioTV LLM VRAM Calculator MCP server still maintained?
StudioTV LLM VRAM Calculator is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.