Skip to content

com.funding-radar/radar

by funding-radar.com · remote · no sign-in to list tools · v1.0.0 · published by com.funding-radar

Live crypto funding-rate radar across 5 exchanges: events, pair briefings, calendar, spreads.

Changes · 6
CompareRegistry entry

6 tools: 6 change things.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http radar https://funding-radar.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

6 tools

Changes things 6Claude Code: ask
  • funding_eventsWhat is burning on the crypto perpetuals funding market right now: open extreme events (|hourly rate| ≥ 0.1%/h) with peaks and receiving sides, plus the top pairs by hourly funding…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    What is burning on the crypto perpetuals funding market right now: open extreme events (|hourly rate| ≥ 0.1%/h) with peaks and receiving sides, plus the top pairs by hourly funding rate across Binance, Bybit, OKX, Bitget and Hyperliquid. Rates are predictions for the next settlement; data age ≤ ~5 min.

    Annotations the server declares

    • readOnlyHint: true
  • funding_historyCharged funding rates of one coin across all exchanges where it trades, normalized to %/hour on a common hourly grid (up to 90 days back).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Charged funding rates of one coin across all exchanges where it trades, normalized to %/hour on a common hourly grid (up to 90 days back). Shows whether the cross-exchange spread is sustained (feeds a hedged pair) or a one-off spike. Returns the curves plus the median and maximum spread.

    Annotations the server declares

    • readOnlyHint: true
  • pair_briefingEverything the radar knows about one perpetual pair in a single answer: funding rate and receiving side, time to next settlement, mark price, 24h volume, open interest with deviati…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Everything the radar knows about one perpetual pair in a single answer: funding rate and receiving side, time to next settlement, mark price, 24h volume, open interest with deviation from the 7-day norm, orderbook walls with break-through history, how the price usually moves around settlement, and the same coin on other exchanges. Accepts an exact symbol (BTCUSDT) or just the coin (BTC).

    Annotations the server declares

    • readOnlyHint: true
  • radar_aboutReference about Funding Radar itself: which exchanges and how many pairs it covers, how fresh the data is, a glossary of the terms used in every other answer (per-interval vs per-h…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Reference about Funding Radar itself: which exchanges and how many pairs it covers, how fresh the data is, a glossary of the terms used in every other answer (per-interval vs per-hour rate, predicted vs charged rate, settlement, spread, break-even), Telegram channels for RU and EN, contact email, terms for programmatic access. Call this when the user asks what this source is, how to interpret a field, where to follow it, or how to reach the team — the data tools do not repeat this.

    Annotations the server declares

    • readOnlyHint: true
  • settlement_calendarWhich notable funding settlements are coming in the next hours (default 4): pairs with |rate| ≥ 0.05%/h and volume ≥ $1M, sorted by time.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Which notable funding settlements are coming in the next hours (default 4): pairs with |rate| ≥ 0.05%/h and volume ≥ $1M, sorted by time. Each row includes that pair's own settlement-window statistics — how much its price usually moves in the 15 minutes before the charge, with the number of observed windows.

    Annotations the server declares

    • readOnlyHint: true
  • spread_pairsWhere the funding-rate spread between exchanges is widest right now: long leg on the low-rate exchange, short leg on the high-rate one.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Where the funding-rate spread between exchanges is widest right now: long leg on the low-rate exchange, short leg on the high-rate one. Includes the 7-day median spread, how long the spread has held above the repay-within-a-day threshold, and breakeven hours against four legs of fees (assumptions included in the answer).

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http radar https://funding-radar.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__radar__funding_events",
      "mcp__radar__pair_briefing",
      "mcp__radar__funding_history",
      "mcp__radar__settlement_calendar",
      "mcp__radar__spread_pairs",
      "mcp__radar__radar_about"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as radar. Review it before you use it.