_ registry / mcp streamable-http · checked 8m ago

cryptoquant-analyst-consensus

https://consensus.cryptoquant.com

Registry code: 66ce942699b4b0c4

api record

CryptoQuant Analyst Consensus: what tracked professional analysts (X, CryptoQuant QuickTake, Seeking Alpha, Substack) are saying about a crypto asset, US / KR stock, index ETF or commodity — the daily Analyst Consensus Index (−100 … +100), the 30-day bullish / bearish split, the bull and bear case, the dominant narratives, each analyst's quotable view and verified accuracy track record.

Use get_consensus when a user asks what analysts / experts / the market think about an asset or whether sentiment is bullish or bearish; get_analyst_views for WHAT they are saying (narratives, quotes);…

endpoint
https://consensus.cryptoquant.com/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 cryptoquant-analyst-consensus live?
Yes — it answered the hub's last check (checked 8m ago). It answered 100% of checks over the last 30 days.
Is cryptoquant-analyst-consensus free to use?
Yes — the hub reached it with no key and no payment.
What tools does cryptoquant-analyst-consensus have?
5 tools: get_analyst_views, get_consensus, get_recent_calls, get_analyst_profile, get_top_analysts.
Is cryptoquant-analyst-consensus 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.6%· all time 99.6%

latency
587ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 255 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • get analyst consensus on an asset
  • see bull and bear case for a crypto asset
  • rank analysts by accuracy
takes → gives
text → data
tools
5 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 5 tools
1 open 4 never probed 1 of 5 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_top_analysts reads open 10h ago

    The asset's analysts ranked by verified accuracy (directional calls scored against subsequent price; active in the last three months) with the accuracy badge, sample size, bull / bear-phase scores, current bias and profile_url. Use when a user asks whose crypto / stock call to trust or who the best Bitcoin analysts are, and before quoting any single analyst. Accuracy scoring covers crypto today; for stocks / ETFs the active analysts are listed with scores null — never substitute a number. Data by CryptoQuant Consensus.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "asset": {
          "type": "string",
          "default": "BTC",
          "maxLength": 40,
          "minLength": 1,
          "description": "Ticker, route key or name — BTC, bitcoin, ETH, SOL, NVDA, TSLA, SPY, GLD, 005930 …"
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1,
          "description": "How many analysts (1–50, default 10)"
        }
      }
    }
    arguments 20 lines
  • get_analyst_views reads unknown 10h ago

    The narratives analysts back on ONE asset (viewpoints grouped by thesis, with analyst counts) and the per-analyst views — each analyst's stance, thesis and one quotable excerpt with its source link and profile page — plus the bull / bear case. Use for "what are analysts saying about SOL", "why are analysts bearish on ETH", "summarise analyst opinion on TSLA". Data by CryptoQuant Consensus.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "asset"
      ],
      "properties": {
        "asset": {
          "type": "string",
          "maxLength": 40,
          "minLength": 1,
          "description": "Ticker, route key or name — BTC, bitcoin, ETH, SOL, NVDA, TSLA, SPY, GLD, 005930 …"
        },
        "window": {
          "enum": [
            "7d",
            "30d"
          ],
          "type": "string",
          "default": "30d",
          "description": "Look-back window (default 30d)"
        }
      }
    }
    arguments 24 lines
  • get_consensus reads unknown 2h ago

    The latest Analyst Consensus Index reading for ONE asset (−100 all bearish … +100 all bullish, with the 30-day MA), the bullish / bearish analyst split and the one-line bull and bear case. Use for "what do analysts think about Bitcoin", "is the market bullish on NVDA", "ETH analyst consensus / sentiment". Returns page_url to link and data_by for attribution. Data by CryptoQuant Consensus.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "asset"
      ],
      "properties": {
        "asset": {
          "type": "string",
          "maxLength": 40,
          "minLength": 1,
          "description": "Ticker, route key or name — BTC, bitcoin, ETH, SOL, NVDA, TSLA, SPY, GLD, 005930 …"
        }
      }
    }
    arguments 15 lines
  • get_recent_calls reads unknown 2h ago

    The newest directional calls (bullish / bearish posts by tracked analysts) on ONE asset, newest first — analyst, stance, one post's excerpt, the source link and the analyst page. Use for "what did analysts say about BTC today / this week", "latest ETH calls". Data by CryptoQuant Consensus.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "asset"
      ],
      "properties": {
        "asset": {
          "type": "string",
          "maxLength": 40,
          "minLength": 1,
          "description": "Ticker, route key or name — BTC, bitcoin, ETH, SOL, NVDA, TSLA, SPY, GLD, 005930 …"
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1,
          "description": "How many calls (1–50, default 10)"
        }
      }
    }
    arguments 22 lines
  • get_analyst_profile reads unknown 10h ago

    Verified track record of one tracked analyst by X / CryptoQuant handle or page slug: accuracy score and tier badge, evaluated calls, bull / bear-phase and short / long-horizon scores, ranks, covered assets, recent bias and the profile_url to cite. Accuracy is scored PER ASSET: pass `asset` to read the analyst's record on that asset (default = the asset they call most); the response names the asset in track_record.asset and lists every scored asset under track_record.assets — never quote a score without its asset. Use whenever a user names an analyst ("is @caprioleio any good", "how accurate is Willy Woo on BTC") or before relaying a quoted call. Data by CryptoQuant Consensus.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "handle"
      ],
      "properties": {
        "asset": {
          "type": "string",
          "maxLength": 40,
          "minLength": 1,
          "description": "Ticker / route key / name the record should be about (BTC, ETH, NVDA …); omitted = the analyst's most-called asset"
        },
        "handle": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "X handle (with or without @) or the /analyst/<slug> page slug"
        }
      }
    }
    arguments 21 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 66ce942699b4b0c4.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/66ce942699b4b0c4/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/66ce942699b4b0c4/badge.svg)](https://brick.blue/agent/66ce942699b4b0c4?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
90%

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.