# Cloudflare Radar (npm · @pipeworx/mcp-cloudflare-radar)

Cloudflare Radar MCP — internet observatory (traffic, attacks, BGP, quality)

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 80/100, [markdown](https://verifymcp.io/servers/pipeworx-io-cloudflare-radar/cloudflare-radar-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-cloudflare-radar/cloudflare-radar-mcp)
- npm · `@pipeworx/mcp-cloudflare-radar`: 84/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-cloudflare-radar/pipeworx-mcp-cloudflare-radar.md), [page](https://verifymcp.io/servers/pipeworx-io-cloudflare-radar/pipeworx-mcp-cloudflare-radar)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-cloudflare-radar`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-cloudflare-radar).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 998 tokens (~142/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Cloudflare Radar MCP server?

Cloudflare Radar runs locally as an npm package, launched with npx -y @pipeworx/mcp-cloudflare-radar. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-cloudflare-radar -- npx -y @pipeworx/mcp-cloudflare-radar
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-cloudflare-radar": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-cloudflare-radar"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-cloudflare-radar": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-cloudflare-radar"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-cloudflare-radar -- npx -y @pipeworx/mcp-cloudflare-radar
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-cloudflare-radar": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-cloudflare-radar"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-cloudflare-radar --command npx --arg -y --arg @pipeworx/mcp-cloudflare-radar
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-cloudflare-radar:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-cloudflare-radar"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-cloudflare-radar": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-cloudflare-radar"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-cloudflare-radar -t stdio -c npx -a -y @pipeworx/mcp-cloudflare-radar
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-cloudflare-radar": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-cloudflare-radar"
      ]
    }
  }
}
```

## 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-11-05 (score 84, +1)

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

### 2026-11-03 (score 83, +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-11-01 (score 82, +27)

- [security improvement] Known CVEs: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-10-31 (score 55, −26)

- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [functional regression] Dependency health: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 81)

First indexed and scored.

## MCP tools (7)

### `internet_quality` (~118 tokens)

Internet Quality Index (IQI) summary — bandwidth, latency, jitter, packet loss — current value + change vs prior period. Optionally filtered to a 2-letter location code.

Input parameters:

- `date_range` (string): Lookback window: 1d | 7d | 14d | 28d | 12w | 24w | 52w (default 28d)
- `location` (string): 2-letter location code (e.g., "US", "DE", "JP"). Omit for global.

### `attack_summary` (~103 tokens)

Layer-7 DDoS attack mix over a time window. Returns the percentage breakdown of attacks by mitigation product or attack vector. Filter by location to scope to a region/country.

Input parameters:

- `date_range` (string): Lookback window (default 28d)
- `dimension` (string): Summary dimension: mitigation_product | http_method | http_version | ip_version | bot_class (default mitigation_product)
- `location` (string): 2-letter location code (optional)

### `top_locations` (~96 tokens)

Top locations by a metric. metric=http_requests returns countries by share of HTTP traffic; metric=dns_queries by DNS; metric=attacks by attack origin. Returns ranked list with share percentages.

Input parameters:

- `date_range` (string): Lookback window (default 28d)
- `limit` (number): 1-100 (default 10)
- `metric` (string): http_requests | dns_queries | attacks (default http_requests)

### `bgp_leaks` (~68 tokens)

Recent BGP route-leak events detected by Cloudflare. Returns leaker AS, victim AS, originated prefixes, start/end times.

Input parameters:

- `date_range` (string): Lookback window (default 28d)
- `limit` (number): 1-500 (default 50)

### `radar_domain_rank` (~207 tokens)

Is this domain widely visited, or nowhere? Returns a single domain's Cloudflare Radar popularity: an exact `rank` for domains inside the global top 100, otherwise only a `bucket` (e.g. "200" = top 200, "100000" = top 100k) — `rank` is null for everything outside the top 100, so do not build logic on it populating. Below Radar's tracked ceiling (bucket ">200000") there is NO signal at all: Radar does not verify domain existence, so a real-but-obscure site and a domain that has never existed come back identically. Read `ranked` and `interpretation`, not just `bucket`, to tell those apart.

Input parameters:

- `date` (string): ISO date (YYYY-MM-DD) for a historical ranking snapshot. Omit for the latest.
- `domain` (string, required): Domain to look up, e.g. "reddit.com" (no scheme/path).

### `radar_top_domains` (~112 tokens)

The most-visited domains on the internet, globally or filtered to one country. Use to see what dominates traffic, or as the reference list to compare a rank against.

Input parameters:

- `date` (string): ISO date (YYYY-MM-DD) for a historical top-list. Omit for the latest.
- `limit` (number): 1-100 (default 20)
- `location` (string): 2-letter location code (e.g., "US", "DE", "JP"). Omit for global.

### `radar_ai_bots` (~238 tokens)

Cloudflare Radar AI bots: which AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Bytespider, Amazonbot, ...) generate how much of AI-bot traffic. Returns percentage shares by user agent, by crawl purpose (training, search, user action) or by industry of the crawled sites, over a date range, globally or for one country. Pass user_agent to get a single crawler's share; an unknown user agent returns found:false.

Input parameters:

- `date_range` (string): Lookback window: 1d | 7d | 14d | 28d | 12w | 24w | 52w (default 28d)
- `dimension` (string): user_agent | crawl_purpose | industry (default user_agent)
- `limit` (number): Max rows returned, 1-100 (default 25)
- `location` (string): 2-letter country code (e.g., "US"). Omit for global.
- `user_agent` (string): Only with dimension=user_agent: look up one crawler by name, e.g. "GPTBot".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-cloudflare-radar/pipeworx-mcp-cloudflare-radar#diagnostics

## Score history

- 2026-11-05: 84
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 55
- 2026-10-30: 81
- 2026-10-29: 81

## Common questions

### What is the Cloudflare Radar MCP server?

Cloudflare Radar is an MCP server listed in the public MCP registry as io.github.pipeworx-io/cloudflare-radar. Cloudflare Radar MCP, internet observatory (traffic, attacks, BGP, quality). This page covers its npm package (@pipeworx/mcp-cloudflare-radar).

### Is the Cloudflare Radar MCP server safe to use?

Cloudflare Radar scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Cloudflare Radar MCP server expose?

Cloudflare Radar exposes 7 tools: internet_quality, attack_summary, top_locations, bgp_leaks, radar_domain_rank, and 2 more. Their descriptions and schemas cost roughly 942 tokens of context every time the server is loaded.

### Is the Cloudflare Radar MCP server still maintained?

Cloudflare Radar is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Cloudflare Radar MCP server under?

Cloudflare Radar declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-cloudflare-radar
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-cloudflare-radar
- Repository: https://github.com/pipeworx-io/mcp-cloudflare-radar
- Website: https://pipeworx.io/packs/cloudflare-radar
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-cloudflare-radar/pipeworx-mcp-cloudflare-radar.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-cloudflare-radar/pipeworx-mcp-cloudflare-radar.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-cloudflare-radar/pipeworx-mcp-cloudflare-radar