# compute.pangle.online — GPU rental market (remote · compute.pangle.online)

Live GPU rental market: 2,500+ offers across a dozen provider feeds. History, watches, limit orders.

- Trust score: 69/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `compute.pangle.online`: 69/100 (this document), [markdown](https://verifymcp.io/servers/online-pangle-compute-gpu-rental-market/compute.md), [page](https://verifymcp.io/servers/online-pangle-compute-gpu-rental-market/compute)

## Channel facts

- Endpoint: `https://compute.pangle.online/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 25 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3700 tokens (~148/item across 25 items; 25 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (4% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_watch" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the compute.pangle.online — GPU rental market MCP server?

compute.pangle.online — GPU rental market is a hosted endpoint at https://compute.pangle.online/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.

### Claude

```bash
claude mcp add --transport http online-pangle-compute-gpu-rental-market 'https://compute.pangle.online/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "online-pangle-compute-gpu-rental-market": {
      "url": "https://compute.pangle.online/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "online-pangle-compute-gpu-rental-market": {
      "type": "http",
      "url": "https://compute.pangle.online/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.online-pangle-compute-gpu-rental-market]
url = "https://compute.pangle.online/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "online-pangle-compute-gpu-rental-market": {
      "type": "remote",
      "url": "https://compute.pangle.online/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add online-pangle-compute-gpu-rental-market --url 'https://compute.pangle.online/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  online-pangle-compute-gpu-rental-market:
    url: "https://compute.pangle.online/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "online-pangle-compute-gpu-rental-market": {
      "Transport": "http",
      "Url": "https://compute.pangle.online/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add online-pangle-compute-gpu-rental-market -t streamable-http -u 'https://compute.pangle.online/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "online-pangle-compute-gpu-rental-market": {
      "type": "http",
      "url": "https://compute.pangle.online/mcp/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 69, +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.

### 2026-09-18 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 65, +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.

### 2026-09-09 (score 64, +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.

### 2026-09-07 (score 63, +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.

### 2026-09-05 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (25)

### `search_offers` (~206 tokens)

Search live GPU offers. gpu matches the model name (e.g. '4090', 'H100').
    offer_class: on_demand | interruptible | reserved. country: ISO-2 (e.g. US),
    a comma list ('DE,NL'), or 'EU' for the 27 member states. min_gpu_count
    filters to multi-GPU configs (8 = full 8x nodes). region substring-matches
    the provider's region/datacenter label. Returns offers ranked
    cheapest-first by price_per_gpu_hr.

Input parameters:

- `country` (string)
- `gpu` (string)
- `limit` (integer)
- `max_price_per_gpu_hr` (number)
- `min_gpu_count` (integer)
- `min_reliability` (number)
- `min_vram_gb` (number)
- `offer_class` (string)
- `provider` (string)
- `region` (string)

Output parameters:

- `result` (array)

### `get_offer` (~28 tokens)

Fetch one offer by its id (from search_offers).

Input parameters:

- `offer_id` (string, required)

### `market_stats` (~40 tokens)

Live market snapshot: total offers, GPU models, idle-capacity share,
    per-provider freshness/health, cheapest price per model, current fee_bps.

### `price_history` (~122 tokens)

Price history for one GPU model (exact name from search_offers/market_stats,
    e.g. 'RTX 4090'). offer_class: on_demand | interruptible. Returns per-provider
    series of [ts, min_price_per_gpu_hr, median_price_per_gpu_hr, offer_count];
    ranges past 3 days are bucketed (hourly, then 6-hourly past a week).

Input parameters:

- `gpu` (string)
- `gpu_model` (string)
- `hours` (integer)
- `offer_class` (string)

### `idle_history` (~64 tokens)

The idle-capacity index over time: share of listed GPU capacity that is
    interruptible (spot/bid) — idle hardware looking for work. Points are
    [ts, idle_share, idle_offers, total_offers].

Input parameters:

- `hours` (integer)

### `best_value` (~103 tokens)

Perf-per-dollar board: for each GPU model, best live price vs its FP16
    tensor throughput (dense, vendor spec sheets) -> TFLOPS per dollar-hour.
    The answer to 'most compute for my budget' rather than 'cheapest card'.
    Models without a defensible public spec figure are listed as unrated.

Input parameters:

- `limit` (integer)
- `min_vram_gb` (number)
- `offer_class` (string)

### `provider_reliability` (~65 tokens)

How dependable each provider's data feed has been for this station
    (poll success over the trailing window), plus the provider's own average
    machine reliability where reported. feed_score is about the DATA, not
    their hardware.

Input parameters:

- `days` (integer)

### `price_position` (~79 tokens)

Rent-now-or-wait context: where the current best price for one GPU
    model sits inside its own trailing 7/30-day range (percentile, 24h trend,
    verdict). Descriptive, not a forecast.

Input parameters:

- `gpu` (string)
- `gpu_model` (string)
- `offer_class` (string)

### `spot_spread` (~50 tokens)

On-demand vs interruptible spread: the live discount for idle capacity
    per model; pass gpu_model for its history too.

Input parameters:

- `gpu_model` (string)
- `hours` (integer)

### `will_it_fit` (~262 tokens)

Will this model fit, and what does a fitting machine cost right now?
    Deterministic VRAM arithmetic — weights (params x bytes/precision) + KV
    cache (2 x layers x kv_heads x head_dim x context x batch) + stated
    overhead — checked against the live book, cheapest fitting offers first.
    Pass a known model slug (llama-3.1-8b/70b/405b, mistral-7b, mixtral-8x7b,
    qwen2.5-7b/32b/72b, gemma-2-9b/27b) OR params_b for a stated Llama-like
    guess. precision: fp16/int8/int4. If you pass tokens_per_s (YOUR measured
    throughput — we never invent one), each offer gains usd_per_m_tokens.
    Every approximation is in the assumptions list, not fine print.

Input parameters:

- `batch` (integer)
- `context` (integer)
- `limit` (integer)
- `model` (string)
- `offer_class` (string)
- `params_b` (number)
- `precision` (string)
- `tokens_per_s` (number)

### `true_cost_notes` (~106 tokens)

The billing fine print behind the $/hr, verified per provider from
    their own published pages (source URL + date on every claim): billing
    granularity (per-second vs per-minute), whether storage bills while
    stopped, bandwidth/egress fees, and the commonly-missed gotchas (e.g.
    Vast bandwidth never appears in $/hr; RunPod stopped volume disk costs
    double). Providers we have not verified are listed with NO claims.

### `register_account` (~69 tokens)

Create a metering account: returns a bearer token (shown once, we keep
    only a hash). Pass it as account_token on rent calls to build a usage
    ledger you can read back with account_usage. Optional — renting works
    without one.

Input parameters:

- `label` (string)

### `account_usage` (~87 tokens)

Your metered usage ledger: placements, destroys, estimated hours and USD,
    and the platform fee (2.5%, $0.01 min, $5.00 cap per lease per UTC day) priced
    at the rate live at event time. Distinct from fee_bps, the display markup.

Input parameters:

- `account_token` (string, required)
- `days` (integer)

### `create_watch` (~146 tokens)

Create a price watch (tripwire): fires when the best live fee-adjusted
    price per GPU-hour matching gpu (and optional offer_class) drops to or
    under max_price_per_gpu_hr. Checked every poll (~5 min). Returns the watch
    with its id — the id is the only key; poll it with watch_status, or give a
    public webhook_url to be POSTed on each trip. Watches re-arm when the
    price climbs 2% back over the line.

Input parameters:

- `gpu` (string, required)
- `max_price_per_gpu_hr` (number, required)
- `offer_class` (string)
- `webhook_url` (string)

### `watch_status` (~43 tokens)

Current state of a watch: armed/tripped, last price seen, recent
    events, and the best matching offer right now.

Input parameters:

- `watch_id` (string, required)

### `delete_watch` (~22 tokens)

Delete a watch by id.

Input parameters:

- `watch_id` (string, required)

### `create_limit_order` (~498 tokens)

Place a standing LIMIT ORDER: when the best live fee-adjusted price for
    gpu (and optional offer_class) trades at or under max_price_per_gpu_hr,
    the station cuts a signed FILL TICKET naming the exact offer. The station
    never holds your provider key — the ticket is executed by whoever does:
    the open-source keyholder sidecar (/agents/#sidecar), your own agent
    long-polling POST /api/orders/{id}/ticket, or a human with curl. Returns
    the order with order_secret SHOWN ONCE — it authenticates ticket reads and
    the fill call for this order only and can rent nothing by itself. Triggers
    are checked on the poll cadence (~5-min bars, not tick-by-tick); orders
    expire in 30 days; a ticket lasts ~4 minutes then the order re-arms.

    standing=true makes it a STANDING order — compute that survives: after a
    live fill the sidecar keeps watching the machine, and when it is preempted
    or dies the order re-arms and refills from the CURRENT best offer, up to
    max_refills times with cooloff_seconds between death and refill. Honest
    limits: this re-provisions the MACHINE, not the WORK (GPU memory is not
    portable — resume from your own checkpoints); refills need your sidecar
    alive (it is both witness and executor); cancelling stops supervision but
    cannot destroy a running machine (the station holds no key). Watchdog:
    spend_alert_usd / age_alert_hours fire a "still yours?" webhook once per
    machine when the spend ESTIMATE (uptime x price; the provider's bill is
    authoritative) or age crosses your line — auto_destroy_budget_usd remains
    the hard stop.

Input parameters:

- `age_alert_hours` (number)
- `auto_destroy_budget_usd` (number)
- `cooloff_seconds` (integer)
- `gpu` (string, required)
- `max_price_per_gpu_hr` (number, required)
- `max_refills` (integer)
- `min_gpu_count` (integer)
- `min_vram_gb` (number)
- `offer_class` (string)
- `spend_alert_usd` (number)
- `standing` (boolean)
- `webhook_url` (string)

### `limit_order_status` (~69 tokens)

State of a limit order (armed/ticketed/filled/cancelled/expired), last
    price seen, recent events. Pass order_secret to also read the live fill
    ticket when one is cut.

Input parameters:

- `order_id` (string, required)
- `order_secret` (string)

### `cancel_limit_order` (~39 tokens)

Cancel a limit order. Requires the order_secret from create_limit_order.

Input parameters:

- `order_id` (string, required)
- `order_secret` (string, required)

### `rent_x402` (~533 tokens)

Rent a prepaid block of GPU time with a wallet and NO account, NO API key
    and no human, over x402 (HTTP 402 micropayments, USDC on Base).

    Call it with no arguments and you get the payment challenge: an x402
    PaymentRequirementsResponse whose accepts[0].extra.x402_fee states the block
    price, the platform fee IN DOLLARS, that there are no refunds, and that you
    are charged only after the lease is live. Sign the EIP-3009
    transferWithAuthorization it describes, then call again with x_payment set to
    the base64 PaymentPayload (the same value the HTTP rail sends as X-PAYMENT).

    `ssh_pubkey` is HOW YOU GET IN, and is required on the paying call: pass the
    public half of your ssh key (one line, the contents of id_ed25519.pub). It is
    written into the rented container's authorized_keys and nowhere else, and the
    receipt comes back with the host and port to connect to. A block nobody can
    enter is not sold.

    `lease_id` is minted by the challenge — send back the one you were given; it
    is the accrual key for the daily fee cap and this station refuses ids it did
    not mint or that belong to another payer.

    `originator` is an OPTIONAL opaque attribution label (<=64 chars, e.g. a
    handle or a reverse-DNS name) naming the client implementation that produced
    the fill. It is carried unmodified onto the receipt and onto the public
    ledger row, and it never affects the price, the fee, verification or
    settlement — the same block costs the same either way.

    Returns the receipt on success. Every fill is published at /api/receipts.
    Wire contract: docs/X402-FEE-0.1.md, frozen as x402-fee/0.1.

    Note for x402 MCP-transport clients: this tool takes the payment as an
    ARGUMENT rather than in _meta["x402/payment"]. The payload is byte-identical;
    only the channel differs, because a tool argument is the one place every MCP
    client can portably put it. The HTTP rail is fully transport-conformant.

Input parameters:

- `blocks` (integer)
- `lease_id` (string)
- `originator` (string)
- `ssh_pubkey` (string)
- `x_payment` (string)

### `rent_offer` (~278 tokens)

Place a rental on YOUR provider account (BYO key — it is used for this
    one call and never stored). Default is a DRY RUN returning exactly what
    would be executed; a live placement needs dry_run=false AND confirm=true.
    The offer is re-quoted live first and refused if its price exceeds
    max_price_per_gpu_hr. Executes on vast and runpod offers. Pass an
    idempotency_key so retries return the first receipt instead of renting
    twice. auto_destroy_budget_usd arms the budget guard: this station then
    holds your key in PROCESS MEMORY ONLY and destroys the rental when
    estimated spend reaches the cap (a station restart drops the guard — the
    receipt says so; poll rental_status as backstop). account_token (from
    register_account) attributes the rental to your usage ledger.

Input parameters:

- `account_token` (string)
- `api_key` (string, required)
- `auto_destroy_budget_usd` (number)
- `confirm` (boolean)
- `disk_gb` (number)
- `dry_run` (boolean)
- `idempotency_key` (string)
- `image` (string)
- `label` (string)
- `max_price_per_gpu_hr` (number, required)
- `offer_id` (string, required)

### `rent_best` (~234 tokens)

One-shot rent: search the live book with these filters and place on the
    best (cheapest) matching offer — 'cheapest H100 under $2/hr, go'. Same
    guarantees as rent_offer (dry-run default, live re-quote, your
    max_price_per_gpu_hr is absolute). If the best offer is already gone it
    walks to the next, at most 3, and reports what it skipped.

Input parameters:

- `account_token` (string)
- `api_key` (string, required)
- `auto_destroy_budget_usd` (number)
- `confirm` (boolean)
- `country` (string)
- `disk_gb` (number)
- `dry_run` (boolean)
- `gpu` (string)
- `idempotency_key` (string)
- `image` (string)
- `label` (string)
- `max_price_per_gpu_hr` (number, required)
- `min_gpu_count` (integer)
- `min_vram_gb` (number)
- `offer_class` (string)
- `provider` (string)

### `rental_status` (~84 tokens)

Live state of an instance on your account: running/starting/stopped/
    gone, uptime, price, estimated spend so far, and the budget guard's state
    if one is armed. Read-only; your key passes through and is never stored.

Input parameters:

- `api_key` (string, required)
- `provider` (string, required)
- `provider_instance_id` (string, required)

### `destroy_rental` (~57 tokens)

Destroy an instance previously placed on your account (vast or runpod).
    Your key passes through and is never stored.

Input parameters:

- `api_key` (string, required)
- `provider` (string, required)
- `provider_instance_id` (string, required)

### `fill_limit_order` (~169 tokens)

Execute a limit order's live fill ticket on YOUR provider key (used for
    this one call, never stored). Only works while the order is ticketed; the
    offer is re-quoted live and refused above the order's line. Idempotent per
    order — a retry returns the first receipt rather than renting a second
    machine. The order's auto_destroy_budget_usd (if set) arms the budget
    guard exactly as rent_offer does.

Input parameters:

- `account_token` (string)
- `api_key` (string, required)
- `confirm` (boolean)
- `disk_gb` (number)
- `dry_run` (boolean)
- `image` (string)
- `order_id` (string, required)
- `order_secret` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/online-pangle-compute-gpu-rental-market/compute#diagnostics

## Score history

- 2026-09-20: 69
- 2026-09-19: 68
- 2026-09-18: 68
- 2026-09-17: 67
- 2026-09-16: 67
- 2026-09-15: 66
- 2026-09-14: 66
- 2026-09-13: 65
- 2026-09-12: 65
- 2026-09-11: 65
- 2026-09-10: 64
- 2026-09-09: 64
- 2026-09-08: 63
- 2026-09-07: 63
- 2026-09-06: 62
- 2026-09-05: 62
- 2026-09-04: 61
- 2026-09-03: 61
- 2026-09-02: 60
- 2026-09-01: 60
- 2026-08-31: 59
- 2026-08-30: 59
- 2026-08-29: 58
- 2026-08-28: 58

## Common questions

### What is the compute.pangle.online — GPU rental market MCP server?

compute.pangle.online — GPU rental market is an MCP server listed in the public MCP registry as online.pangle.compute/gpu-rental-market. Live GPU rental market: 2,500+ offers across a dozen provider feeds. History, watches, limit orders. This page covers its hosted endpoint (https://compute.pangle.online/mcp/).

### Is the compute.pangle.online — GPU rental market MCP server safe to use?

compute.pangle.online — GPU rental market scores 69 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.pangle.online — GPU rental market MCP server expose?

compute.pangle.online — GPU rental market exposes 25 tools: search_offers, get_offer, market_stats, price_history, idle_history, and 20 more. Their descriptions and schemas cost roughly 3,453 tokens of context every time the server is loaded.

### Does the compute.pangle.online — GPU rental market MCP server require authentication?

No. We connected to compute.pangle.online — GPU rental market without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the compute.pangle.online — GPU rental market MCP server still maintained?

compute.pangle.online — GPU rental market is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://compute.pangle.online/mcp/
- Repository: https://github.com/aitools420/compute-wick
- Website: https://compute.pangle.online/agents/
- Changelog RSS feed: https://verifymcp.io/servers/online-pangle-compute-gpu-rental-market/compute.xml
- Changelog JSON feed: https://verifymcp.io/servers/online-pangle-compute-gpu-rental-market/compute.json
- HTML version of this page: https://verifymcp.io/servers/online-pangle-compute-gpu-rental-market/compute