Skip to content

The White Report MCP server

io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/white-reportCYAN-ECLIPSE-TECHNOLOGIES-LLCstreamable-httpv0.1.2Scanned

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

12 tools: 5 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 5 write, 7 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the The White Report MCP server can do

The The White Report MCP server is published by the GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLC. It has 12 tools. It can create or change data (5 tools: calls_list, calls_get, calls_since, telemetry_latest and 1 more), but cannot delete data. 7 tools only read.

1 tool reads private data (event_briefs_list).

The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 0.1.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

12 tools

Changes things 5Claude Code: ask
  • calls_getMachine format (wr.calls.v1, testnet): the full sealed envelope for one call id (e.g.1 finding

    Why it is in this group

    • The name "calls_get" says "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "calls_get" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "calls_get" says "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get One Call (Machine Format)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • calls_listMachine format (wr.calls.v1, testnet): sealed per-call envelopes from the graded-calls ledger.1 finding

    Why it is in this group

    • The name "calls_list" says "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "calls_list" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "calls_list" says "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List Calls (Machine Format)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • calls_sinceMachine format (wr.calls.v1, testnet): call envelopes with published_at after the given ISO-8601 UTC timestamp (v1 basis: published_at).1 finding

    Why it is in this group

    • The name "calls_since" says "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "calls_since" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "calls_since" says "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Calls Since Timestamp (Machine Format)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • telemetry_latestMachine format (wr.telemetry.v1, testnet): the latest sealed compile envelope per telemetry metric; optional metric filter.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Latest Telemetry (Machine Format)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • telemetry_seriesMachine format (wr.telemetry.v1, testnet): every sealed compile envelope for one metric id, oldest first.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Telemetry Series (Machine Format)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 7Show 7 read-only tools
  • event_brief_getMachine format (wr.event.v1, testnet): one sealed event brief envelope by id; version optional (default: latest version).No findings

    Why it is in this group

    • The name "event_brief_get" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get Event Brief (Machine Format)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • event_briefs_listMachine format (wr.event.v1, testnet): the scheduled-event coverage calendar and brief index (id, version, event, sla_met).Reads private dataNo findings

    Why it is in this group

    • The name "event_briefs_list" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "calendar": it reads calendars.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List Event Briefs (Machine Format)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_articleFull machine-readable article (the JSON twin: facts, sources, call, full text).No findings

    Why it is in this group

    • The name "get_article" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get Article
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_latestNewest White Report articles (headline, summary, dates, URLs).No findings

    Why it is in this group

    • The name "get_latest" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get Latest Articles
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_scoreboardEvery dated public call The White Report has made, its grade date, and its grade (null while pending).No findings

    Why it is in this group

    • The name "get_scoreboard" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get Scoreboard
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_tickerMarket snapshot: crypto top 5, SI stocks, and metrics, with the snapshot timestamp.No findings

    Why it is in this group

    • The name "get_ticker" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get Market Ticker
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_articlesSearch the article archive by keyword (headline, summary, key facts, entities, tickers).No findings

    Why it is in this group

    • The name "search_articles" says "search": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Search Articles
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 16, 2026, 14:23 UTC, unchanged since Nov 2, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://thewhitereport.com/mcp.php: tools/list returned 12 tools to an anonymous client, including calls_list (write), calls_get (write), calls_since (write), telemetry_latest (write), telemetry_series (write)

    What this check looks for

Posture changes

  1. Nov 2, 2026
    • Tools that change things, listed without credentials: 0 to 5

Findings

Matches of fixed checks, with the text they matched.

3 warn
  • The server marks "calls_list" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "calls_list" says "call": a word for a change.

    What this check looks for
  • The server marks "calls_get" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "calls_get" says "call": a word for a change.

    What this check looks for
  • The server marks "calls_since" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "calls_since" says "call": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools7 added, 5 changed.+7 added~5 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 5.View diff
    • Tools that change things, listed without credentials: 0 to 5

Install

Pinned to version 0.1.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http white-report https://thewhitereport.com/mcp.php
claude mcp add --transport http white-report https://thewhitereport.com/mcp.php

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__white-report__get_latest",
      "mcp__white-report__search_articles",
      "mcp__white-report__get_article",
      "mcp__white-report__get_ticker",
      "mcp__white-report__get_scoreboard",
      "mcp__white-report__event_briefs_list",
      "mcp__white-report__event_brief_get"
    ],
    "ask": [
      "mcp__white-report__calls_list",
      "mcp__white-report__calls_get",
      "mcp__white-report__calls_since",
      "mcp__white-report__telemetry_latest",
      "mcp__white-report__telemetry_series"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as white-report. Review it before you use it.

Capability tags behind 1 rule
  • mcp__white-report__event_briefs_list private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/white-report/verify?hash=d003ab9be3722dcbedb8d5784a97eb72c307250bf242d0eb74f597cfdad033f7" | jq -e '.changed == false'

Pinned hash d003ab9be372, from Nov 9, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/white-report/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/white-report
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/white-report.svg)](https://radar.anlyon.com/servers/io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/white-report)

Source: MCP Registry · repository. Synced Nov 9, 2026, 04:17 UTC.

The White Report MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the The White Report MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 5 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the The White Report MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the The White Report MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the The White Report MCP server have?

12 tools: 5 write, 7 read. calls_list, calls_get, calls_since, telemetry_latest, telemetry_series, get_latest, search_articles, get_article and 4 more.

Does the The White Report MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the The White Report MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the The White Report MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.