Cloudflare Radar
NPM · @PIPEWORX/MCP-CLOUDFLARE-RADAR · 2 COMPONENTS
Cloudflare Radar MCP — internet observatory (traffic, attacks, BGP, quality)
Available components
Last scanned (23 hours ago)
Scores higher than 77% of npm servers
Category Monitoring and Observability
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-cloudflare-radar). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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.
- 3 Nov 26 +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.
- 1 Nov 26 +27
- Known CVEs: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 31 Oct 26 −26
- Known CVEs: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Dependency health: pass → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 81
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 4 Nov 2026 · Analysed npm/@pipeworx/mcp-cloudflare-radar@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-cloudflare-radar |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-cloudflare-radar/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3612115381 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:9010e42f474319f748bf966d9af8c064e03ab9edc1164ef5555be6365f9d5a3c40d2a3a5aaddd37e8d8cfe896b8532374cc1a695f298d9e633fef2825 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
attack_summary ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
bgp_leaks ~68
Recent BGP route-leak events detected by Cloudflare. Returns leaker AS, victim AS, originated prefixes, start/end times.
| Name | Type | Req | Description |
|---|---|---|---|
| date_range | string | – | Lookback window (default 28d) |
| limit | number | – | 1-500 (default 50) |
No output schema declared.
No examples provided.
internet_quality ~118
Internet Quality Index (IQI) summary — bandwidth, latency, jitter, packet loss — current value + change vs prior period. Optionally filtered to a 2-letter location code.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
radar_ai_bots ~238
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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". |
No output schema declared.
No examples provided.
radar_domain_rank ~207
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | ISO date (YYYY-MM-DD) for a historical ranking snapshot. Omit for the latest. |
| domain | string | yes | Domain to look up, e.g. "reddit.com" (no scheme/path). |
No output schema declared.
No examples provided.
radar_top_domains ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
top_locations ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date_range | string | – | Lookback window (default 28d) |
| limit | number | – | 1-100 (default 10) |
| metric | string | – | http_requests | dns_queries | attacks (default http_requests) |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-cloudflare-radar
claude mcp add pipeworx-io-cloudflare-radar -- npx -y @pipeworx/mcp-cloudflare-radar
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 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 4 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.