# com.funding-radar/radar (remote · funding-radar.com)

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

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- remote · `funding-radar.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/com-funding-radar-radar/funding-radar.md), [page](https://verifymcp.io/servers/com-funding-radar-radar/funding-radar)

## Channel facts

- Endpoint: `https://funding-radar.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-funding-radar-radar --url https://funding-radar.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-funding-radar-radar:
    url: "https://funding-radar.com/mcp"
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-19 (score 65, +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.

### 2026-08-17 (score 64, +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.

### 2026-08-16 (score 63, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 128 → 180
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “radar_about”

### 2026-08-15 (score 64, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-14 (score 63)

First indexed and scored.

## MCP tools (6)

### `funding_events` (~121 tokens)

Extreme funding events right now

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.

Input parameters:

- `lang` (string): Language of the summary and links: 'en' (default) or 'ru'
- `limit` (integer): Rows per list, default 10

Output parameters:

- `data`: Compact numbers the conclusion is based on, units named inside
- `link` (string): Live page with the same data
- `summary` (string): One-line conclusion — quote this

### `pair_briefing` (~153 tokens)

Full briefing for one pair

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

Input parameters:

- `exchange` (string, required): Exchange id
- `lang` (string): Language of the summary and links: 'en' (default) or 'ru'
- `symbol` (string, required): Native pair symbol (BTCUSDT, BTC-USDT-SWAP) or base coin (BTC)

Output parameters:

- `data`: Compact numbers the conclusion is based on, units named inside
- `link` (string): Live page with the same data
- `summary` (string): One-line conclusion — quote this

### `funding_history` (~134 tokens)

Cross-exchange funding history of a coin

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.

Input parameters:

- `base` (string, required): Base coin, e.g. BTC
- `days`: Window in days: 1, 3, 7 (default), 30 or 90
- `lang` (string): Language of the summary and links: 'en' (default) or 'ru'

Output parameters:

- `data`: Compact numbers the conclusion is based on, units named inside
- `link` (string): Live page with the same data
- `summary` (string): One-line conclusion — quote this

### `settlement_calendar` (~123 tokens)

Upcoming funding settlements

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.

Input parameters:

- `horizonHours` (integer): Horizon in hours, 1–8, default 4
- `lang` (string): Language of the summary and links: 'en' (default) or 'ru'

Output parameters:

- `data`: Compact numbers the conclusion is based on, units named inside
- `link` (string): Live page with the same data
- `summary` (string): One-line conclusion — quote this

### `spread_pairs` (~113 tokens)

Hedged pairs: cross-exchange spreads

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

Input parameters:

- `lang` (string): Language of the summary and links: 'en' (default) or 'ru'
- `limit` (integer): Rows, default 10

Output parameters:

- `data`: Compact numbers the conclusion is based on, units named inside
- `link` (string): Live page with the same data
- `summary` (string): One-line conclusion — quote this

### `radar_about` (~136 tokens)

About the radar: how to read its numbers, and contacts

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.

Input parameters:

- `lang` (string): Language of the summary and links: 'en' (default) or 'ru'

Output parameters:

- `data`: Compact numbers the conclusion is based on, units named inside
- `link` (string): Live page with the same data
- `summary` (string): One-line conclusion — quote this

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-funding-radar-radar/funding-radar#diagnostics

## Score history

- 2026-08-20: 65
- 2026-08-19: 65
- 2026-08-18: 64
- 2026-08-17: 64
- 2026-08-16: 63
- 2026-08-15: 64
- 2026-08-14: 63

## Links

- Remote endpoint: https://funding-radar.com/mcp
- Website: https://funding-radar.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-funding-radar-radar/funding-radar.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-funding-radar-radar/funding-radar.json
- HTML version of this page: https://verifymcp.io/servers/com-funding-radar-radar/funding-radar