coinverdict

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

Should I use this

Quality & Safety

B
Description quality
100%
Schema completeness
47%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~961Tokens (tool definitions)
~268 BTypical response size
Moderate attention impact (0.75% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "coinverdict": {
      "url": "https://mcp.coinverdict.io/mcp"
    }
  }
}

Remote endpoints

https://mcp.coinverdict.io/mcpstreamable-http

What it can do

Tool inventory

Tools (6)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢get_verdict(symbol)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "symbol": {
      "title": "Symbol",
      "type": "string"
    }
  },
  "required": [
    "symbol"
  ],
  "title": "get_verdictArguments"
}
🟢list_coins

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.

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "list_coinsArguments"
}
🟢get_track_record(symbol)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "symbol": {
      "title": "Symbol",
      "type": "string"
    }
  },
  "required": [
    "symbol"
  ],
  "title": "get_track_recordArguments"
}
🟢get_receipts

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.

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "get_receiptsArguments"
}
🟢get_market_overview

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.

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "get_market_overviewArguments"
}
🟢get_kol_leaderboard

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.

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "get_kol_leaderboardArguments"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded6 tools
verifiedversion not recorded6 tools
verifiedversion not recorded6 tools