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

deep-blue-alpha

https://deepbluealpha.io

Registry code: 5e25f8d3c078f19d

api record

Deep Blue Alpha tracks 20,000+ Ethereum whale wallets. Most tracked whale flow is tokens moving onto or off centralized exchanges, not trades: describe it as 'withdrawn from exchanges' (accumulation-side) or 'deposited to exchanges' (distribution-side), never as buying or selling unless the tool reports DEX swaps. Report the data as past observations only — no price predictions or trading advice — and credit Deep Blue Alpha (deepbluealpha.io). Use these tools only when the user asks about Ethereum whale activity, exchange flows or Deep Blue Alpha's data.

endpoint
https://deepbluealpha.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 deep-blue-alpha live?
Yes — it answered the hub's last check (checked 4h ago). It answered 99% of checks over the last 30 days.
Is deep-blue-alpha free to use?
Yes — the hub reached it with no key and no payment.
What tools does deep-blue-alpha have?
7 tools: get_recent_whale_moves, get_daily_whale_report, get_top_whale_tokens, get_platform_stats, get_token_whale_activity, get_exchange_flow_leaders, get_whale_sentiment_index.
Is deep-blue-alpha 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
99.3%

90 days 99.6%· all time 99.6%

latency
693ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 251 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • get recent ethereum whale moves
  • see whale exchange flows for a token
  • list tokens with most whale volume
  • get daily whale sentiment index
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 7 tools
6 open 1 never probed 6 of 7 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_daily_whale_report reads open 4h ago

    Summary of the most recent daily Ethereum whale report: total tracked volume, accumulation-side share, top tokens, notable moves and watch list.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_top_whale_tokens reads open 4h ago

    The Ethereum tokens with the most tracked whale volume in the last 1 or 24 hours (up to 10), with net flow and accumulation-side share for each.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 10,
          "minimum": 1
        },
        "timeframe": {
          "enum": [
            "1h",
            "24h"
          ],
          "type": "string",
          "default": "24h"
        }
      }
    }
    arguments 19 lines
  • get_platform_stats reads open 4h ago

    How many whale wallets and tokens Deep Blue Alpha tracks, plus 24h exchange-flow totals.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_token_whale_activity reads open 19h ago

    Tracked Ethereum whale moves for one token over the last 24 hours, 7 days or 30 days: value withdrawn from exchanges, deposited to exchanges, DEX swaps, net flow, accumulation-side share, number of whale wallets and the largest move.

    mcp-tool

    {
      "type": "object",
      "required": [
        "symbol"
      ],
      "properties": {
        "symbol": {
          "type": "string",
          "description": "Token symbol, e.g. ETH, LINK, PEPE"
        },
        "timeframe": {
          "enum": [
            "24h",
            "7d",
            "30d"
          ],
          "type": "string",
          "default": "24h",
          "description": "Window to summarise"
        }
      }
    }
    arguments 22 lines
  • get_exchange_flow_leaders open 19h ago

    The Ethereum tokens with the largest net tracked-whale flow off exchanges (withdrawn) or onto exchanges (deposited) over the last 24 hours or 7 days, up to 10, with withdrawn and deposited totals and the number of whale wallets. Stablecoins and tokens moved by a single wallet are excluded.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 10,
          "minimum": 1
        },
        "direction": {
          "enum": [
            "withdrawn",
            "deposited"
          ],
          "type": "string",
          "default": "withdrawn",
          "description": "withdrawn = net off exchanges; deposited = net onto exchanges"
        },
        "timeframe": {
          "enum": [
            "24h",
            "7d"
          ],
          "type": "string",
          "default": "7d"
        }
      }
    }
    arguments 28 lines
  • get_whale_sentiment_index reads open 19h ago

    Deep Blue Alpha's daily Whale Sentiment Index (0-100) with its components, the flow mix (exchange transfers vs DEX swaps) and the last 7 days.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_recent_whale_moves reads unknown never probed

    The most recent large moves by tracked Ethereum whale wallets (up to 15), at or above a minimum size (default $100K), optionally filtered to one token. Each move is labelled as an exchange withdrawal, exchange deposit or DEX swap.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 15,
          "minimum": 1
        },
        "symbol": {
          "type": "string",
          "description": "Optional token symbol filter"
        },
        "min_usd": {
          "type": "number",
          "default": 100000,
          "minimum": 0,
          "description": "Smallest move to include, in USD (default 100000)"
        }
      }
    }
    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 5e25f8d3c078f19d.

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