com.funding-radar/radar
REMOTE · FUNDING-RADAR.COM
Live crypto funding-rate radar across 5 exchanges: events, pair briefings, calendar, spreads.
Available components
Last scanned (7 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Crypto and Web3
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 → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 28 Sept 26 +6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 13 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 16 Aug 26 0
- 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 0
- Stability: unverified → 0.03 ▲ functional
- 14 Aug 26 0
First indexed and scored.
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 23 Oct 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 | 18 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 9b7d16f1308fe19413ba77c54b088f7a |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
funding_events Extreme funding events right now ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the summary and links: 'en' (default) or 'ru' |
| limit | integer | – | Rows per list, default 10 |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Compact numbers the conclusion is based on, units named inside |
| link | string | yes | Live page with the same data |
| summary | string | yes | One-line conclusion — quote this |
No examples provided.
funding_history Cross-exchange funding history of a coin ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | yes | 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' |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Compact numbers the conclusion is based on, units named inside |
| link | string | yes | Live page with the same data |
| summary | string | yes | One-line conclusion — quote this |
No examples provided.
pair_briefing Full briefing for one pair ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | yes | Exchange id |
| lang | string | – | Language of the summary and links: 'en' (default) or 'ru' |
| symbol | string | yes | Native pair symbol (BTCUSDT, BTC-USDT-SWAP) or base coin (BTC) |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Compact numbers the conclusion is based on, units named inside |
| link | string | yes | Live page with the same data |
| summary | string | yes | One-line conclusion — quote this |
No examples provided.
radar_about About the radar: how to read its numbers, and contacts ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the summary and links: 'en' (default) or 'ru' |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Compact numbers the conclusion is based on, units named inside |
| link | string | yes | Live page with the same data |
| summary | string | yes | One-line conclusion — quote this |
No examples provided.
settlement_calendar Upcoming funding settlements ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| horizonHours | integer | – | Horizon in hours, 1–8, default 4 |
| lang | string | – | Language of the summary and links: 'en' (default) or 'ru' |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Compact numbers the conclusion is based on, units named inside |
| link | string | yes | Live page with the same data |
| summary | string | yes | One-line conclusion — quote this |
No examples provided.
spread_pairs Hedged pairs: cross-exchange spreads ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the summary and links: 'en' (default) or 'ru' |
| limit | integer | – | Rows, default 10 |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Compact numbers the conclusion is based on, units named inside |
| link | string | yes | Live page with the same data |
| summary | string | yes | One-line conclusion — quote this |
No examples provided.
How do I install the com.funding-radar/radar MCP server?
com.funding-radar/radar is a hosted endpoint at https://funding-radar.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · funding-radar.com
claude mcp add --transport http com-funding-radar-radar 'https://funding-radar.com/mcp'
What is the com.funding-radar/radar MCP server?
com.funding-radar/radar is an MCP server listed in the public MCP registry as com.funding-radar/radar. Live crypto funding-rate radar across 5 exchanges: events, pair briefings, calendar, spreads. This page covers its hosted endpoint (https://funding-radar.com/mcp).
Is the com.funding-radar/radar MCP server safe to use?
com.funding-radar/radar scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.funding-radar/radar MCP server expose?
com.funding-radar/radar exposes 6 tools: funding_events, pair_briefing, funding_history, settlement_calendar, spread_pairs, radar_about. Their descriptions and schemas cost roughly 780 tokens of context every time the server is loaded.
Does the com.funding-radar/radar MCP server require authentication?
No. We connected to com.funding-radar/radar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.funding-radar/radar MCP server still maintained?
com.funding-radar/radar is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.