# The White Report (remote · thewhitereport.com)

The White Report news archive: crypto and AI stories, search, full text, ticker, graded calls.

- Trust score: 73/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `thewhitereport.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/cyan-eclipse-technologies-llc-white-report/mcp-php.md), [page](https://verifymcp.io/servers/cyan-eclipse-technologies-llc-white-report/mcp-php)

## Channel facts

- Endpoint: `https://thewhitereport.com/mcp.php`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.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-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 906 tokens (~75/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the The White Report MCP server?

The White Report is a hosted endpoint at https://thewhitereport.com/mcp.php, 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 cyan-eclipse-technologies-llc-white-report 'https://thewhitereport.com/mcp.php'
```

### Cursor

```json
{
  "mcpServers": {
    "cyan-eclipse-technologies-llc-white-report": {
      "url": "https://thewhitereport.com/mcp.php"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cyan-eclipse-technologies-llc-white-report": {
      "type": "http",
      "url": "https://thewhitereport.com/mcp.php"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cyan-eclipse-technologies-llc-white-report]
url = "https://thewhitereport.com/mcp.php"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyan-eclipse-technologies-llc-white-report": {
      "type": "remote",
      "url": "https://thewhitereport.com/mcp.php",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cyan-eclipse-technologies-llc-white-report --url 'https://thewhitereport.com/mcp.php' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cyan-eclipse-technologies-llc-white-report:
    url: "https://thewhitereport.com/mcp.php"
```

### Netclaw

```json
{
  "McpServers": {
    "cyan-eclipse-technologies-llc-white-report": {
      "Transport": "http",
      "Url": "https://thewhitereport.com/mcp.php"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cyan-eclipse-technologies-llc-white-report -t streamable-http -u 'https://thewhitereport.com/mcp.php'
```

### Other

```json
{
  "mcpServers": {
    "cyan-eclipse-technologies-llc-white-report": {
      "type": "http",
      "url": "https://thewhitereport.com/mcp.php"
    }
  }
}
```

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-05 (score 73, +1)

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

### 2026-11-03 (score 72, −4)

- [security regression] HTTPS: pass → fail

### 2026-11-02 (score 76, +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-10-30 (score 75, +3)

- [security] Tool “calls_get” rewrote its description, which is the text the model reads
- [security] Tool “calls_list” rewrote its description, which is the text the model reads
- [security] Tool “calls_since” rewrote its description, which is the text the model reads
- [security] Tool “event_brief_get” rewrote its description, which is the text the model reads
- [security] Tool “event_briefs_list” rewrote its description, which is the text the model reads
- [security] Tool “get_article” rewrote its description, which is the text the model reads
- [security] Tool “get_latest” rewrote its description, which is the text the model reads
- [security] Tool “get_scoreboard” rewrote its description, which is the text the model reads
- [security] Tool “get_ticker” rewrote its description, which is the text the model reads
- [security] Tool “search_articles” rewrote its description, which is the text the model reads
- [security] Tool “telemetry_latest” rewrote its description, which is the text the model reads
- [security] Tool “telemetry_series” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 49 → 75
- [functional] Schema quality: good → excellent
- [cosmetic] “calls_get” reworded the description of “call_id”
- [cosmetic] “event_brief_get” reworded the description of “id”
- [cosmetic] “get_article” reworded the description of “slug”
- [cosmetic] “telemetry_latest” reworded the description of “metric”
- [cosmetic] “telemetry_series” reworded the description of “metric”

### 2026-10-29 (score 72, 0)

- [functional regression] Schema quality: 39 → 49
- [functional] New tool “calls_get”
- [functional] New tool “calls_list”
- [functional] New tool “calls_since”
- [functional] New tool “event_brief_get”
- [functional] New tool “event_briefs_list”
- [functional] New tool “telemetry_latest”
- [functional] New tool “telemetry_series”

### 2026-10-28 (score 72, +1)

- [security] Tool “get_ticker” rewrote its description, which is the text the model reads

### 2026-10-26 (score 71, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-25 (score 70)

First indexed and scored.

## MCP tools (12)

### `get_latest` (~74 tokens)

Get Latest Articles

Newest White Report articles (headline, summary, dates, URLs). Start here for the newest coverage; use search_articles instead when you have a topic or keyword, and get_article for one article's full text once you have its slug.

Input parameters:

- `limit` (integer): How many articles (1-20, default 5).

### `search_articles` (~84 tokens)

Search Articles

Search the article archive by keyword (headline, summary, key facts, entities, tickers). Use get_latest instead for the newest articles without a query; open a hit's full text with get_article (the slug comes from the search results).

Input parameters:

- `limit` (integer): Max results (1-20, default 10).
- `query` (string, required): Keyword or phrase.

### `get_article` (~69 tokens)

Get Article

Full machine-readable article (the JSON twin: facts, sources, call, full text). Use search_articles or get_latest first if you do not have a slug.

Input parameters:

- `slug` (string, required): Article slug, as returned by search_articles or get_latest, e.g. institutions-sold-the-dip.

### `get_ticker` (~44 tokens)

Get Market Ticker

Market snapshot: crypto top 5, SI stocks, and metrics, with the snapshot timestamp. For the publication's dated predictions and their grades, use get_scoreboard instead.

### `get_scoreboard` (~63 tokens)

Get Scoreboard

Every dated public call The White Report has made, its grade date, and its grade (null while pending). Start here for the track record in human-readable form; use calls_list instead for the sealed machine-format envelopes (wr.calls.v1) behind the same calls.

### `calls_list` (~122 tokens)

List Calls (Machine Format)

Machine format (wr.calls.v1, testnet): sealed per-call envelopes from the graded-calls ledger. Optional filters: state (grade_state), asset (substring of asset_or_event). Historical record only. Use calls_get for one call's full envelope once you have its call_id, calls_since to sync only what is new, and get_scoreboard instead for the human-readable track record.

Input parameters:

- `asset` (string): Substring match on asset_or_event, e.g. BTC.
- `state` (string): Filter by grade_state, e.g. OPEN.

### `calls_get` (~74 tokens)

Get One Call (Machine Format)

Machine format (wr.calls.v1, testnet): the full sealed envelope for one call id (e.g. ep.6). Use calls_list first if you do not have a call_id.

Input parameters:

- `call_id` (string, required): Call id, as returned by calls_list or calls_since, e.g. ep.6.

### `calls_since` (~89 tokens)

Calls Since Timestamp (Machine Format)

Machine format (wr.calls.v1, testnet): call envelopes with published_at after the given ISO-8601 UTC timestamp (v1 basis: published_at). Use calls_list instead when you need state/asset filters rather than a time window.

Input parameters:

- `since` (string, required): ISO-8601 UTC timestamp, e.g. 2026-10-24T00:00:00Z.

### `event_briefs_list` (~57 tokens)

List Event Briefs (Machine Format)

Machine format (wr.event.v1, testnet): the scheduled-event coverage calendar and brief index (id, version, event, sla_met). Use event_brief_get for one brief's full sealed envelope once you have its id.

### `event_brief_get` (~82 tokens)

Get Event Brief (Machine Format)

Machine format (wr.event.v1, testnet): one sealed event brief envelope by id; version optional (default: latest version). Use event_briefs_list first if you do not have a brief id.

Input parameters:

- `id` (string, required): Brief id, as returned by event_briefs_list.
- `version` (integer): Version number; omit for latest.

### `telemetry_latest` (~75 tokens)

Latest Telemetry (Machine Format)

Machine format (wr.telemetry.v1, testnet): the latest sealed compile envelope per telemetry metric; optional metric filter. Use telemetry_series instead for every envelope of one metric over time.

Input parameters:

- `metric` (string): Metric id, as enumerated by this tool when metric is omitted; omit for the latest envelope of every metric.

### `telemetry_series` (~73 tokens)

Telemetry Series (Machine Format)

Machine format (wr.telemetry.v1, testnet): every sealed compile envelope for one metric id, oldest first. Use telemetry_latest instead when you only need the newest envelope per metric.

Input parameters:

- `metric` (string, required): Metric id, as enumerated by telemetry_latest (call it with metric omitted to list all metric ids).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-white-report/mcp-php#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 76
- 2026-11-01: 75
- 2026-10-31: 75
- 2026-10-30: 75
- 2026-10-29: 72
- 2026-10-28: 72
- 2026-10-27: 71
- 2026-10-26: 71
- 2026-10-25: 70

## Common questions

### What is the The White Report MCP server?

The White Report is an MCP server listed in the public MCP registry as io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/white-report. The White Report news archive: crypto and AI stories, search, full text, ticker, graded calls. This page covers its hosted endpoint (https://thewhitereport.com/mcp.php).

### Is the The White Report MCP server safe to use?

The White Report scores 73 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 The White Report MCP server expose?

The White Report exposes 12 tools: get_latest, search_articles, get_article, get_ticker, get_scoreboard, and 7 more. Their descriptions and schemas cost roughly 906 tokens of context every time the server is loaded.

### Does the The White Report MCP server require authentication?

No. We connected to The White Report without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the The White Report MCP server still maintained?

The White Report is still listed as active in the MCP registry. We last reached this channel on 5 November 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://thewhitereport.com/mcp.php
- Repository: https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/white-report-mcp
- Website: https://thewhitereport.com/agents
- Changelog RSS feed: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-white-report/mcp-php.xml
- Changelog JSON feed: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-white-report/mcp-php.json
- HTML version of this page: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-white-report/mcp-php