AI Compute Radar MCP server
dev.aicomputeradar/ai-compute-radaraicomputeradar.devstreamable-httpv1.2.3Scanned
Which open models fit your GPU or Mac, measured. Model momentum, GPU rental prices, weekly pick.
6 tools: 4 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the AI Compute Radar MCP server can do
The AI Compute Radar MCP server is published by aicomputeradar.dev, a domain the MCP Registry verified. It has 6 tools. It can create or change data (4 tools: trending_models, gpu_prices, price_history and weekly_pick), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 9, 2026, version 1.2.3.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 4Claude Code: ask
gpu_pricesMedian verified on-demand rental price per GPU class on Vast.ai (USD per hour), with min/p75 and offer counts, the collection timestamp, and per class the Rent Index: this week's m…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Median verified on-demand rental price per GPU class on Vast.ai (USD per hour), with min/p75 and offer counts, the collection timestamp, and per class the Rent Index: this week's median against last week and against the first week collected, a trend word, and the days excluded as marketplace glitches, plus RunPod's lowest posted on-demand price per class (a list price, not a median), Clore.ai's median for the same class (a second marketplace, never blended), and the AWS, Azure and Oracle Cloud pay-as-you-go list prices per GPU-hour, each with the instance type, VM size or bare-metal shape the price sits in (list prices, read four times a day, no statement about capacity). The index describes what prices did; it never forecasts.
price_historyDaily price history per GPU class and source, up to 90 days: the rows the Rent Index and the 30-day range are computed from.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Daily price history per GPU class and source, up to 90 days: the rows the Rent Index and the 30-day range are computed from. Marketplace days (Vast.ai, Clore.ai) are medians over the day's counted hourly medians with min, p75 and offer count; list-price days (RunPod, AWS, Azure, Oracle Cloud, Lambda, Nebius, CoreWeave, Hyperstack) carry the posted price. Each row says which kind it is; never blend the two. Describes what prices did; it never forecasts.
trending_modelsTracked AI models ranked by Heat Score (0–100, weighted percentiles of measured Hugging Face/OpenRouter signals) with the raw signals, local-run facts (GGUF size, quantization) and…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Tracked AI models ranked by Heat Score (0–100, weighted percentiles of measured Hugging Face/OpenRouter signals) with the raw signals, local-run facts (GGUF size, quantization) and links. Models still collecting a week of history have heat=null and rank after scored ones.
weekly_pickThe current pick of the week: one tracked model chosen by a published rule (largest counted Heat Score rise among models that run comfortably on a consumer card of up to 24 GB), wi…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it The current pick of the week: one tracked model chosen by a published rule (largest counted Heat Score rise among models that run comfortably on a consumer card of up to 24 GB), with the numbers frozen at selection time, a device-by-device fit ladder and the written report including its caveats. Pass week (e.g. 2026-w37) for a past issue. issue is null until the first issue is published.
Only reads 2Show 2 read-only tools
find_fitWhich tracked models run on a given GPU or Mac: measured GGUF weights + computed context cache + runtime overhead versus usable memory.No findings
Why it is in this group
- The name "find_fit" says "find": a word for reading.
Description, as the server wrote it Which tracked models run on a given GPU or Mac: measured GGUF weights + computed context cache + runtime overhead versus usable memory. Returns the best recommendation and every verdict (EXCELLENT/GOOD/TIGHT/OFFLOAD_REQUIRED/NOT_RECOMMENDED/UNKNOWN) with plain-language reasons. Get hardware ids from list_hardware.
list_hardwareCurated GPU and Mac profiles the fit engine knows — ids, memory, usable memory after margins, bandwidth.No findings
Why it is in this group
- The name "list_hardware" says "list": a word for reading.
Description, as the server wrote it Curated GPU and Mac profiles the fit engine knows — ids, memory, usable memory after margins, bandwidth. Use an id with find_fit.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:51 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://aicomputeradar.dev/api/mcp: tools/list returned 6 tools to an anonymous client, including trending_models (write), gpu_prices (write), price_history (write), weekly_pick (write)
Posture changes
- Oct 29, 2026
- Tools that change things, listed without credentials: 3 to 4
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:price_historyChanges thingsinputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 4.View diff
- Tools that change things, listed without credentials: 3 to 4
Tools1 added.+1 addedView diff
- Added:price_historyChanges things
Install
Pinned to version 1.2.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http ai-compute-radar https://aicomputeradar.dev/api/mcpclaude mcp add --transport http ai-compute-radar https://aicomputeradar.dev/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ai-compute-radar__find_fit",
"mcp__ai-compute-radar__list_hardware"
],
"ask": [
"mcp__ai-compute-radar__trending_models",
"mcp__ai-compute-radar__gpu_prices",
"mcp__ai-compute-radar__price_history",
"mcp__ai-compute-radar__weekly_pick"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ai-compute-radar. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.aicomputeradar/ai-compute-radar/verify?hash=d7be17819f095db55073ea6041aa7ca819688e4aad05723d1ec1e7678fa38464" | jq -e '.changed == false'Pinned hash d7be17819f09, from Nov 9, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.aicomputeradar/ai-compute-radar/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.aicomputeradar/ai-compute-radar)Source: MCP Registry. Synced Oct 27, 2026, 18:17 UTC.
AI Compute Radar MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the AI Compute Radar MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the AI Compute Radar MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the AI Compute Radar MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the AI Compute Radar MCP server have?
- 6 tools: 4 write, 2 read. trending_models, gpu_prices, price_history, weekly_pick, find_fit and list_hardware.
Does the AI Compute Radar MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the AI Compute Radar MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the AI Compute Radar MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.