Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.funding-radar/radar

REMOTE · FUNDING-RADAR.COM · SCANNED AUG 20

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

65 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1083 tokens (~180/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · funding-radar.com

# add to Claude Code
claude mcp add --transport http com-funding-radar-radar https://funding-radar.com/mcp
# ~/.codex/config.toml
[mcp_servers.com-funding-radar-radar]
url = "https://funding-radar.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-funding-radar-radar": {
      "type": "remote",
      "url": "https://funding-radar.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-funding-radar-radar --url https://funding-radar.com/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-funding-radar-radar:
    url: "https://funding-radar.com/mcp"
// mcp.json
{
  "mcpServers": {
    "com-funding-radar-radar": {
      "type": "http",
      "url": "https://funding-radar.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Aug 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 128 → 180 functional
    • Server version: 1.0.0 → 1.1.0 functional
    • New tool “radar_about” functional
  • 15 Aug 26 +1
    • Stability: unverified → 0.03 functional
  • 14 Aug 26 63

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Aug 2026 · Probed https://funding-radar.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=funding-radar.com CN=WE1,O=Google Trust Services,C=US 21 Jul 2026 19 Oct 2026 ECDSA 256 ECDSA-SHA256 a134a5f4579835d9131120531679e13c
SANs: funding-radar.com, *.funding-radar.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC insecure

Validation of funding-radar.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
funding-radar.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://funding-radar.com/mcp Verified 200
http (plaintext) http://funding-radar.com/mcp HTTPS enforced 301 https://funding-radar.com/mcp
MCP tools · 6 exposed · ~780 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
funding_events ~121

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.

NameTypeReqDescription
langstringLanguage of the summary and links: 'en' (default) or 'ru'
limitintegerRows per list, default 10
NameTypeReqDescription
datayesCompact numbers the conclusion is based on, units named inside
linkstringyesLive page with the same data
summarystringyesOne-line conclusion — quote this

No examples provided.

funding_history ~134

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.

NameTypeReqDescription
basestringyesBase coin, e.g. BTC
daysWindow in days: 1, 3, 7 (default), 30 or 90
langstringLanguage of the summary and links: 'en' (default) or 'ru'
NameTypeReqDescription
datayesCompact numbers the conclusion is based on, units named inside
linkstringyesLive page with the same data
summarystringyesOne-line conclusion — quote this

No examples provided.

pair_briefing ~153

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).

NameTypeReqDescription
exchangestringyesExchange id
langstringLanguage of the summary and links: 'en' (default) or 'ru'
symbolstringyesNative pair symbol (BTCUSDT, BTC-USDT-SWAP) or base coin (BTC)
NameTypeReqDescription
datayesCompact numbers the conclusion is based on, units named inside
linkstringyesLive page with the same data
summarystringyesOne-line conclusion — quote this

No examples provided.

radar_about ~136

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.

NameTypeReqDescription
langstringLanguage of the summary and links: 'en' (default) or 'ru'
NameTypeReqDescription
datayesCompact numbers the conclusion is based on, units named inside
linkstringyesLive page with the same data
summarystringyesOne-line conclusion — quote this

No examples provided.

settlement_calendar ~123

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.

NameTypeReqDescription
horizonHoursintegerHorizon in hours, 1–8, default 4
langstringLanguage of the summary and links: 'en' (default) or 'ru'
NameTypeReqDescription
datayesCompact numbers the conclusion is based on, units named inside
linkstringyesLive page with the same data
summarystringyesOne-line conclusion — quote this

No examples provided.

spread_pairs ~113

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).

NameTypeReqDescription
langstringLanguage of the summary and links: 'en' (default) or 'ru'
limitintegerRows, default 10
NameTypeReqDescription
datayesCompact numbers the conclusion is based on, units named inside
linkstringyesLive page with the same data
summarystringyesOne-line conclusion — quote this

No examples provided.