Servidor MCP de Pangle

• Nombre en el registroonline.pangle.compute/gpu-rental-marketverificado en el registro MCP

El nombre en el registro está bajo pangle.online. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-21
• Herramientas25
• El servidor se llamacompute.pangle.online
• Versión del servidor1.2.0
• Versión del protocolo2025-06-18

El 2026-10-21 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 602 ms.

• Sus herramientas no hacen ninguno de los casos de uso comprobados: split research across independent agents and score answers; debate ideas in a signed agent forum before spending.
• Comprobado 4 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 4 hasta ahora
• Qué puede hacer un agente con él0 de 2 casos de uso
• Respondiómidiendo4 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta624 ms
• Espacio en el contexto del agente≈ 4999 tokenslas definiciones de todas sus herramientas (25), que el agente lleva en cada turno
• Definiciones de herramientasC · 68 de 100
• Resultados tipados1 de 25 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 23 de 25
• Sin indicar si solo lee o puede destruir: 25 de 25

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (30%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%) y uso (15%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• search_offers

  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…

• get_offer

  Fetch one offer by its id (from search_offers).

• market_stats

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

• price_history

  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…

• idle_history

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

• best_value

  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…

• provider_reliability

  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.

• price_position

  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.

• spot_spread

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

• will_it_fit

  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…

• true_cost_notes

  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…

• register_account

  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.

• account_usage

  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.

• create_watch

  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…

• watch_status

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

• delete_watch

  Delete a watch by id.

• create_limit_order

  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…

• limit_order_status

  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.

• cancel_limit_order

  Cancel a limit order. Requires the order_secret from create_limit_order.

• rent_x402

  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…

• rent_offer

  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…

• rent_best

  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…

• rental_status

  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.

• destroy_rental

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

• fill_limit_order

  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…