Skip to content

GridHop GPU Price & Carbon Index MCP server

io.github.gridhopai/gpu-price-indexgridhopaistreamable-httpv0.11.1Scanned

Live GPU rental prices on AWS, Azure, Google Cloud, Vast.ai, RunPod, Lambda and more, with carbon.

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 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.
Govern this server →

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 GridHop GPU Price & Carbon Index MCP server can do

The GridHop GPU Price & Carbon Index MCP server is published by the GitHub account gridhopai. It has 4 tools. It can create or change data (2 tools: price_history and grid_carbon), but cannot delete data. 2 tools only read.

4 tools bring in text other people can write (find_offers, list_gpus, price_history and 1 more).

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 7 times since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 0.11.1.

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.

4 tools

Changes things 2Claude Code: ask
  • grid_carbonHow clean and how expensive the electricity is on the power grids GPU hosts sit on (Europe, Great Britain, the US): carbon intensity now, its low and high over the last 24 hours an…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    How clean and how expensive the electricity is on the power grids GPU hosts sit on (Europe, Great Britain, the US): carbon intensity now, its low and high over the last 24 hours and when, the hour of day that is usually cleanest, the day-ahead wholesale power price now and the cheapest hour in the next 24. Use it to choose where or when to run a job that can wait. The grid_zone values match the grid_zone on find_offers results.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • price_historyHow the cheapest rental price of one GPU class has moved: one point per day since 1 November 2026 (snapshots are hourly from 10 November; earlier days have only a few), or one per …Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    How the cheapest rental price of one GPU class has moved: one point per day since 1 November 2026 (snapshots are hourly from 10 November; earlier days have only a few), or one per hour for the last three days. For each point: the cheapest on-demand price seen, the typical cheapest (median across the day's hourly snapshots) and the cheapest cloud spot price, per GPU. Use it to judge whether a price is unusually low or high before renting, or how much waiting could save.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • find_offersCheapest GPU machines for rent right now across Vast.ai, RunPod, Nebius, CoreWeave, Lambda, OVHcloud, AWS, Azure and Google Cloud, ranked by price.Reads text others writeNo findings

    Why it is in this group

    • The name "find_offers" says "find": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Cheapest GPU machines for rent right now across Vast.ai, RunPod, Nebius, CoreWeave, Lambda, OVHcloud, AWS, Azure and Google Cloud, ranked by price. Returns price per hour, provider, country, tier (datacenter or community host), reliability score, whether the price is interruptible (spot), and grid carbon intensity where an open data feed covers the host's grid (Europe and GB live; US by state or cloud region, a day old). Can filter and sort by carbon. AWS, Azure and Nebius are covered with on-demand prices (providers aws, azure, nebius) and spot prices (aws_spot, azure_spot, nebius_spot); Google Cloud with spot prices only (gcp_spot); CoreWeave with on-demand list prices of whole 8-GPU nodes (coreweave); Lambda and OVHcloud with on-demand list prices (lambda, ovh). Data is refreshed hourly; `observed_at` is the snapshot time. Read-only, free, no account.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • list_gpusEvery GPU class in the current snapshot: VRAM, how many offers and which providers have it, the machine sizes (GPU counts) listed, and the cheapest on-demand and spot price per GPU…Reads text others writeNo findings

    Why it is in this group

    • The name "list_gpus" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Every GPU class in the current snapshot: VRAM, how many offers and which providers have it, the machine sizes (GPU counts) listed, and the cheapest on-demand and spot price per GPU. Use it to see what exists before calling find_offers, or to pick a class by VRAM and price.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

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

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
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.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:19 UTC, unchanged since Nov 15, 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
2
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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://gridhop.dev/v1/mcp?src=mcp-registry: tools/list returned 4 tools to an anonymous client, including price_history (write), grid_carbon (write)

    What this check looks for

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.

  1. Tools1 changed.~1 changedView diff
  2. Tools1 changed.~1 changedView diff
  3. Tools1 changed.~1 changedView diff
  4. Tools2 changed.~2 changedView diff
  5. Tools1 changed.~1 changedView diff
  6. Tools1 changed.~1 changedView diff
  7. Tools3 added.+3 addedView diff

Install

Pinned to version 0.11.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http gpu-price-index https://gridhop.dev/v1/mcp?src=mcp-registry
claude mcp add --transport http gpu-price-index https://gridhop.dev/v1/mcp?src=mcp-registry

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__gpu-price-index__find_offers",
      "mcp__gpu-price-index__list_gpus"
    ],
    "ask": [
      "mcp__gpu-price-index__price_history",
      "mcp__gpu-price-index__grid_carbon"
    ],
    "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 gpu-price-index. Review it before you use it.

Capability tags behind 4 rules
  • mcp__gpu-price-index__find_offers untrusted-input
  • mcp__gpu-price-index__list_gpus untrusted-input
  • mcp__gpu-price-index__price_history untrusted-input
  • mcp__gpu-price-index__grid_carbon untrusted-input

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/io.github.gridhopai/gpu-price-index/verify?hash=0c8341eba137944c9bf56066e65cdba5fab53204817f5b2b4d06b0b1cf44c1ff" | jq -e '.changed == false'

Pinned hash 0c8341eba137, from Nov 20, 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/io.github.gridhopai/gpu-price-index/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.gridhopai/gpu-price-index
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.gridhopai/gpu-price-index.svg)](https://radar.anlyon.com/servers/io.github.gridhopai/gpu-price-index)

Source: MCP Registry · repository. Synced Nov 20, 2026, 17:17 UTC.

GridHop GPU Price & Carbon Index MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the GridHop GPU Price & Carbon Index MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 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 GridHop GPU Price & Carbon Index MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the GridHop GPU Price & Carbon Index 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 GridHop GPU Price & Carbon Index MCP server have?

4 tools: 2 write, 2 read. price_history, grid_carbon, find_offers and list_gpus.

Does the GridHop GPU Price & Carbon Index MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the GridHop GPU Price & Carbon Index MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the GridHop GPU Price & Carbon Index MCP server changed its tools?

Yes, 7 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.