_ registry / mcp http-sse · checked 5h ago

coinlobster

https://coinlobster.com

Registry code: 020bac60b02c52c4

api record

Pass the question asked as `question`: `answer` is our whole written answer: say it word for word, then only what else was asked. Else answer first in one sentence, opening with the payload `summary`, then the numbers behind it. When `standout` is present, open with it: what is unusual now, how rare, the price since, what followed the last times, counts. Why it moved: `backdrop` (press by outlet and date), `on_coin`, `move` (vs usual day, BTC), `money_now`, `ahead` (dated, counts), `record` (a day, a week on), `case`. The payload describes what happened, with no forecast in it. A non-null…

endpoint
https://coinlobster.com/mcp
protocol
http-sse ·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 coinlobster live?
Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.
Is coinlobster free to use?
Yes — the hub reached it with no key and no payment.
What tools does coinlobster have?
24 tools: watch, coin_search, my_positions, wallet, signals, orderbook, liquidations, options, ….
Is coinlobster 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 97.5%· all time 97.5%

latency
1,135ms

last good check

priced tools
0

of 24 tools

_ answered our checks, 90 days 326 checks · signed record
  • degraded → live
  • down → live
  • degraded → down· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
used for
  • get a crypto coin brief
  • track whale flows
  • get liquidations and funding data
  • get crypto news sentiment
  • set price alerts
takes → gives
text → data
tools
20 reads1 changes data
_ 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 24 tools
18 open 6 never probed 18 of 24 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.

  • liquidations reads open 14h ago

    Forced closes. scope: coin (recorded long vs short closes for one coin, the default when a coin is named), market (the whole market, long/short split, the default otherwise), lending (on-chain lending liquidations with both wallets, never added to perp), projected (modelled levels, not trades), heat (where closes hit by price band). A long is force-closed by selling.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "coin": {
          "type": "string",
          "description": "Coin symbol, e.g. BTC. A pair like ETH/USD works too."
        },
        "chain": {
          "type": "string",
          "description": "ethereum, base or arbitrum. Omit for all."
        },
        "hours": {
          "type": "integer",
          "description": "How many hours back to read."
        },
        "limit": {
          "type": "integer",
          "description": "Rows to return (usually up to 1000; more is clamped and said)."
        },
        "scope": {
          "enum": [
            "coin",
            "market",
            "lending",
            "projected",
            "heat"
          ],
          "type": "string",
          "description": "Which lane; see the description."
        },
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        },
        "question": {
          "type": "string",
          "description": "The question to answer, as it was asked (e.g. \"why is ETH down today\"). `answer` is then written for it."
        },
        "since_ms": {
          "type": "integer",
          "description": "Only rows newer than this Unix-ms time (polling cursor)."
        }
      },
      "additionalProperties": {}
    }
    arguments 53 lines
  • options reads open 14h ago

    BTC or ETH options: open interest by strike, put/call balance, max pain per expiry, implied volatility and recent large option trades.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "coin": {
          "type": "string",
          "description": "BTC (default) or ETH."
        },
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        }
      },
      "additionalProperties": {}
    }
    arguments 22 lines
  • whale_activity reads open 41h ago

    What whales are doing, per coin. view: summary (default with a coin: net flow over 1h/4h/24h/7d, exchange vs on-chain vs Hyperliquid split, flow against price), hourly (buy and sell dollars per hour), trades (individual whale trades, newest first), venues (which exchanges hold the flow), context (is this unusual for THIS coin, accepts a list), hyperliquid (fills with both wallets named), onchain (DEX swaps on Ethereum, Base, Arbitrum with the signer).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "coin": {
          "type": "string",
          "description": "Coin symbol, e.g. BTC. A pair like ETH/USD works too."
        },
        "view": {
          "enum": [
            "summary",
            "hourly",
            "trades",
            "venues",
            "context",
            "hyperliquid",
            "onchain"
          ],
          "type": "string",
          "description": "Which lane; see the description."
        },
        "chain": {
          "type": "string",
          "description": "ethereum, base or arbitrum. Omit for all."
        },
        "coins": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            {
              "type": "string"
            }
          ],
          "description": "Several coins in one call (list or \"BTC,ETH\"), up to 10."
        },
        "hours": {
          "type": "integer",
          "description": "How many hours back to read."
        },
        "limit": {
          "type": "integer",
          "description": "Rows to return (usually up to 200; more is clamped and said)."
        },
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        },
        "source": {
          "enum": [
            "cex",
            "dex",
            "all"
          ],
          "type": "string",
          "description": "trades only: exchanges, DEX swaps or both."
        },
        "min_usd": {
          "type": "number",
          "description": "Smallest trade in USD."
        },
        "question": {
          "type": "string",
          "description": "The question to answer, as it was asked (e.g. \"why is ETH down today\"). `answer` is then written for it."
        },
        "since_ms": {
          "type": "integer",
          "description": "Only rows newer than this Unix-ms time (polling cursor)."
        },
        "breakdown": {
          "enum": [
            "none",
            "venues",
            "wallets",
            "all"
          ],
          "type": "string",
          "description": "hourly only: split each hour by exchange or wallet (Pro)."
        }
      },
      "additionalProperties": {}
    }
    arguments 92 lines
  • traders reads open 2d ago

    Smart money here means the PROVEN cohort: Hyperliquid accounts screened for real profit and verified by their own fills. view: smart_money (default: what that cohort holds and trades per coin), proven (who they are, by trader number), screened (every wallet screened from closing fills, a weaker claim), board (tracked big accounts: equity, leverage, bias), moves (opens, adds, trims, closes, flips just now), dex (wallets moving the most on DEXes).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "coin": {
          "type": "string",
          "description": "Coin symbol, e.g. BTC. A pair like ETH/USD works too."
        },
        "kind": {
          "type": "string",
          "description": "moves only: open, add, trim, close or flip."
        },
        "view": {
          "enum": [
            "smart_money",
            "proven",
            "screened",
            "board",
            "moves",
            "dex"
          ],
          "type": "string",
          "description": "Which lane; see the description."
        },
        "chain": {
          "type": "string",
          "description": "ethereum, base or arbitrum. Omit for all."
        },
        "limit": {
          "type": "integer",
          "description": "Rows to return (usually up to 100; more is clamped and said)."
        },
        "token": {
          "type": "string",
          "description": "dex only: one token."
        },
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        },
        "wallet": {
          "type": "string",
          "description": "moves only: one account address."
        },
        "window": {
          "enum": [
            "1h",
            "4h",
            "24h"
          ],
          "type": "string",
          "description": "Time window: 1h, 4h or 24h."
        },
        "question": {
          "type": "string",
          "description": "The question to answer, as it was asked (e.g. \"why is ETH down today\"). `answer` is then written for it."
        },
        "since_ms": {
          "type": "integer",
          "description": "Only rows newer than this Unix-ms time (polling cursor)."
        }
      },
      "additionalProperties": {}
    }
    arguments 71 lines
  • my_alerts reads open 14h ago

    What your CoinLobster alerts fired since a time, newest first, with the move since each. Needs a signed-in connection (free).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "coin": {
          "type": "string",
          "description": "Coin symbol, e.g. BTC. A pair like ETH/USD works too."
        },
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        },
        "since_ms": {
          "type": "integer",
          "description": "Only rows newer than this Unix-ms time (polling cursor)."
        }
      },
      "additionalProperties": {}
    }
    arguments 26 lines
  • sectors reads open 3d ago

    Where whale money is moving between sectors (L1, L2, DeFi, memes, AI and others): net direction, share of flow and the coins carrying it.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        },
        "window": {
          "enum": [
            "1h",
            "4h",
            "24h"
          ],
          "type": "string",
          "description": "Time window: 1h, 4h or 24h."
        },
        "question": {
          "type": "string",
          "description": "The question to answer, as it was asked (e.g. \"why is ETH down today\"). `answer` is then written for it."
        }
      },
      "additionalProperties": {}
    }
    arguments 31 lines
  • what_followed open 41h ago

    Every past unusual time on one coin inside your window, oldest first, with the price then, a day later and the move either way; then the counts both ways and the one record sentence. Free: the last 24 hours plus the record dots.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "coin": {
          "type": "string",
          "description": "Coin symbol, e.g. BTC. A pair like ETH/USD works too."
        },
        "kind": {
          "enum": [
            "whales",
            "forced",
            "fee",
            "all"
          ],
          "type": "string",
          "description": "whales, forced (a wave of forced closes), fee (a costly fee) or all (default)."
        },
        "side": {
          "enum": [
            "buy",
            "sell",
            "both",
            "long",
            "short",
            "any"
          ],
          "type": "string",
          "description": "Only this side. Default any."
        },
        "limit": {
          "type": "integer",
          "description": "Rows to return (usually up to 10; more is clamped and said)."
        },
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        },
        "question": {
          "type": "string",
          "description": "The question to answer, as it was asked (e.g. \"why is ETH down today\"). `answer` is then written for it."
        }
      },
      "additionalProperties": {}
    }
    arguments 52 lines
  • situations reads open 5h ago

    What is going on right now, in stages (emerging, confirmed, escalating, cooling, contested): one coin, one story each, with the evidence behind it and the price move since it started.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "coin": {
          "type": "string",
          "description": "Coin symbol, e.g. BTC. A pair like ETH/USD works too."
        },
        "limit": {
          "type": "integer",
          "description": "Rows to return (usually up to 50; more is clamped and said)."
        },
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        },
        "question": {
          "type": "string",
          "description": "The question to answer, as it was asked (e.g. \"why is ETH down today\"). `answer` is then written for it."
        },
        "include_resolved": {
          "type": "boolean",
          "description": "Also finished ones with their outcome (Pro)."
        }
      },
      "additionalProperties": {}
    }
    arguments 34 lines
  • big_catch reads open 5h ago

    The whale-flow setups tracked right now, one coin each, with state (forming, confirmed, accelerating), direction, age and the price move since it started.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "coin": {
          "type": "string",
          "description": "Coin symbol, e.g. BTC. A pair like ETH/USD works too."
        },
        "limit": {
          "type": "integer",
          "description": "Rows to return (usually up to 100; more is clamped and said)."
        },
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        }
      },
      "additionalProperties": {}
    }
    arguments 26 lines
  • market_now reads open 32h ago

    The whole market in one call. view: changes (default: what changed since your last check or since_ms, ranked by how unusual, with plain state labels, what whales net bought and sold, coins that turned unusual, biggest movers, forced closes, the market news read; pass back next_since_ms on a timer), overview (totals, whale net flow, top coins; pass coin for one row), movers (24h gainers and losers with volume), extremes (pairs at a record or their own top or bottom 5% for funding, open interest or liquidations), defi (DEX volume and TVL per chain).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "coin": {
          "type": "string",
          "description": "Coin symbol, e.g. BTC. A pair like ETH/USD works too."
        },
        "only": {
          "enum": [
            "gainers",
            "losers"
          ],
          "type": "string",
          "description": "movers only: one side."
        },
        "view": {
          "enum": [
            "changes",
            "overview",
            "movers",
            "extremes",
            "defi"
          ],
          "type": "string",
          "description": "Which lane; see the description."
        },
        "limit": {
          "type": "integer",
          "description": "Rows to return (usually up to 50; more is clamped and said)."
        },
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        },
        "question": {
          "type": "string",
          "description": "The question to answer, as it was asked (e.g. \"why is ETH down today\"). `answer` is then written for it."
        },
        "since_ms": {
          "type": "integer",
          "description": "changes only: only changes after this Unix-ms time. Omit for everything since your last check."
        }
      },
      "additionalProperties": {}
    }
    arguments 53 lines
  • history reads open 23h ago

    History for one coin. series: price (default: near-live hourly or daily bars, oldest first), funding_oi (the intraday open interest and funding path), daily (the recorded daily archive of funding, open interest, price and liquidations for the coin), whale_daily (the recorded daily whale buy and sell flow for the coin). daily (and price at interval 1d) also carries own_history: where the price sits in its own record (the streak, highs and lows with dates, the averages, the month, the swings, days like the last day a day and a week later), labelled context, never a receipt.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "coin": {
          "type": "string",
          "description": "Coin symbol, e.g. BTC. A pair like ETH/USD works too."
        },
        "days": {
          "type": "integer",
          "description": "How many days back to read."
        },
        "hours": {
          "type": "integer",
          "description": "How many hours back to read."
        },
        "limit": {
          "type": "integer",
          "description": "Rows to return (usually up to 720; more is clamped and said)."
        },
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        },
        "series": {
          "enum": [
            "price",
            "funding_oi",
            "daily",
            "whale_daily"
          ],
          "type": "string",
          "description": "Which lane; see the description."
        },
        "interval": {
          "type": "string",
          "description": "price only: 1h (default) or 1d."
        }
      },
      "additionalProperties": {}
    }
    arguments 48 lines
  • coin_brief reads open 32h ago

    The one-call answer for ONE coin, with the news read (summary, mood, headlines) riding along, in the owner's order: summary (the answer first, the one record sentence at its end), you (the account's saved position on it, when there is one), backdrop (the market this fortnight and the headlines, each by outlet and date, and the market's state with its denominators), on_coin (dated facts, the change feed, situations), move (the move against its usual day and against BTC: usual_day_pct, move_pctile, vs_market), money_now (whales by window with lean at 60% and the hour-adjusted multiple, named accounts as labels, venues, forced closes, the fee, open positions, positioning, options), tracked_accounts (what the Hyperliquid accounts we track hold, both sides in dollars), levels (their real liquidation prices, nearest first; Pro), ahead (dated, each with the last times of that kind as counts a day and a week later), record (what followed the earlier times a day later and in week_later a week later, counts both ways, the coin's ordinary day beside them; present on a quiet coin too), case (points up and points down as sent, neither weighed), what_it_is, sources, gaps and unavailable (a section that could not be read, distinct from one read and empty). Answers "why is X moving" without a second call. view: brief (default), quick (price, funding, open interest only), funding (rate per exchange), crowding (0-100 crowding read, Pro).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "coin": {
          "type": "string",
          "description": "Coin symbol, e.g. BTC. A pair like ETH/USD works too."
        },
        "view": {
          "enum": [
            "brief",
            "quick",
            "funding",
            "crowding"
          ],
          "type": "string",
          "description": "Which lane; see the description."
        },
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        },
        "compact": {
          "type": "boolean",
          "description": "true: one line of text instead of JSON."
        },
        "question": {
          "type": "string",
          "description": "The question to answer, as it was asked (e.g. \"why is ETH down today\"). `answer` is then written for it."
        },
        "position_usd": {
          "type": "number",
          "description": "Position size in USD, to price the funding cost."
        }
      },
      "additionalProperties": {}
    }
    arguments 44 lines
  • my_access reads open 23h ago

    Your plan, what it includes, roughly how many answers are left, and the next plan up. Free, never counted.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": {}
    }
    arguments 5 lines
  • whale_radar reads open 32h ago

    Which coins have UNUSUAL whale flow right now, each against its own normal, over 1h, 4h and 24h, ranked by how far above normal (not by dollar size). For discovery when no coin is named.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "description": "Rows to return (usually up to 100; more is clamped and said)."
        },
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        },
        "window": {
          "enum": [
            "1h",
            "4h",
            "24h"
          ],
          "type": "string",
          "description": "One window only. Omit for all three."
        },
        "question": {
          "type": "string",
          "description": "The question to answer, as it was asked (e.g. \"why is ETH down today\"). `answer` is then written for it."
        }
      },
      "additionalProperties": {}
    }
    arguments 35 lines
  • market_screener reads open 23h ago

    Screen every recorded pair at once: funding_band and oi_band against each pair's own recorded days (record high, top 5%, top 25%, typical, bottom 25%, bottom 5%, record low), a minimum whale-flow multiple, and unusual-only.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "description": "Rows to return (usually up to 50; more is clamped and said)."
        },
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        },
        "compact": {
          "type": "boolean",
          "description": "true: one line per coin."
        },
        "oi_band": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "array",
              "items": {
                "type": "string"
              }
            }
          ],
          "description": "Open interest band(s)."
        },
        "question": {
          "type": "string",
          "description": "The question to answer, as it was asked (e.g. \"why is ETH down today\"). `answer` is then written for it."
        },
        "funding_band": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "array",
              "items": {
                "type": "string"
              }
            }
          ],
          "description": "Funding band(s), e.g. \"top 5%\"."
        },
        "unusual_only": {
          "type": "boolean",
          "description": "Only coins with unusual whale activity now."
        },
        "whale_mult_min": {
          "type": "number",
          "description": "Minimum whale flow as a multiple of the coin's own average."
        }
      },
      "additionalProperties": {}
    }
    arguments 66 lines
  • news reads open 5h ago

    Headlines for one coin with the mood score (-100 to +100), the written points behind it and the market-wide read. For "why is X moving" use coin_brief: it already carries this.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "coin": {
          "type": "string",
          "description": "Coin symbol, e.g. BTC. A pair like ETH/USD works too."
        },
        "limit": {
          "type": "integer",
          "description": "Rows to return (usually up to 20; more is clamped and said)."
        },
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        }
      },
      "additionalProperties": {}
    }
    arguments 26 lines
  • watchlist_brief reads open 2d ago

    Every coin on your watchlist through the whale read in one call: flow against each coin's normal, buy or sell lean, and whether it is unusual now. Needs a signed-in connection (free).

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": {}
    }
    arguments 5 lines
  • my_week open 41h ago

    Your last seven days: the coins, every unusual time on them with the day-later move, record dots, alerts and questions as counts. Needs a signed-in connection (free).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        }
      },
      "additionalProperties": {}
    }
    arguments 18 lines
  • watch changes data unknown never probed

    Alerts checked continuously and delivered to your CoinLobster account when they trigger: the alert list on the site, or the webhook or Discord channel saved on your account page (never a URL given here). action: list (default), create (coin + trigger: radar_unusual, flag_fired or funding_band with band; deliver: app, webhook or discord), delete (id). Pro to create.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "id": {
          "type": "string",
          "description": "delete only: the alert id."
        },
        "band": {
          "type": "string",
          "description": "create with funding_band: the band, e.g. \"top 5%\"."
        },
        "coin": {
          "type": "string",
          "description": "Coin symbol, e.g. BTC. A pair like ETH/USD works too."
        },
        "action": {
          "enum": [
            "list",
            "create",
            "delete"
          ],
          "type": "string",
          "description": "Which lane; see the description."
        },
        "deliver": {
          "enum": [
            "app",
            "webhook",
            "discord"
          ],
          "type": "string",
          "description": "create only: where it goes on your account. app (the alert list on coinlobster.com, default), webhook or discord (the one saved at coinlobster.com/account#channels)."
        },
        "trigger": {
          "enum": [
            "radar_unusual",
            "flag_fired",
            "funding_band"
          ],
          "type": "string",
          "description": "create only: what triggers it."
        },
        "webhook_url": {
          "type": "string",
          "description": "Not accepted: an alert never goes to a URL given here. Save a webhook at coinlobster.com/account#channels and pass deliver: \"webhook\"."
        }
      },
      "additionalProperties": {}
    }
    arguments 49 lines
  • coin_search reads unknown 2d ago

    Find a coin by symbol or name and learn the symbol the other tools take, whether it is covered and whether it is free, with price and 24h change. Free.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "coin": {
          "type": "string",
          "description": "Coin symbol, e.g. BTC. A pair like ETH/USD works too."
        },
        "limit": {
          "type": "integer",
          "description": "Rows to return (usually up to 20; more is clamped and said)."
        },
        "query": {
          "type": "string",
          "description": "Symbol or part of a name, e.g. \"sol\"."
        },
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        }
      },
      "additionalProperties": {}
    }
    arguments 30 lines
  • my_positions unknown never probed

    Up to 10 of your own positions on your account, each read with the facts now: price against entry, whale lean both ways, the tracked accounts, forced-close levels (paid), the fee, the record. No view on the position. Needs a signed-in connection (free).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "coin": {
          "type": "string",
          "description": "Coin symbol, e.g. BTC. A pair like ETH/USD works too."
        },
        "side": {
          "enum": [
            "long",
            "short"
          ],
          "type": "string",
          "description": "set: long or short."
        },
        "entry": {
          "type": "number",
          "description": "set: the price you got in at."
        },
        "action": {
          "enum": [
            "set",
            "list",
            "clear"
          ],
          "type": "string",
          "description": "set, list (default) or clear."
        },
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        },
        "leverage": {
          "type": "number",
          "description": "set, optional: leverage, 1 to 200."
        },
        "size_usd": {
          "type": "number",
          "description": "set, optional: dollar size."
        },
        "liquidation": {
          "type": "number",
          "description": "set, optional: the liquidation price."
        }
      },
      "additionalProperties": {}
    }
    arguments 55 lines
  • wallet reads unknown 34d ago

    One address. A Hyperliquid account returns its live positions, leverage, liquidation prices and recent fills; an Ethereum, Base or Arbitrum wallet returns its DEX swaps and net flow per token. chain: auto (default: tries Hyperliquid, then on-chain), hyperliquid, or evm.

    mcp-tool

    {
      "type": "object",
      "required": [
        "address"
      ],
      "properties": {
        "chain": {
          "enum": [
            "auto",
            "hyperliquid",
            "evm",
            "ethereum",
            "base",
            "arbitrum"
          ],
          "type": "string",
          "description": "auto (default), hyperliquid, or evm (ethereum, base, arbitrum)."
        },
        "limit": {
          "type": "integer",
          "description": "Rows to return (usually up to 200; more is clamped and said)."
        },
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        },
        "address": {
          "type": "string",
          "description": "0x followed by 40 hex characters."
        }
      },
      "additionalProperties": {}
    }
    arguments 41 lines
  • signals reads unknown never probed

    Signals logged live when they fired, never backfilled, with the price after. view: recent (default: the latest signals and their outcomes), record (the last N firings of one type on one coin: how many rose, median move), scorecard (the totals only).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "coin": {
          "type": "string",
          "description": "Coin symbol, e.g. BTC. A pair like ETH/USD works too."
        },
        "type": {
          "type": "string",
          "description": "Signal type; an unknown one lists the valid types."
        },
        "view": {
          "enum": [
            "recent",
            "record",
            "scorecard"
          ],
          "type": "string",
          "description": "Which lane; see the description."
        },
        "hours": {
          "type": "integer",
          "description": "How many hours back to read."
        },
        "limit": {
          "type": "integer",
          "description": "Rows to return (usually up to 500; more is clamped and said)."
        },
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        }
      },
      "additionalProperties": {}
    }
    arguments 43 lines
  • orderbook reads unknown never probed

    The order book for one coin merged across exchanges: best bid and ask, the gap between them, and the dollars resting on each side with the exchanges holding each level.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "coin": {
          "type": "string",
          "description": "Coin symbol, e.g. BTC. A pair like ETH/USD works too."
        },
        "cursor": {
          "type": "string",
          "description": "Next page: the cursor from the previous answer."
        },
        "detail": {
          "enum": [
            "brief",
            "full"
          ],
          "type": "string",
          "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor."
        },
        "levels": {
          "type": "integer",
          "description": "Price levels per side."
        }
      },
      "additionalProperties": {}
    }
    arguments 26 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 020bac60b02c52c4.

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