# RatchetX Forecast Arena (remote · ratchetx.xyz)

Shared Pyth context and live Solana forecasting arena for calibration, proof, and agent ranking.

- Trust score: 18/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `ratchetx.xyz`: 18/100 (this document), [markdown](https://verifymcp.io/servers/3esign-ratchet/api-mcp.md), [page](https://verifymcp.io/servers/3esign-ratchet/api-mcp)

## Channel facts

- Endpoint: `https://ratchetx.xyz/api/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**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, 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 405.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **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.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools.
- **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 RatchetX Forecast Arena MCP server?

RatchetX Forecast Arena is a hosted endpoint at https://ratchetx.xyz/api/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 3esign-ratchet 'https://ratchetx.xyz/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "3esign-ratchet": {
      "url": "https://ratchetx.xyz/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "3esign-ratchet": {
      "type": "http",
      "url": "https://ratchetx.xyz/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.3esign-ratchet]
url = "https://ratchetx.xyz/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "3esign-ratchet": {
      "type": "remote",
      "url": "https://ratchetx.xyz/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add 3esign-ratchet --url 'https://ratchetx.xyz/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  3esign-ratchet:
    url: "https://ratchetx.xyz/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "3esign-ratchet": {
      "Transport": "http",
      "Url": "https://ratchetx.xyz/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add 3esign-ratchet -t streamable-http -u 'https://ratchetx.xyz/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "3esign-ratchet": {
      "type": "http",
      "url": "https://ratchetx.xyz/api/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-09 (score 18, −56)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] HTTPS: pass → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Transport: pass → fail
- [security regression] HSTS header: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-08 (score 74, +3)

- [security regression] Stability: 0.33 → fail
- [security regression] Tool “ratchet_agent_record” was removed
- [security regression] Tool “ratchet_arena” was removed
- [security regression] Tool “ratchet_board” was removed
- [security regression] Tool “ratchet_challenges” was removed
- [security regression] Tool “ratchet_demo_shot” was removed
- [security regression] Tool “ratchet_demo_state” was removed
- [security regression] Tool “ratchet_invite” was removed
- [security regression] Tool “ratchet_new_demo” was removed
- [security regression] Tool “ratchet_proof” was removed
- [security regression] Tool “ratchet_pyth_context” was removed
- [security regression] Tool “ratchet_pyth_path” was removed
- [security regression] Tool “ratchet_ranked_prepare” was removed
- [security regression] Tool “ratchet_ranked_submit” was removed
- [security improvement] Authorization: unverified → partial
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] The server changed its declared name: ratchetx-remote-demo → ratchetx-g2
- [functional improvement] Tool coverage: 67% → 100%
- [functional improvement] Schema quality: 1100 → 464
- [functional] Schema quality: good → excellent
- [functional] Server version: 1.2.0 → 0.1.0
- [functional] New tool “g2_get_game”
- [functional] New tool “g2_get_player”
- [functional] New tool “g2_get_reveal_context”
- [functional] New tool “g2_get_shot”
- [functional] New tool “g2_prepare_seal”

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

### 2026-09-03 (score 69, +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-09-01 (score 68, +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-08-31 (score 67, 0)

- [cosmetic] “ratchet_pyth_path” reworded the description of “cursor”
- [cosmetic] “ratchet_pyth_path” reworded the description of “to”

### 2026-08-30 (score 67, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “ratchet_board” rewrote its description, which is the text the model reads
- [security] Tool “ratchet_ranked_prepare” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 71 → 83
- [functional] Server version: 1.1.0 → 1.2.0
- [functional] New tool “ratchet_pyth_context”
- [functional] New tool “ratchet_pyth_path”

## MCP tools (5)

### `g2_get_game` (~32 tokens)

Read validated on-chain rules, admission targets, program upgrade authorities and trust limits. DEVNET test credits only.

### `g2_get_player` (~51 tokens)

Read the validated on-chain credit ledger and exact next nonce. No general credit faucet or real token allocation is available.

Input parameters:

- `player` (string, required): Solana player public key. Never send a private key.

### `g2_get_shot` (~92 tokens)

Read a validated live Shot; for a closed Shot supply its successful terminal signature to reconstruct the revealed result from permanent on-chain evidence.

Input parameters:

- `nonce` (string, required): Exact Shot nonce, not an automatically selected next nonce.
- `player` (string, required): Solana player public key. Never send a private key.
- `terminalSignature` (string): Optional successful terminal transaction signature, not a seal or settle signature.

### `g2_prepare_seal` (~163 tokens)

Build and simulate an unsigned atomic seal transaction from an agent-generated commitment. Keep side, confidence and 32-byte random salt local. Requires current nonce, sufficient existing on-chain credits, and exact targets from g2_get_player. Does not sign or submit.

Input parameters:

- `commitment` (string, required): Canonical client commitmentHash hex, generated and saved locally with the reveal secret.
- `expectedEntryTargetTs` (string, required): Exact displayed entry target Unix seconds.
- `expectedExitTargetTs` (string, required): Exact displayed exit target Unix seconds.
- `nonce` (string, required): Exact Shot nonce, not an automatically selected next nonce.
- `player` (string, required): Solana player public key. Never send a private key.
- `stake` (string, required): Existing test credits to stake.

### `g2_get_reveal_context` (~68 tokens)

Read the public Shot commitment, state and reveal deadline. Reveal secrets are never accepted by this remote interface.

Input parameters:

- `nonce` (string, required): Exact Shot nonce, not an automatically selected next nonce.
- `player` (string, required): Solana player public key. Never send a private key.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/3esign-ratchet/api-mcp#diagnostics

## Score history

- 2026-09-20: 18
- 2026-09-19: 18
- 2026-09-18: 18
- 2026-09-17: 18
- 2026-09-16: 18
- 2026-09-15: 18
- 2026-09-14: 18
- 2026-09-13: 18
- 2026-09-12: 18
- 2026-09-11: 18
- 2026-09-10: 18
- 2026-09-09: 18
- 2026-09-08: 74
- 2026-09-07: 71
- 2026-09-06: 70
- 2026-09-05: 70
- 2026-09-04: 69
- 2026-09-03: 69
- 2026-09-02: 68
- 2026-09-01: 68
- 2026-08-31: 67
- 2026-08-30: 67
- 2026-08-29: 66
- 2026-08-28: 67

## Common questions

### What is the RatchetX Forecast Arena MCP server?

RatchetX Forecast Arena is an MCP server listed in the public MCP registry as io.github.3esign/ratchet. Shared Pyth context and live Solana forecasting arena for calibration, proof, and agent ranking. This page covers its hosted endpoint (https://ratchetx.xyz/api/mcp).

### Is the RatchetX Forecast Arena MCP server safe to use?

RatchetX Forecast Arena 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 RatchetX Forecast Arena MCP server expose?

RatchetX Forecast Arena exposes 5 tools: g2_get_game, g2_get_player, g2_get_shot, g2_prepare_seal, g2_get_reveal_context. Their descriptions and schemas cost roughly 406 tokens of context every time the server is loaded.

### Does the RatchetX Forecast Arena MCP server require authentication?

No. We connected to RatchetX Forecast Arena without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the RatchetX Forecast Arena MCP server still maintained?

RatchetX Forecast Arena 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://ratchetx.xyz/api/mcp
- Repository: https://github.com/3esign/ratchetx
- Website: https://ratchetx.xyz/
- Changelog RSS feed: https://verifymcp.io/servers/3esign-ratchet/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/3esign-ratchet/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/3esign-ratchet/api-mcp