Compute Screener

Is Compute Screener MCP server safe?

• No hidden instructions were found in its tool descriptions.
• Its error messages showed no secrets or internal details.
• All 14 of its tools are labeled read-only.
• Overall it scored 91/100 on 30 Oct 2026.

A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.

What it can do

14 tools, in the server's own words.

Test results

Safe mode: only tools labeled read-only were run. How the test works

• !
  Ready for the newest MCP version

  1 warning

  • !Uses an older MCP version (2025-11-25). It works today, but it isn't on the July 2026 version (2026-07-28) yet.
  note
• !
  Follows MCP best practices (not scored yet)

  1 tip (not scored)

  • !Very common tool names: search, fetch. Next to other servers' tools the AI may mix them up; a short prefix helps (like "github_search" instead of "search").
  note
• !
  Resources and prompts work

  3 warnings (2 resources, 3 prompts)

  • !gpu_price_brief: Could not open it with sample inputs: gpu must be one of: H100, H200, A100, B200, B300, RTX PRO 6000, L40S, RTX A6000
  • !token_price_comparison: Could not open it with sample inputs: companies must be from: Anthropic, OpenAI, Google, xAI, Meta, Moonshot AI, Alibaba, DeepSeek, Z.ai, Xiaomi, StepFun, MiniMax, Mistral, Refl…
  • !check_a_price: Could not open it with sample inputs: name must be one of: H100, H200, A100, B200, B300, RTX PRO 6000, L40S, RTX A6000, Anthropic, OpenAI, Google, xAI, Meta, Moonshot AI, Alibab…
  • and 2 more
  note
• ✓
  ConnectsConnected in 682 ms
  pass
• ✓
  Lists its toolsFound 14 tools
  pass
• ✓
  Every tool is describedAll 14 tools and their inputs are described
  pass
• ✓
  Tools are labeled safe or dangerousEvery tool has a safety label
  pass
• ✓
  No hidden instructionsNo hidden instructions found in tool descriptions
  pass
• ✓
  Tools work with good inputs

  All good

  • ✓get_gpu_prices: Worked (326 ms)
  • ✓get_token_prices: Worked (190 ms)
  • ✓get_price_history: Worked (198 ms)
  • ✓get_model_prices: Worked (147 ms)
  • ✓get_provider_prices: Worked (258 ms)
  • ✓get_price_changes: Worked (198 ms)
  • ✓get_gpu_market_prices: Worked (198 ms)
  • ✓get_gpu_price_at: Answered with an error, probably because of our sample input: at must look like 2026-10-25 (YYYY-MM-DD).
  • and 6 more
  pass
• ✓
  Bad inputs give a clean error

  All good

  • ✓get_gpu_prices: Refused wrong type for "gpu" with a clear error
  • ✓get_token_prices: Refused wrong type for "company" with a clear error
  • ✓get_price_history: Refused missing required input "name" with a clear error
  • ✓get_price_history: Refused wrong type for "name" with a clear error
  • ✓get_model_prices: Refused wrong type for "model" with a clear error
  • ✓get_provider_prices: Refused wrong type for "provider" with a clear error
  • ✓get_price_changes: Refused wrong type for "days" with a clear error
  • ✓get_gpu_market_prices: Refused wrong type for "gpu" with a clear error
  • and 9 more
  pass
• ✓
  Fast enough

  All good

  • ✓Connecting took 682 ms
  • ✓Listing tools took 66 ms
  • ✓Average tool answer: 206 ms
  • ✓verify_price: Slowest tool: verify_price (482 ms)
  pass
• ✓
  No secrets leakedChecked 30 error messages: no secrets or internal details
  pass
• –
  Tools work togetherNo tool's answer could be fed into another tool, so there were no chains to test (not counted either way)
  not tested

Test it yourself

Free and open source. Same checks, same score.

Show this score on GitHub

Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.

Score over time

• 30 Oct 202691

One test so far. New tests will show here.

Reviews

Coming soon: reviews from people who use Compute Screener, signed in with GitHub, one per person. Reviews never change the score.