# website.gexchange/compute-futures (remote · gexchange.website)

Trade GPU-hour futures on-chain. GEX-GCI index, $100 demo, no KYC, 9 tools.

- Trust score: 18/100 (low)
- Change this week: −40
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `gexchange.website`: 18/100 (this document), [markdown](https://verifymcp.io/servers/website-gexchange-compute-futures/gexchange.md), [page](https://verifymcp.io/servers/website-gexchange-compute-futures/gexchange)

## Channel facts

- Endpoint: `https://gexchange.website/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-11-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 530, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 530.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the website.gexchange/compute-futures MCP server?

website.gexchange/compute-futures is a hosted endpoint at https://gexchange.website/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 website-gexchange-compute-futures 'https://gexchange.website/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "website-gexchange-compute-futures": {
      "url": "https://gexchange.website/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "website-gexchange-compute-futures": {
      "type": "http",
      "url": "https://gexchange.website/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.website-gexchange-compute-futures]
url = "https://gexchange.website/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "website-gexchange-compute-futures": {
      "type": "remote",
      "url": "https://gexchange.website/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add website-gexchange-compute-futures --url 'https://gexchange.website/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  website-gexchange-compute-futures:
    url: "https://gexchange.website/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "website-gexchange-compute-futures": {
      "Transport": "http",
      "Url": "https://gexchange.website/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add website-gexchange-compute-futures -t streamable-http -u 'https://gexchange.website/mcp'
```

### Other

```json
{
  "mcpServers": {
    "website-gexchange-compute-futures": {
      "type": "http",
      "url": "https://gexchange.website/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-11-16 (score 18, −40)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] HTTPS: fail → unverified
- [security regression] Stability: 0.23 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-14 (score 58, +1)

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

### 2026-11-12 (score 57, +1)

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

### 2026-11-10 (score 56, +1)

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

### 2026-11-09 (score 55, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 55, +37)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: fair
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: pass

### 2026-11-07 (score 18)

First indexed and scored.

## MCP tools (9)

### `futures_index` (~28 tokens)

Query the GEX-GCI general compute futures index (HEH = H100-equivalent hour)

### `futures_trade` (~22 tokens)

Futures trading: open / close / close_all / quote / cancel

### `futures_mandate` (~29 tokens)

Create a mandate: a principal authorises an agent to trade within limits, never to withdraw

### `futures_open` (~22 tokens)

Open an account (no KYC, no email, no geography)

### `gpu_cheapest` (~16 tokens)

Cheapest GPU price across all venues

### `gpu_quote` (~20 tokens)

B2B bulk quote + 5% matching fee

### `exchange_book` (~21 tokens)

Matching order book (resting bids, asks and recent fills)

### `place_compute_order` (~20 tokens)

Place a compute bid (settled in USDC)

### `list_compute_offer` (~14 tokens)

Place a compute offer

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/website-gexchange-compute-futures/gexchange#diagnostics

## Score history

- 2026-11-21: 18
- 2026-11-20: 18
- 2026-11-19: 18
- 2026-11-18: 18
- 2026-11-17: 18
- 2026-11-16: 18
- 2026-11-15: 58
- 2026-11-14: 58
- 2026-11-13: 57
- 2026-11-12: 57
- 2026-11-11: 56
- 2026-11-10: 56
- 2026-11-09: 55
- 2026-11-08: 55
- 2026-11-07: 18

## Common questions

### What is the website.gexchange/compute-futures MCP server?

website.gexchange/compute-futures is an MCP server listed in the public MCP registry as website.gexchange/compute-futures. Trade GPU-hour futures on-chain. GEX-GCI index, $100 demo, no KYC, 9 tools. This page covers its hosted endpoint (https://gexchange.website/mcp).

### Is the website.gexchange/compute-futures MCP server safe to use?

website.gexchange/compute-futures scores 18 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 website.gexchange/compute-futures MCP server expose?

website.gexchange/compute-futures exposes 9 tools: futures_index, futures_trade, futures_mandate, futures_open, gpu_cheapest, and 4 more. Their descriptions and schemas cost roughly 192 tokens of context every time the server is loaded.

### Does the website.gexchange/compute-futures MCP server require authentication?

Its publisher declares no required credentials for website.gexchange/compute-futures. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the website.gexchange/compute-futures MCP server still maintained?

website.gexchange/compute-futures is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the website.gexchange/compute-futures MCP server?

VerifyMCP ran 4 checks on website.gexchange/compute-futures, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about website.gexchange/compute-futures: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://gexchange.website/mcp
- Website: https://gexchange.website/
- Changelog RSS feed: https://verifymcp.io/servers/website-gexchange-compute-futures/gexchange.xml
- Changelog JSON feed: https://verifymcp.io/servers/website-gexchange-compute-futures/gexchange/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/website-gexchange-compute-futures/gexchange.json
- HTML version of this page: https://verifymcp.io/servers/website-gexchange-compute-futures/gexchange
