compute.pangle.online — GPU rental market
REMOTE · COMPUTE.PANGLE.ONLINE · SCANNED SEP 20
Live GPU rental market: 2,500+ offers across a dozen provider feeds. History, watches, limit orders.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (4% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · compute.pangle.online
claude mcp add --transport http online-pangle-compute-gpu-rental-market 'https://compute.pangle.online/mcp/'
{
"mcpServers": {
"online-pangle-compute-gpu-rental-market": {
"url": "https://compute.pangle.online/mcp/"
}
}
} {
"servers": {
"online-pangle-compute-gpu-rental-market": {
"type": "http",
"url": "https://compute.pangle.online/mcp/"
}
}
} [mcp_servers.online-pangle-compute-gpu-rental-market] url = "https://compute.pangle.online/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"online-pangle-compute-gpu-rental-market": {
"type": "remote",
"url": "https://compute.pangle.online/mcp/",
"enabled": true
}
}
} openclaw mcp add online-pangle-compute-gpu-rental-market --url 'https://compute.pangle.online/mcp/' --transport streamable-http
mcp_servers:
online-pangle-compute-gpu-rental-market:
url: "https://compute.pangle.online/mcp/" {
"McpServers": {
"online-pangle-compute-gpu-rental-market": {
"Transport": "http",
"Url": "https://compute.pangle.online/mcp/"
}
}
} assistant mcp add online-pangle-compute-gpu-rental-market -t streamable-http -u 'https://compute.pangle.online/mcp/'
{
"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.
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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 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.
- 7 Sept 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.
- 5 Sept 26 +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.
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 20 Sept 2026 · Probed https://compute.pangle.online/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pangle.online | CN=WE1,O=Google Trust Services,C=US | 25 Aug 2026 | 23 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 101ac27c2e2c31c10e08d2b94105fe39 |
| SANs: pangle.online, *.pangle.online | ||||||
| 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 compute.pangle.online. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| online. | present | 30961 | 13 | Verified |
| pangle.online. | 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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://compute.pangle.online/mcp/ | Verified | 200 | |
| http (plaintext) | http://compute.pangle.online/mcp/ | HTTPS enforced | 301 | https://compute.pangle.online/mcp/ |
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 →
account_usage ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account_token | string | yes | – |
| days | integer | – | – |
No output schema declared.
No examples provided.
best_value ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| min_vram_gb | number | – | – |
| offer_class | string | – | – |
No output schema declared.
No examples provided.
cancel_limit_order ~39
Cancel a limit order. Requires the order_secret from create_limit_order.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
| order_secret | string | yes | – |
No output schema declared.
No examples provided.
create_limit_order ~498
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.
| Name | Type | Req | Description |
|---|---|---|---|
| age_alert_hours | number | – | – |
| auto_destroy_budget_usd | number | – | – |
| cooloff_seconds | integer | – | – |
| gpu | string | yes | – |
| max_price_per_gpu_hr | number | yes | – |
| max_refills | integer | – | – |
| min_gpu_count | integer | – | – |
| min_vram_gb | number | – | – |
| offer_class | string | – | – |
| spend_alert_usd | number | – | – |
| standing | boolean | – | – |
| webhook_url | string | – | – |
No output schema declared.
No examples provided.
create_watch ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| gpu | string | yes | – |
| max_price_per_gpu_hr | number | yes | – |
| offer_class | string | – | – |
| webhook_url | string | – | – |
No output schema declared.
No examples provided.
delete_watch ~22
Delete a watch by id.
| Name | Type | Req | Description |
|---|---|---|---|
| watch_id | string | yes | – |
No output schema declared.
No examples provided.
destroy_rental ~57
Destroy an instance previously placed on your account (vast or runpod). Your key passes through and is never stored.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | – |
| provider | string | yes | – |
| provider_instance_id | string | yes | – |
No output schema declared.
No examples provided.
fill_limit_order ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account_token | string | – | – |
| api_key | string | yes | – |
| confirm | boolean | – | – |
| disk_gb | number | – | – |
| dry_run | boolean | – | – |
| image | string | – | – |
| order_id | string | yes | – |
| order_secret | string | yes | – |
No output schema declared.
No examples provided.
get_offer ~28
Fetch one offer by its id (from search_offers).
| Name | Type | Req | Description |
|---|---|---|---|
| offer_id | string | yes | – |
No output schema declared.
No examples provided.
idle_history ~64
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].
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | – |
No output schema declared.
No examples provided.
limit_order_status ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
| order_secret | string | – | – |
No output schema declared.
No examples provided.
market_stats ~40
Live market snapshot: total offers, GPU models, idle-capacity share, per-provider freshness/health, cheapest price per model, current fee_bps.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
price_history ~122
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).
| Name | Type | Req | Description |
|---|---|---|---|
| gpu | string | – | – |
| gpu_model | string | – | – |
| hours | integer | – | – |
| offer_class | string | – | – |
No output schema declared.
No examples provided.
price_position ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| gpu | string | – | – |
| gpu_model | string | – | – |
| offer_class | string | – | – |
No output schema declared.
No examples provided.
provider_reliability ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
register_account ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | – |
No output schema declared.
No examples provided.
rent_best ~234
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account_token | string | – | – |
| api_key | string | yes | – |
| 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 | yes | – |
| min_gpu_count | integer | – | – |
| min_vram_gb | number | – | – |
| offer_class | string | – | – |
| provider | string | – | – |
No output schema declared.
No examples provided.
rent_offer ~278
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account_token | string | – | – |
| api_key | string | yes | – |
| 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 | yes | – |
| offer_id | string | yes | – |
No output schema declared.
No examples provided.
rent_x402 ~533
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.
| Name | Type | Req | Description |
|---|---|---|---|
| blocks | integer | – | – |
| lease_id | string | – | – |
| originator | string | – | – |
| ssh_pubkey | string | – | – |
| x_payment | string | – | – |
No output schema declared.
No examples provided.
rental_status ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | – |
| provider | string | yes | – |
| provider_instance_id | string | yes | – |
No output schema declared.
No examples provided.
search_offers ~206
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
spot_spread ~50
On-demand vs interruptible spread: the live discount for idle capacity per model; pass gpu_model for its history too.
| Name | Type | Req | Description |
|---|---|---|---|
| gpu_model | string | – | – |
| hours | integer | – | – |
No output schema declared.
No examples provided.
true_cost_notes ~106
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
watch_status ~43
Current state of a watch: armed/tripped, last price seen, recent events, and the best matching offer right now.
| Name | Type | Req | Description |
|---|---|---|---|
| watch_id | string | yes | – |
No output schema declared.
No examples provided.
will_it_fit ~262
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.
| Name | Type | Req | Description |
|---|---|---|---|
| batch | integer | – | – |
| context | integer | – | – |
| limit | integer | – | – |
| model | string | – | – |
| offer_class | string | – | – |
| params_b | number | – | – |
| precision | string | – | – |
| tokens_per_s | number | – | – |
No output schema declared.
No examples provided.
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.