mcp-registry/com.funding-radar/radar · v1.4.0
Verdict. Funding Radar Radar MCP server answered 99.85% of Glimind's liveness checks over 30 days, better than 29% of MCP servers, with 566 ms median handshake and 12 outages in 90 days. Its agent-readiness grade is A (93/100) across 12 tools, costing an agent about 2,970 tokens to load. Checked every few minutes; no tool is ever called.
Data as of .
| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.85% | 29% of MCP servers |
| Median handshake latency | 566 ms | 19% of MCP servers |
| p95 handshake latency | 2078 ms | — |
| Checks in 30 days | 7,110 | — |
| Outages, 90 days | 12 | — |
| Median recovery | 4 min | — |
| Agent-readiness score | 93/100 (A) | 74% of MCP servers |
| Tools | 12 | — |
| Tool-list size for an agent | ~2,970 tokens | 45% of MCP servers |
| Days observed | 29 | — |
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-12 16:43 UTC, the Funding Radar Radar MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 12 outages in 90 days, with a median recovery of 4 minutes.
Live crypto funding rates on 5 exchanges: events, pair search, briefings, calendar, spreads, alerts.
Claude Code
claude mcp add --transport http funding-radar-radar-mcp-server https://funding-radar.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"funding-radar-radar-mcp-server": {
"type": "http",
"url": "https://funding-radar.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
1 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
In the last 30 days: 0 tool(s) removed and 2 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.funding-radar/radar"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.funding-radar/radar"}) over MCP.
pair_search ~397 tokenscondition_scan ~318 tokenspair_events ~284 tokenspair_briefing ~267 tokensdelistings ~256 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fcom.funding-radar%2Fradar?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.funding-radar%2Fradar?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fcom.funding-radar%2Fradar.svg" alt="MCP server status"></a>
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:746fa619b8d13f71…, first seen 2026-11-10, included at leaf 212297 of 238,825. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable data servers · most reliable finance servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp?ref=install-server"
}
}
}
As of 2026-11-12 16:43 UTC, the Funding Radar Radar MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 12 outages in 90 days, with a median recovery of 4 minutes.
Funding Radar Radar MCP server advertises 12 tools, including alert_options, condition_scan, delistings, funding_events, funding_history.
Point your MCP client at this streamable-http endpoint: https://funding-radar.com/mcp
Glimind scanned all 12 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.