mcpField
C
compute.wick.pics

compute.wick.pics

Remote
compute.wick.picsCloud & Infra0Updated 9w ago

About compute.wick.pics

compute.wick.pics aggregates GPU spot offers from provider feeds and publishes ranked market data, history, and watches. It is for GPU renters and market researchers who want provider prices and availability in one place.

Key features

  1. 01Aggregated GPU spot offers
  2. 02Ranked REST API
  3. 03Price and idle history
  4. 04Watches and limit orders
  5. 05SQLite-backed provider health

Use cases

  1. 01Compare current GPU rental offers
  2. 02Review historical market prices
  3. 03Track providers with watches
  4. 04Run a self-hosted GPU market feed

MCP support

The service mounts an MCP server at `/mcp/` using Streamable HTTP. It exposes the aggregated GPU market data to MCP clients.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://compute.wick.pics/mcp/
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

25
ParameterTypeRequiredDescription
gpustringNo
limitintegerNo
regionstringNo
countrystringNo
providerstringNo
min_vram_gbnumberNo
offer_classstringNo
min_gpu_countintegerNo
min_reliabilitynumberNo
max_price_per_gpu_hrnumberNo

Details

From the project README

compute.pangle.online — GPU compute meta-aggregator

live H100 spot live RTX 4090 idle

One process: provider pollers + SQLite store + ranked REST API + MCP server + the site. Live at https://compute.pangle.online · API /api/offers, /api/history, /api/idle-history, /api/watches · MCP /mcp/ (streamable HTTP).

Run anywhere (the VPS lift)

docker compose up          # or:
python3 -m venv venv && venv/bin/pip install -r requirements.txt
venv/bin/uvicorn app:app --port 8956

No external services, no keys required (keys in .env deepen Vast/RunPod results; DataCrunch and Akash need none).

The fee levers — there are two, and confusing them corrupts the data

FEE_BPS (core/economics.py) marks up displayed prices, and it is 0, permanently. The book, the tape, the index and the per-chip prices are published as THE MARKET's numbers — check any of them against the provider's own page. A markup here would quietly make every published price ours instead of theirs, so this lever stays off.

EXEC_FEE_BPS is the platform fee, charged on what we settle, never on what the provider charges: 2.5%, one cent minimum, capped at $5 per lease per UTC day (core/meter.py). Renters place on their own provider key and pay the provider directly; this is the only thing we take, and it is disclosed in the quote and the receipt before anything is placed.

REF_VAST / REF_RUNPOD referral slots ride the same seam.

Layout

providers/ one drop-in module per marketplace · core/ schema, rank, economics, stats · db.py SQLite (WAL) with provider_health honesty table · app.py FastAPI + scheduler + MCP mount · web/ the hand-written site (see DESIGN-DIRECTION.md).

Tests: venv/bin/python -m tests.test_pipeline

Generated pages

web/gpu/, web/vs/ and web/sitemap.xml are built artifacts — regenerate with venv/bin/python gen_gpu_pages.py (the deployment runs it hourly).

Fonts

Martian Mono ships in web/fonts/ (SIL OFL). The display serif (Erode, by Indian Type Foundry via Fontshare) is not redistributed here — its license doesn't allow it; fetch it from https://www.fontshare.com/fonts/erode into web/fonts/ as erode-400.woff2 / erode-600.woff2, or let the stack fall back to Georgia.

License

AGPL-3.0 — see LICENSE. Run it, fork it, learn from it; if you serve a modified version, share your changes the same way.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.