Skip to content

coinverdict MCP server

io.github.OCArk/coinverdictOCArkstreamable-httpv1.0.0Scanned

Free daily AI crypto research verdicts: graded stance, dimensions, and key levels for 67+ coins.

6 tools: 6 only read.

Tools: 0 delete, 0 irreversible, 0 write, 6 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • 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 coinverdict MCP server can do

The coinverdict MCP server is published by the GitHub account OCArk. It has 6 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 1.0.0.

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.

6 tools

Only reads 6Show 6 read-only tools
  • get_kol_leaderboardGet the KOL settlement leaderboard: crypto influencers ranked by their SETTLED hit rate (from VeraMind's ledger of public calls graded after the fact — misses count).No findings

    Why it is in this group

    • The name "get_kol_leaderboard" says "get": a word for reading.
    Description, as the server wrote it
    Get the KOL settlement leaderboard: crypto influencers ranked by their SETTLED hit rate (from VeraMind's ledger of public calls graded after the fact — misses count). CoinVerdict-exclusive data. Returns {ranked:[{author,hit_rate_pct,n_verified,coins,n_total, n_prospective,hits_prospective,prospective_rate_pct, n_retrospective,hits_retrospective,retrospective_rate_pct}], building:[...], as_of, rule}. Rates are graded under rule kol_directional_v1: did the direction hold over a 7-day window, with a ±3% band, altcoins scored against BTC and BTC against USD — identical parameters to the settle_v1 rule CoinVerdict scores its own verdicts with. Always report the `rule` field alongside any number you quote; if it reads price_target_v1, the board fell back to price-target records and the numbers mean "did the stated price target print?" instead. Prospective (called before the fact) and backtested (graded from history) records are scored as separate lines and MUST NOT be averaged together; hit_rate_pct/n_verified are the prospective line, n_total is the combined sample size used for ranking eligibility. A null rate means no samples of that kind — report it as n=0, never as 0%. Free, read-only, not advice.
  • get_market_overviewGet today's verdict for ALL covered coins in one call — the full docket: each coin's current stance (overweight/neutral/underweight), price, and W/L/P settled record.No findings

    Why it is in this group

    • The name "get_market_overview" says "get": a word for reading.
    Description, as the server wrote it
    Get today's verdict for ALL covered coins in one call — the full docket: each coin's current stance (overweight/neutral/underweight), price, and W/L/P settled record. Use this to scan the whole market at once instead of calling get_verdict per coin. Returns {coins:[{symbol,stance,price_usd,board}], as_of}. Free, read-only, not advice.
  • get_receiptsGet CoinVerdict's overall settled scoreboard across all coins: directional win rate, wins/losses/pushes, neutral (no-call) count, and how many calls are still open.No findings

    Why it is in this group

    • The name "get_receipts" says "get": a word for reading.
    Description, as the server wrote it
    Get CoinVerdict's overall settled scoreboard across all coins: directional win rate, wins/losses/pushes, neutral (no-call) count, and how many calls are still open. Every verdict is graded 7 days later against BTC. Returns {board:{winrate,W,L,P,decided,neu}, since, open_calls}. Free, read-only.
  • get_track_recordGet the SETTLED track record for a coin — CoinVerdict's differentiator.No findings

    Why it is in this group

    • The name "get_track_record" says "get": a word for reading.
    Description, as the server wrote it
    Get the SETTLED track record for a coin — CoinVerdict's differentiator. Every past daily verdict is scored 7 days later against BTC: win, loss, or push. Returns the coin's W/L/P scoreboard plus recent settled calls (date, stance, 7d-vs-BTC return, outcome). This is the receipts: misses included, never edited. Args: symbol e.g. "BTC". Free, read-only, not advice.
  • get_verdictGet today's research verdict for a coin (e.g.No findings

    Why it is in this group

    • The name "get_verdict" says "get": a word for reading.
    Description, as the server wrote it
    Get today's research verdict for a coin (e.g. BTC, ETH, SOL): stance (overweight/neutral/underweight), graded dimensions (technical/sentiment/funding/KOL), key levels, and a link to the full dossier. Refreshed daily; free; not investment advice.
  • list_coinsList every coin symbol CoinVerdict covers with a daily research verdict (100 major crypto assets: BTC, ETH, SOL, …).No findings

    Why it is in this group

    • The name "list_coins" says "list": a word for reading.
    Description, as the server wrote it
    List every coin symbol CoinVerdict covers with a daily research verdict (100 major crypto assets: BTC, ETH, SOL, …). Use this to discover which symbols get_verdict / get_track_record accept. Returns {coins: [SYM,...], count: int, site: url}. Free, read-only.

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 private-data or untrusted-input or outbound.

Reads private data0
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 20, 2026, 18:59 UTC, unchanged since Oct 22, 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
0
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

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http coinverdict https://mcp.coinverdict.io/mcp
claude mcp add --transport http coinverdict https://mcp.coinverdict.io/mcp

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__coinverdict__get_verdict",
      "mcp__coinverdict__list_coins",
      "mcp__coinverdict__get_track_record",
      "mcp__coinverdict__get_receipts",
      "mcp__coinverdict__get_market_overview",
      "mcp__coinverdict__get_kol_leaderboard"
    ],
    "ask": [],
    "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 coinverdict. Review it before you use it.

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.OCArk/coinverdict/verify?hash=03caf146dbdfd6b00d1fa93c83edd89aa832be911d54bbf5c644d6def1333c2c" | jq -e '.changed == false'

Pinned hash 03caf146dbdf, from Nov 16, 2026, 02: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.OCArk/coinverdict/changes.xml

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

Badge

Anlyon Radar badge for io.github.OCArk/coinverdict
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.OCArk/coinverdict.svg)](https://radar.anlyon.com/servers/io.github.OCArk/coinverdict)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:18 UTC.

coinverdict MCP server: questions and answers

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

Is the coinverdict MCP server safe?

No scan can promise that. What its definitions show: 6 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the coinverdict MCP server delete data?

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

Can the coinverdict 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 coinverdict MCP server have?

6 tools: 6 read. get_verdict, list_coins, get_track_record, get_receipts, get_market_overview and get_kol_leaderboard.

Does the coinverdict MCP server need sign-in or OAuth?

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

Does the coinverdict MCP server send data to outside services?

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

Has the coinverdict MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.