Cloudflare Radar MCP Server

🛡️ Official✓ VerifiedHTTP + SSEOAuth 2.14 tools·Online229ms·30d uptime: 100%·Last checked 18m ago

Radar MCP exposes Cloudflare's Internet-observability datasets — traffic summaries, AS details, routing security events and URL scans — through an OAuth-protected remote endpoint.

https://radar.mcp.cloudflare.com/mcp

SSEhttps://radar.mcp.cloudflare.com/sse

Provider: Cloudflare ↗
Source: https://github.com/cloudflare/mcp-server-cloudflare ↗
Categories: ☁️ Cloud, Infrastructure & DevOps 🔍 Documentation, Search & Context

中文简介

Cloudflare Radar 的 MCP 服务器，提供互联网规模数据：HTTP 流量趋势、ASN 信息、BGP 劫持与 URL 扫描。

HTTP + SSEhttps://radar.mcp.cloudflare.com/mcp

Legacy SSE endpoint

SSEhttps://radar.mcp.cloudflare.com/sse

Install in Cursor →

Or add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "cloudflare-radar": {
      "url": "https://radar.mcp.cloudflare.com/mcp"
    }
  }
}

🔬 Test Live in Online Inspector 🔐 Audit OAuth 2.1 Config

🧰 Tools exposed by Cloudflare Radar MCP (4)

Tool	Safety	Description	Parameters
get_http_traffic_summary	🟢 Read	Get HTTP traffic summary for a location or ASN over a time range.	location: stringasn: stringdateRange: string
get_as_details	🟢 Read	Get details about an autonomous system (ASN).	asn*: string
get_bgp_hijacks	🟢 Read	List recent BGP hijack and route-leak events.	asn: stringdateRange: string
scan_url	🟢 Read	Submit a URL for Cloudflare URL Scanner analysis.	url*: string

🔐 OAuth 2.1 & Security

Auth type: OAuth 2.1
Dynamic Client Registration: ✅ Supported
PKCE S256: ✅ Supported
Protected resource metadata: https://radar.mcp.cloudflare.com/.well-known/oauth-protected-resource (expected location)

🔐 Audit OAuth 2.1 Config →

🧩 Recommended Agent Skills

Networking & security skills ↗

📖 Guide

Cloudflare Radar MCP — Remote MCP Server

Radar is Cloudflare's public window into how the Internet is behaving, and its MCP server puts the same data — HTTP traffic summaries by location, autonomous-system details, BGP hijack reports and URL scans — inside your agent. Useful for threat research, outage triage and net-ops questions.

Endpoint & Transport

Endpoint URL: https://radar.mcp.cloudflare.com/mcp
Legacy SSE endpoint: https://radar.mcp.cloudflare.com/sse
Transport: Streamable HTTP + legacy SSE

Authentication

Cloudflare Radar MCP uses OAuth 2.1 — the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow — PKCE and Dynamic Client Registration, so no manual client setup is needed — and simply open a browser consent screen.

Available Tools (4)

Tool	Safety	Description
`get_http_traffic_summary`	read	Get HTTP traffic summary for a location or ASN over a time range.
`get_as_details`	read	Get details about an autonomous system (ASN).
`get_bgp_hijacks`	read	List recent BGP hijack and route-leak events.
`scan_url`	read	Submit a URL for Cloudflare URL Scanner analysis.

Connect in 30 Seconds

Claude Code — one command:

claude mcp add --transport http cloudflare-radar https://radar.mcp.cloudflare.com/mcp

Cursor — add to ~/.cursor/mcp.json:

{ "mcpServers": { "cloudflare-radar": { "url": "https://radar.mcp.cloudflare.com/mcp" } } }

VS Code — add to .vscode/mcp.json:

{ "servers": { "cloudflare-radar": { "type": "http", "url": "https://radar.mcp.cloudflare.com/mcp" } } }

Claude Desktop & stdio clients — bridge with mcp-remote:

{ "mcpServers": { "cloudflare-radar": { "command": "npx", "args": ["-y", "mcp-remote", "https://radar.mcp.cloudflare.com/mcp"] } } }

On first connect your client opens a browser OAuth consent screen — approve it and tools become available immediately.

Troubleshooting

401 Unauthorized on connect — that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact WWW-Authenticate challenge.
Which URL should I use? Prefer https://radar.mcp.cloudflare.com/mcp (Streamable HTTP). The SSE URL is only for older clients pinned to the pre-2025-03-26 spec.
"Session expired" / stale Mcp-Session-Id — just re-send initialize; stateless clients can ignore session headers entirely.
OAuth-protected; a free Cloudflare account is sufficient.
Data freshness matches radar.cloudflare.com's public datasets.

🚀 How to Connect

Copy the Cloudflare Radar MCP endpoint URL
The remote endpoint is https://radar.mcp.cloudflare.com/mcp. A legacy SSE endpoint is also available at https://radar.mcp.cloudflare.com/sse.
Add it to your MCP client
Claude Code: claude mcp add --transport http cloudflare-radar https://radar.mcp.cloudflare.com/mcp. Cursor: add "cloudflare-radar": { "url": "https://radar.mcp.cloudflare.com/mcp" } under mcpServers in ~/.cursor/mcp.json. Other clients work similarly.
Complete the OAuth consent
On first connection your client opens a Cloudflare consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
Verify with the online inspector
Paste https://radar.mcp.cloudflare.com/mcp into remotemcp.net/inspector, run initialize and tools/list, and confirm Cloudflare Radar MCP's 4 tools respond.

❓ FAQ

What is the Cloudflare Radar MCP remote MCP endpoint?

The primary endpoint is https://radar.mcp.cloudflare.com/mcp, with a legacy SSE endpoint at https://radar.mcp.cloudflare.com/sse. It is an official first-party server operated by Cloudflare, speaking the Streamable HTTP + legacy SSE transport.

Should I use Cloudflare Radar MCP's /mcp or /sse endpoint?

Use https://radar.mcp.cloudflare.com/mcp — Streamable HTTP is the current MCP transport and what every modern client defaults to. https://radar.mcp.cloudflare.com/sse exists only for clients still on the legacy HTTP+SSE transport from the 2024 spec.

How do I authenticate with Cloudflare Radar MCP?

Cloudflare Radar MCP uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen. Dynamic Client Registration is supported, so compliant clients register themselves automatically.

I'm getting a 401 Unauthorized from Cloudflare Radar MCP — what's wrong?

A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.

Which MCP clients work with Cloudflare Radar MCP?

Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http cloudflare-radar https://radar.mcp.cloudflare.com/mcp`), VS Code Copilot, ChatGPT connectors, Windsurf, and Claude Desktop via the `mcp-remote` bridge.

What tools does Cloudflare Radar MCP expose?

4 tools are cataloged in this directory — including `get_http_traffic_summary`, `get_as_details`, `get_bgp_hijacks` and more. Use our online inspector to fetch the live tool list straight from the endpoint.

🔗 Connect Guides

Cursor

Connect Cloudflare Radar MCP →

Claude

Connect Cloudflare Radar MCP →

Claude Code

Connect Cloudflare Radar MCP →

VS Code

Connect Cloudflare Radar MCP →

ChatGPT

Connect Cloudflare Radar MCP →

Windsurf

Connect Cloudflare Radar MCP →

📛 Embed Status Badge in README

[![Remote MCP Status](https://remotemcp.net/api/badge/status/cloudflare-radar.svg)](https://remotemcp.net/servers/cloudflare-radar)

[![Test in Inspector](https://remotemcp.net/api/badge/inspect/cloudflare-radar.svg)](https://remotemcp.net/inspector?url=https%3A%2F%2Fradar.mcp.cloudflare.com%2Fmcp)