_ registry / mcp streamable-http · checked 1h ago

CoinVerdict

https://mcp.coinverdict.io

Registry code: c2cf6036814acf7e

api record

Free AI crypto research verdicts from coinverdict.io: an AI analyst panel debates each major coin daily and issues a graded research verdict. Read-only, refreshed daily.

endpoint
https://mcp.coinverdict.io/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is CoinVerdict live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is CoinVerdict free to use?
Yes — the hub reached it with no key and no payment.
What tools does CoinVerdict have?
6 tools: get_verdict, get_track_record, get_receipts, get_kol_leaderboard, get_market_overview, list_coins.
Is CoinVerdict safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.7%· all time 99.7%

latency
713ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 394 checks · signed record
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • get daily ai research verdict for a coin
  • get market overview of coin verdicts
  • view verdict track record
  • see crypto influencer leaderboard
takes → gives
text → data
tools
6 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
4 open 2 never probed 4 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_receipts reads open 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "get_receiptsArguments",
      "properties": {}
    }
    arguments 5 lines
  • get_kol_leaderboard reads open 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "get_kol_leaderboardArguments",
      "properties": {}
    }
    arguments 5 lines
  • get_market_overview reads open 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "get_market_overviewArguments",
      "properties": {}
    }
    arguments 5 lines
  • list_coins reads open 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "list_coinsArguments",
      "properties": {}
    }
    arguments 5 lines
  • get_verdict reads unknown 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "get_verdictArguments",
      "required": [
        "symbol"
      ],
      "properties": {
        "symbol": {
          "type": "string",
          "title": "Symbol"
        }
      }
    }
    arguments 13 lines
  • get_track_record reads unknown 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "get_track_recordArguments",
      "required": [
        "symbol"
      ],
      "properties": {
        "symbol": {
          "type": "string",
          "title": "Symbol"
        }
      }
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c2cf6036814acf7e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c2cf6036814acf7e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c2cf6036814acf7e/badge.svg)](https://brick.blue/agent/c2cf6036814acf7e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.