Skip to content

Funding Radar MCP server

com.funding-radar/radarfunding-radar.comstreamable-httpv1.4.0Scanned

Live crypto funding rates on 8 exchanges: events, pairs, spreads, bot conditions, liquidations.

12 tools: 11 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 11 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

11 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Funding Radar MCP server can do

The Funding Radar MCP server is published by funding-radar.com, a domain the MCP Registry verified. It has 12 tools. It can create or change data (11 tools: funding_events, pair_briefing, funding_history, settlement_calendar and 7 more), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 4 times since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 1.4.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

12 tools

Changes things 11Claude Code: ask
  • alert_optionsHow to get funding alerts from the radar: the public Telegram channels (RU/EN, extreme events, delayed), the personal bot with instant alerts and custom conditions (free during the…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
    How to get funding alerts from the radar: the public Telegram channels (RU/EN, extreme events, delayed), the personal bot with instant alerts and custom conditions (free during the open beta), and a deep link that opens the bot with the coin already set. MCP is anonymous and cannot subscribe anyone — this tool only explains and links.

    Annotations the server declares

    • readOnlyHint: true
  • condition_scanCheck a condition in the Telegram bot's syntax against live data and list the pairs that match now, strongest first.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
    Check a condition in the Telegram bot's syntax against live data and list the pairs that match now, strongest first. Syntax: metrics funding (%/h), cut (minutes to settlement), vol (24h volume, 1M = $1M), oi, plus ranges and presets — e.g. `funding>0.3 cut<30 vol>1M`, `hedge 0.3` (cross-exchange spread), `squeeze`, or a bare threshold `0.3`. Returns the exact `/watch` command the bot accepts, so the user can subscribe to future matches. Rates are predictions for the next settlement.

    Annotations the server declares

    • readOnlyHint: true
  • delistingsPerpetual contracts the exchanges are winding down, with the settlement or delisting date where the exchange gives one, 24h volume and the current hourly rate.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
    Perpetual contracts the exchanges are winding down, with the settlement or delisting date where the exchange gives one, 24h volume and the current hourly rate. An extreme funding rate on a contract being removed is a trap: the position gets settled at the exchange's price and liquidity is leaving. Source: exchange contract statuses and disappearance from the instrument list — observed in our data, not an exchange announcement.

    Annotations the server declares

    • readOnlyHint: true
  • 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, Hyperliquid, Gate, Aster and Bitunix. 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
  • liquidationsCoins with the largest liquidations in the last hour or 24 hours, exchanges summed, with the long/short split (longShare ≥ 0.6 — longs are being wiped out, ≤ 0.4 — shorts).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
    Coins with the largest liquidations in the last hour or 24 hours, exchanges summed, with the long/short split (longShare ≥ 0.6 — longs are being wiped out, ≤ 0.4 — shorts). Read together with an extreme funding rate it shows a squeeze in progress. Coverage: exchange liquidation streams of Binance, OKX, Bitget, Gate, Aster and part of Bybit; Hyperliquid and Bitunix are not covered.

    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
  • pair_eventsHow often one pair has had extreme funding (|rate| ≥ 0.1%/h) over 30 days, 7 days and 24 hours, how long an episode usually lasts, whether one is running now, and how past ones end…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
    How often one pair has had extreme funding (|rate| ≥ 0.1%/h) over 30 days, 7 days and 24 hours, how long an episode usually lasts, whether one is running now, and how past ones ended: funding accrued vs the price move against the receiving side. Counts episodes, not raw detector events (same-side events under an hour apart are merged). Answers whether a burning rate is a pattern or a one-off. 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
Only reads 1Show 1 read-only tool

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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:38 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
11
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 11 tools that change things (11 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://funding-radar.com/mcp: tools/list returned 12 tools to an anonymous client, including funding_events (write), pair_briefing (write), funding_history (write), settlement_calendar (write), spread_pairs (write) and 6 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 7 to 11
  2. Oct 29, 2026
    • Tools that change things, listed without credentials: 6 to 7

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 7 -> 11.View diff
    • Tools that change things, listed without credentials: 7 to 11
  2. Tools1 added.+1 addedView diff
  3. Tools1 changed.~1 changedView diff
  4. Tools3 added, 4 changed.+3 added~4 changedView diff
  5. PostureRemote posture changed. Tools that change things, listed without credentials: 6 -> 7.View diff
    • Tools that change things, listed without credentials: 6 to 7
  6. Tools2 added.+2 addedView diff

Install

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

claude mcp add --transport http radar https://funding-radar.com/mcp
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 or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__radar__pair_search"
    ],
    "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",
      "mcp__radar__condition_scan",
      "mcp__radar__liquidations",
      "mcp__radar__delistings",
      "mcp__radar__pair_events",
      "mcp__radar__alert_options"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as radar. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.funding-radar/radar/verify?hash=3ad2f54dd4acf2cb6580ecd2a4fee571f40f894f04c46dd2141e3d24d907a4a9" | jq -e '.changed == false'

Pinned hash 3ad2f54dd4ac, from Nov 10, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.funding-radar/radar/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.funding-radar/radar
[![Anlyon Radar](https://radar.anlyon.com/badge/com.funding-radar/radar.svg)](https://radar.anlyon.com/servers/com.funding-radar/radar)

Source: MCP Registry. Synced Nov 10, 2026, 19:17 UTC.

Funding Radar MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Funding Radar MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 11 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Funding Radar MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Funding Radar MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Funding Radar MCP server have?

12 tools: 11 write, 1 read. funding_events, pair_briefing, funding_history, settlement_calendar, spread_pairs, radar_about, condition_scan, liquidations and 4 more.

Does the Funding Radar MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Funding Radar MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Funding Radar MCP server changed its tools?

Yes, 4 times since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.