Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

The White Report

REMOTE · THEWHITEREPORT.COM

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

+1 this week 73 Trust /100

Last scanned (2 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 5 Nov 2026.

Category News and Social

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 906 tokens (~75/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +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.

  • 3 Nov 26 −4
    • HTTPS: pass → fail ▼ security
  • 2 Nov 26 +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.

  • 30 Oct 26 +3
    • 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 security
    • Schema quality: 49 → 75 ▼ functional
    • Schema quality: good → excellent functional
    • “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” cosmetic
  • 29 Oct 26 0
    • 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” functional
  • 28 Oct 26 +1
    • Tool “get_ticker” rewrote its description, which is the text the model reads security
  • 26 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 25 Oct 26 70

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://thewhitereport.com/mcp.php

TLS valid

Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=thewhitereport.com CN=ZeroSSL RSA DV SSL CA 2,O=ZeroSSL GmbH,C=AT 24 Oct 2026 22 Jan 2027 RSA 2048 SHA256-RSA e7f67b250806c666281f21c6e383880a
SANs: thewhitereport.com, www.thewhitereport.com
CN=ZeroSSL RSA DV SSL CA 2,O=ZeroSSL GmbH,C=AT (CA) CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB 24 Sept 2025 23 Sept 2035 RSA 3072 SHA384-RSA d0a908255f8e50e5f3396d1114702a37

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of thewhitereport.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
thewhitereport.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://thewhitereport.com/mcp.php Verified 200
http (plaintext) http://thewhitereport.com/mcp.php Served over HTTP 200
MCP tools · 12 exposed · ~906 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
calls_get ~74

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.

NameTypeReqDescription
call_idstringyesCall id, as returned by calls_list or calls_since, e.g. ep.6.

No output schema declared.

No examples provided.

calls_list ~122

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.

NameTypeReqDescription
assetstring–Substring match on asset_or_event, e.g. BTC.
statestring–Filter by grade_state, e.g. OPEN.

No output schema declared.

No examples provided.

calls_since ~89

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.

NameTypeReqDescription
sincestringyesISO-8601 UTC timestamp, e.g. 2026-10-24T00:00:00Z.

No output schema declared.

No examples provided.

event_brief_get ~82

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.

NameTypeReqDescription
idstringyesBrief id, as returned by event_briefs_list.
versioninteger–Version number; omit for latest.

No output schema declared.

No examples provided.

event_briefs_list ~57

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_article ~69

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.

NameTypeReqDescription
slugstringyesArticle slug, as returned by search_articles or get_latest, e.g. institutions-sold-the-dip.

No output schema declared.

No examples provided.

get_latest ~74

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.

NameTypeReqDescription
limitinteger–How many articles (1-20, default 5).

No output schema declared.

No examples provided.

get_scoreboard ~63

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_ticker ~44

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_articles ~84

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).

NameTypeReqDescription
limitinteger–Max results (1-20, default 10).
querystringyesKeyword or phrase.

No output schema declared.

No examples provided.

telemetry_latest ~75

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.

NameTypeReqDescription
metricstring–Metric id, as enumerated by this tool when metric is omitted; omit for the latest envelope of every metric.

No output schema declared.

No examples provided.

telemetry_series ~73

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.

NameTypeReqDescription
metricstringyesMetric id, as enumerated by telemetry_latest (call it with metric omitted to list all metric ids).

No output schema declared.

No examples provided.

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.

remote · thewhitereport.com

# add to Claude Code
claude mcp add --transport http cyan-eclipse-technologies-llc-white-report 'https://thewhitereport.com/mcp.php'
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.