# io.github.zerozaky/spoiler (remote · spoiler.bet)

Sealed prediction-market verdicts, graded in public across Polymarket and Kalshi. No auth required.

- Trust score: 57/100 (low)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `spoiler.bet`: 57/100 (this document), [markdown](https://verifymcp.io/servers/zerozaky-spoiler/spoiler.md), [page](https://verifymcp.io/servers/zerozaky-spoiler/spoiler)

## Channel facts

- Endpoint: `https://spoiler.bet/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 49/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 492 tokens (~41/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http zerozaky-spoiler https://spoiler.bet/mcp
```

### Codex

```toml
[mcp_servers.zerozaky-spoiler]
url = "https://spoiler.bet/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zerozaky-spoiler": {
      "type": "remote",
      "url": "https://spoiler.bet/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add zerozaky-spoiler --url https://spoiler.bet/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  zerozaky-spoiler:
    url: "https://spoiler.bet/mcp"
```

### Other

```json
{
  "mcpServers": {
    "zerozaky-spoiler": {
      "type": "http",
      "url": "https://spoiler.bet/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-08-03 (score 57, +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-08-01 (score 56, +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-07-31 (score 55, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 52, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 51, +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-07-27 (score 50, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 49)

First indexed and scored.

## MCP tools (12)

### `get_board` (~23 tokens)

Read public Spoiler receipts, public meter counts, and public methodology summary.

### `get_receipt` (~31 tokens)

Read one public receipt by event id, slug, or commit hash prefix.

Input parameters:

- `id` (string, required)

### `lookup_market` (~22 tokens)

Search public receipts by market text.

Input parameters:

- `query` (string, required)

### `paid_single_market_check` (~57 tokens)

Ask about any market: our call and edge if we have one, or why it was screened out. Price: 0.05 USDT per call, paid via x402 on X Layer.

Input parameters:

- `query` (string)

### `paid_spoiler_metrics` (~45 tokens)

Board-wide win rate, Brier and the graded record, by category. Price: 0.05 USDT per call, paid via x402 on X Layer.

### `paid_receipt_verify` (~46 tokens)

Check one public receipt and its onchain proof. Price: 0.10 USDT per call, paid via x402 on X Layer.

Input parameters:

- `id` (string)

### `paid_top_edges_now` (~41 tokens)

The five strongest open calls across the whole board right now. Price: 0.10 USDT per call, paid via x402 on X Layer.

### `paid_crypto_call_pack` (~41 tokens)

Every open crypto call on the board, with public receipts. Price: 0.10 USDT per call, paid via x402 on X Layer.

### `paid_esports_call_pack` (~42 tokens)

Every open esports call on the board, with public receipts. Price: 0.10 USDT per call, paid via x402 on X Layer.

### `paid_board_snapshot` (~45 tokens)

Get a board-wide snapshot of open calls and the public record, not one market. Price: 0.25 USDT per call, paid via x402 on X Layer.

### `paid_full_verdict` (~56 tokens)

One called market in full depth: side, edge, probability, timeline, and on-chain proof. Price: 1.00 USDT per call, paid via x402 on X Layer.

Input parameters:

- `query` (string)

### `paid_venue_gaps` (~43 tokens)

Compare current Kalshi and Polymarket prices ranked by gap. Price: 0.50 USDT per call, paid via x402 on X Layer.

## Diagnostics

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

## Score history

- 2026-08-03: 57
- 2026-08-02: 56
- 2026-08-01: 56
- 2026-07-31: 55
- 2026-07-30: 52
- 2026-07-29: 51
- 2026-07-28: 51
- 2026-07-27: 50
- 2026-07-26: 49

## Links

- Remote endpoint: https://spoiler.bet/mcp
- Website: https://spoiler.bet/
- Changelog RSS feed: https://verifymcp.io/servers/zerozaky-spoiler/spoiler/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/zerozaky-spoiler/spoiler/changelog.json
- HTML version of this page: https://verifymcp.io/servers/zerozaky-spoiler/spoiler