Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Compute Screener

REMOTE · COMPUTESCREENER.COM

GPU cloud pricing (H100, H200, B200 per hour) and AI model API pricing per 1M tokens, with history.

+3 this week 77 Trust /100

Last scanned (3 hours ago)

Scores higher than 69% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security74
Transport & Reachability100
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3126 tokens (~195/item across 16 items; 14 tools + 2 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 Management40
  • Stability observed for 12 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 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
  • Supports UI / widget rendering.Pass
Changelog

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 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.

  • 4 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_model_prices” rewrote its description, which is the text the model reads security
    • Tool “get_price_history” rewrote its description, which is the text the model reads security
    • Tool “get_provider_prices” rewrote its description, which is the text the model reads security
    • Schema quality: 174 → 195 ▼ functional
    • Server version: 1.19.0 → 1.21.0 functional
    • “get_model_prices” added an optional parameter “limit” cosmetic
    • “get_model_prices” added an optional parameter “sort” cosmetic
    • “get_price_history” added an optional parameter “from” cosmetic
    • “get_price_history” added an optional parameter “to” cosmetic
    • “get_model_prices” reworded the description of “company” cosmetic
  • 3 Nov 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.

  • 31 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_gpu_market_prices” rewrote its description, which is the text the model reads security
    • Tool “get_gpu_prices” rewrote its description, which is the text the model reads security
    • Tool “get_model_prices” rewrote its description, which is the text the model reads security
    • Tool “get_price_history” rewrote its description, which is the text the model reads security
    • Tool “get_provider_prices” rewrote its description, which is the text the model reads security
    • Tool “get_token_prices” rewrote its description, which is the text the model reads security
    • Tool “get_workload_cost” rewrote its description, which is the text the model reads security
    • Server version: 1.17.0 → 1.19.0 functional
  • 30 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “fetch” rewrote its description, which is the text the model reads security
    • Tool “get_gpu_market_prices” rewrote its description, which is the text the model reads security
    • Server version: 1.16.1 → 1.17.0 functional
  • 29 Oct 26 0
    • Tool “estimate_gpu_cost” was removed ▼ security
    • Tool “estimate_token_cost” was removed ▼ security
    • Tool “find_gpu_for_model” was removed ▼ security
    • Tool “get_forward_curve” was removed ▼ security
    • Tool “get_gpu_volume_metrics” was removed ▼ security
    • Tool “get_market_overview” was removed ▼ security
    • Tool “get_market_stats” was removed ▼ security
    • Tool “get_token_volume” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “fetch” rewrote its description, which is the text the model reads security
    • Tool “get_data_status” rewrote its description, which is the text the model reads security
    • Tool “get_gpu_market_prices” rewrote its description, which is the text the model reads security
    • Tool “get_gpu_price_at” rewrote its description, which is the text the model reads security
    • Tool “get_gpu_prices” rewrote its description, which is the text the model reads security
    • Tool “get_model_prices” rewrote its description, which is the text the model reads security
    • Tool “get_price_changes” rewrote its description, which is the text the model reads security
    • Tool “get_provider_prices” rewrote its description, which is the text the model reads security
    • Tool “get_token_prices” rewrote its description, which is the text the model reads security
    • Tool “get_workload_cost” rewrote its description, which is the text the model reads security
    • Tool “list_indices” rewrote its description, which is the text the model reads security
    • Schema quality: 108 → 159 ▼ functional
    • Resource “gpu-index-latest” was removed ▼ functional
    • Resource “manifests” was removed ▼ functional
    • Resource “token-index-latest” was removed ▼ functional
    • Server version: 1.12.0 → 1.16.1 functional
    • “get_model_prices” added an optional parameter “every” cosmetic
    • “fetch” reworded the description of “id” cosmetic
    • “get_model_prices” reworded the description of “model” cosmetic
    • “get_price_changes” reworded the description of “days” cosmetic
    • “get_workload_cost” reworded the description of “company” cosmetic
    • “get_workload_cost” reworded the description of “model” cosmetic
    • “get_gpu_market_prices” dropped the optional parameter “days” cosmetic
    • Tool “get_workload_cost” changed its title: Inference economics per GPU → Break-even throughput and gross margin cosmetic
    • Tool “list_indices” changed its title: Every GPU and company covered → Every GPU and company listed cosmetic
  • 28 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_gpu_market_prices” rewrote its description, which is the text the model reads security
    • Tool “get_gpu_prices” rewrote its description, which is the text the model reads security
    • Server version: 1.9.0 → 1.12.0 functional
    • “get_gpu_market_prices” reworded the description of “gpu” cosmetic
  • 27 Oct 26 +4
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_gpu_prices” rewrote its description, which is the text the model reads security
    • Tool “get_token_prices” rewrote its description, which is the text the model reads security
    • Schema quality: 196 → 106 ▲ functional
    • Tool “get_gpu_prices” now declares an output schema ▲ functional
    • Tool “get_price_history” now declares an output schema ▲ functional
    • Tool “get_token_prices” now declares an output schema ▲ functional
    • The server now declares the “prompts” capability functional
    • The server now declares the “resources” capability functional
    • First check of Capabilities: pass functional
    • First check of Schema quality: 100 functional
    • First check of Tool coverage: 100 functional
    • New prompt “check_a_price” functional
    • New prompt “gpu_price_brief” functional
    • New prompt “token_price_comparison” functional
    • New resource “compute-screener-view” functional
    • New resource “gpu-index-latest” functional
    • New resource “manifests” functional
    • New resource “site-guide” functional
    • New resource “token-index-latest” functional
    • Server version: 1.5.0 → 1.9.0 functional
    • New tool “estimate_gpu_cost” functional
    • New tool “estimate_token_cost” functional
    • New tool “fetch” functional
    • New tool “find_gpu_for_model” functional
    • New tool “get_data_status” functional
    • New tool “get_forward_curve” functional
    • New tool “get_gpu_market_prices” functional
    • New tool “get_gpu_price_at” functional
    • New tool “get_gpu_volume_metrics” functional
    • New tool “get_market_overview” functional
    • New tool “get_market_stats” functional
    • New tool “get_model_prices” functional
    • New tool “get_price_changes” functional
    • New tool “get_provider_prices” functional
    • New tool “get_token_volume” functional
    • New tool “get_workload_cost” functional
    • New tool “list_indices” functional
    • New tool “search” functional
    • New tool “verify_price” functional
Diagnostics

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://computescreener.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=computescreener.com CN=WE1,O=Google Trust Services,C=US 14 Oct 2026 12 Jan 2027 ECDSA 256 ECDSA-SHA256 b21d98d57e4922441356ac99ed3c8db5
SANs: computescreener.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 computescreener.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
computescreener.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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://computescreener.com/mcp Verified 200
http (plaintext) http://computescreener.com/mcp HTTPS enforced 301 https://computescreener.com/mcp
MCP tools · 14 exposed · ~2,413 tokens

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 →

Tool Tokens
fetch ~114

The full text of a result from search, by its id (gpu:H100, company:OpenAI, model:<page>, provider:<page>, page:methodology, page:futures, page:verification, page:power, page:coding, page:datacenters) or the page's address: prices, changes, history, providers or models, as on the site.

NameTypeReqDescription
idstringyesAn id from search, or a page's address (https://computescreener.com/gpu/h100).
NameTypeReqDescription
idstring|nullyes–
metadataobject|null––
textstring|nullyes–
titlestring|nullyes–
urlstring|nullyes–

No examples provided.

get_data_status ~67

How fresh the data is, as the status page shows it: when the GPU and token indices were last calculated, today's index day, each GPU price source's status and last read, each GPU index's status, provider count and imputed share, and the latest days with a manifest.

Input schema present but exposes no named parameters.

NameTypeReqDescription
gpu_indexobject|nullyes–
manifestsobject|null––
methodologystring|null––
token_indexobject|nullyes–
verifierstring|null––

No examples provided.

get_gpu_market_prices ~263

Rental prices of every other GPU, as the site's Every GPU page lists them (https://computescreener.com/gpus): RTX 5090, A40, L4, GH200, V100 and over 60 more, each one's lowest and median price per GPU-hour today as posted (offers that can be rented now), its offers, how many are in stock, its providers and the cheapest, from RunPod, Vast.ai, Akash, Shadeform's catalog of clouds, Lium, Vultr, AWS, Azure, Google Cloud, Oracle, Akamai, Koyeb, Packet, Northflank, Fireworks AI, Thunder Compute, DeepInfra, Replicate, Baseten, Lightning AI, Beam, fal, Exoscale, Atlantic.Net, Hugging Face, IBM Cloud, Novita AI, Oblivus, FriendliAI, Seeweb (posted in euros, converted at the ECB rate) and, from 2026-11-01, SaladCloud. Not an index: configurations are not standardized (the GPUs with a price index are in get_gpu_prices).

NameTypeReqDescription
gpustring–A GPU model, e.g. "RTX 5090" or "A40"; omit for all.
NameTypeReqDescription
aboutstring|null––
gpusarray|nullyes–
licensestring|null––
unitstring|null––
updatedstring|null––

No examples provided.

get_gpu_price_at ~125

A GPU's index price at a past date or time, as its page's chart draws it: the value calculated at or just before an ISO time within the last few days (the 1D and 5D charts; prices are recalculated every minute, kept at least every 30 minutes), else the daily value of that US Central day.

NameTypeReqDescription
atstringyesA date (2026-10-20) or an ISO time (2026-10-26T15:00:00Z).
gpustringyesThe GPU.
NameTypeReqDescription
as_ofstring|nullyes–
gpustring|nullyes–
kindstring|nullyes–
notestring|null––
pricenumber|nullyes–
provisionalboolean|null––
requestedstring|nullyes–
unitstring|null––
urlstring|null––

No examples provided.

get_gpu_prices ~262

Today's GPU rental prices: the price index in USD per GPU-hour for each GPU (H100, H200, A100, B200, B300, RTX PRO 6000, L40S, RTX A6000, RTX 6000 Ada, L40, RTX 4090), with 1-day, 1-week and 1-month changes, the index day and a link to each GPU's page. Give one GPU to also get what its page shows: its benchmark contract, each provider's average price standardized to that contract, the posted prices of providers outside the index (AWS, Azure, Google Cloud, Oracle, Koyeb, Packet: each one's lowest, as posted) and its compute futures prices: each exchange listing a contract on its rental price, with the last price and 24-hour volume, read within the last minute (all of them: https://computescreener.com/futures). For past values use get_price_history; for providers' posted prices get_provider_prices. For questions like "what does an H100 cost per hour?", "how much is it to rent a B200?" or "H200 cloud pricing today".

NameTypeReqDescription
gpustring–One GPU; omit for all listed GPUs.
NameTypeReqDescription
gpusarray|nullyes–
licensestring|null––
markets_notestring|null–What the compute futures prices are, with markets
methodologystring|null––
sourcesstring|null––
tickers_notestring|null––
unitstring|nullyes–
updatedstring|nullyesWhen the GPU prices were last calculated (ISO 8601, UTC)

No examples provided.

get_model_prices ~445

Each AI model's posted API prices in USD per 1M input, cached input and output tokens and its price at the mix of tokens agents send (the models behind the token index and the Intelligence Index chart's, each with its page), with its usage share and its 1-month change. Give a model (name or page id, e.g. "Claude Opus 5.5" or "kimi-k3") for its daily price history as its page's chart draws it (a name several models share answers with each one's prices), or a company to list its models. Every other model OpenRouter prices is on the Every AI model page (https://computescreener.com/models): give its name or id (e.g. "meta-llama/llama-3.3-70b-instruct"), any company on it (e.g. "Cohere"), or every: true to list them, with sort: "price" for the cheapest first. For questions like "what does Claude Sonnet cost per 1M input and output tokens?", "the cheapest AI model API" or "the cheapest provider of a model".

NameTypeReqDescription
companystring–List only this company's models: one of the token index's companies (Anthropic, OpenAI, Google, xAI, Meta, Moonshot AI, Alibaba, DeepSeek, Z.ai, Xiaomi, StepFun, MiniMax, Mistral, Reflection AI, NVID…
everyboolean–List every model on the Every AI model page (/models), not only those with a page.
limitinteger–How many models to list (the Every AI model page lists over 300).
modelstring–A model's name, page id or OpenRouter id; omit to list models.
sortstring–"price": the cheapest at the mix first (every model's default); "name": by company and name. A company's models otherwise come by usage, as its page lists them.
NameTypeReqDescription
fieldsstring|null–What each figure of a model's row is
licensestring|null––
modelsarray|nullyes–
notestring|null––
sourcesstring|null––
totalinteger|null–How many models the list has before limit
unitstring|nullyes–
updatedstring|null––

No examples provided.

get_price_changes ~107

What moved, as the site's changes show it: every listed GPU and company index's change over 1, 5, 7 or 30 days (the site's 1D, 5D, 1W and 1M), largest first, and every AI model whose price (at the mix, as its page charts it) moved over that time.

NameTypeReqDescription
daysinteger–How many days back: 1, 5, 7 or 30.
NameTypeReqDescription
daysinteger|null––
index_movesarray|nullyes–
licensestring|null––
model_price_changesarray|nullyesEach model whose price at the mix (87% cache read, 12% input, 1% output) moved, as its page's chart and changes show it

No examples provided.

get_price_history ~202

Price history of one GPU (USD per GPU-hour) or one AI company (USD per 1M tokens), oldest first. GPU history is daily from 2025-11-07 for H100 and A100, from 2026-10-23 for the other first GPUs and from its first index day for each GPU added later, weekly before; token history is daily from 2025-01-01. Give days for the latest days, or from and to for a period (e.g. a month: from 2026-01-01 to 2026-01-31).

NameTypeReqDescription
daysinteger–How many days back from the latest value.
fromstring–First day of a period, YYYY-MM-DD (instead of days).
namestringyesA GPU or an AI company.
tostring–Last day of the period, YYYY-MM-DD; omit for the latest.
NameTypeReqDescription
kindstring|nullyes–
licensestring|null––
namestring|nullyes–
notestring|null–With from: how the period's values are dated
pointsarray|nullyes–
sourcesstring|null––
unitstring|nullyes–
urlstring|null––

No examples provided.

get_provider_prices ~180

Each GPU cloud's and marketplace's posted on-demand prices per GPU, as its page on the site shows them (lowest and highest that day, as posted, with the configuration of the lowest) and its average in the index, standardized to the GPU's benchmark contract so providers compare like for like. Give a provider (e.g. "CoreWeave", "RunPod") and/or a GPU; a provider outside the index (AWS, Azure, Google Cloud, Oracle and others) answers with its lowest posted price for each GPU, as the GPU's page lists it. For questions like "what does RunPod charge for an H100?", "AWS H100 price" or "Lambda GPU pricing".

NameTypeReqDescription
gpustring–Only this GPU.
providerstring–A provider's name or page id; omit for all providers.
NameTypeReqDescription
licensestring|null––
notestring|null––
other_posted_pricesarray|null–With a GPU: the providers outside the index (the hyperscalers and others), each one's lowest on-demand price per GPU-hour as posted, not standardized, as the GPU's page lists them
providersarray|nullyes–
unitstring|null––
updatedstring|null––

No examples provided.

get_token_prices ~156

Today's AI token prices by company: each company's price index in USD per 1M tokens at the mix of tokens agents send (87% cache read, 12% input, 1% output), weighted by its models' usage, with 1-day, 1-week and 1-month changes. Give one company to also get its models' usage shares and posted input, cached input and output prices, and its estimated spend on OpenRouter. For one model's prices use get_model_prices; for past values get_price_history. For questions like "what does Claude cost per 1M tokens?" or "which AI company's API is cheapest?".

NameTypeReqDescription
companystring–One company; omit for all listed companies.
NameTypeReqDescription
companiesarray|nullyes–
licensestring|null––
methodologystring|null––
sourcesstring|null––
tickers_notestring|null––
unitstring|nullyes–
updatedstring|nullyesWhen the token prices were last calculated (ISO 8601, UTC)

No examples provided.

get_workload_cost ~207

Break-even throughput, as each GPU's and each model's page shows it: the tokens per second one GPU must sell at a model's list price (3 input : 1 output) to cover the GPU's rental price today. Give a GPU for every model on it, a model for every GPU, or a company for its models; give a throughput for what the gross margin calculator on a model's page shows: the revenue per GPU-hour and the gross margin. For questions like "how many tokens per second must an H100 sell to cover its rent?".

NameTypeReqDescription
companystring–Only this company's models.
gpustring–One GPU; omit for all listed.
modelstring–A model's name or page id (e.g. "Claude Opus 5.5"); omit for every model.
throughput_tokens_per_secondnumber–Tokens per second one GPU generates (input and output, 3 to 1).
NameTypeReqDescription
licensestring|null––
methodologystring|null––
notestring|null––
rowsarray|nullyes–
throughput_tokens_per_secondnumber|null––

No examples provided.

list_indices ~101

Every GPU rental index and AI company token index the site lists: whether it is listed (has a price, a month of history and a value for each of its 1-day, 1-week and 1-month changes), its latest value and day, when its history starts, its provider or model count, its benchmark contract (GPUs) and its page, and the GPUs on the Every GPU page. Use it to see what the other tools accept.

Input schema present but exposes no named parameters.

NameTypeReqDescription
companiesarray|nullyes–
gpusarray|nullyes–
licensestring|null––
methodologystring|null––
other_gpusarray|null–The GPUs on the Every GPU page, priced as posted by get_gpu_market_prices (not indices)
unitsobject|null––

No examples provided.

search ~61

Search Compute Screener's GPUs, AI companies, AI models, GPU providers and methodology by keyword (e.g. "H100", "Claude Opus", "CoreWeave", "benchmark contract"). Returns ids for fetch.

NameTypeReqDescription
querystringyesKeywords.
NameTypeReqDescription
resultsarray|nullyes–

No examples provided.

verify_price ~123

How a published daily value can be checked: whether it is final, and for a final day its manifest (every file it was computed from with its SHA-256, the factors in force, the calculation code's SHA-256 and the final values) and the command that recomputes it from the public files with the published code. Omit date for the latest day with a manifest.

NameTypeReqDescription
datestring–The index day, YYYY-MM-DD (US Central for GPUs, UTC for companies).
namestringyesA GPU or an AI company.
NameTypeReqDescription
datestring|nullyes–
explanationstring|nullyes–
kindstring|nullyes–
manifestobject|null––
methodologystring|null––
namestring|nullyes–
publishednumber|null–The value as published for that day
recomputeobject|null––
statusstring|nullyesverifiable: final, with a manifest; provisional: the day is not over; pending: final, its manifest comes with the next update; rebuilt_history: before manifests began; restated: final, as recomputed…
unitstring|null––

No examples provided.

Install

How do I install the Compute Screener MCP server?

Compute Screener is a hosted endpoint at https://computescreener.com/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 · computescreener.com

# add to Claude Code
claude mcp add --transport http com-computescreener-compute-screener 'https://computescreener.com/mcp'
Common questions

What is the Compute Screener MCP server?

Compute Screener is an MCP server listed in the public MCP registry as com.computescreener/compute-screener. GPU cloud pricing (H100, H200, B200 per hour) and AI model API pricing per 1M tokens, with history. This page covers its hosted endpoint (https://computescreener.com/mcp).

Is the Compute Screener MCP server safe to use?

Compute Screener scores 77 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 Compute Screener MCP server expose?

Compute Screener exposes 14 tools: get_gpu_prices, get_token_prices, get_price_history, get_model_prices, get_provider_prices, and 9 more. Their descriptions and schemas cost roughly 2,413 tokens of context every time the server is loaded.

Does the Compute Screener MCP server require authentication?

No. We connected to Compute Screener without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Compute Screener MCP server still maintained?

Compute Screener 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.