Quick answer
Cloudflare Radar exposes WebMCP tools so a compatible browser agent can filter locations and dates, search pages or entities, navigate sections, scan URLs, open domain reports, and test post-quantum TLS support through structured interfaces. Radar uses both JavaScript imperative tools and annotated-form declarative tools.
These tools drive functions already present in the UI. They do not grant extra business authority, prove an agent interpreted the result correctly, or remove browser compatibility and preview-status risks.
WebMCP versus Radar Researcher
| Surface | Primary user | Purpose |
|---|---|---|
| Radar Researcher | Human analyst | Ask questions and receive API-grounded explanations and charts |
| Radar WebMCP | Browser agent acting for a user | Discover and invoke structured Radar page actions |
| Radar API / MCP server | Developer or agent runtime | Query Radar data programmatically outside a page UI |
Choose the narrowest surface that fits. A human analyst may prefer Researcher; a browser assistant navigating Radar can use WebMCP; a reproducible data pipeline should usually use the documented API directly.
Imperative tools
Cloudflare says Radar registers JavaScript tools that call the same code powering the UI. Documented examples include:
- filtering to a country, region, continent, or ASN;
- changing the date range;
- searching pages, sections, domains, ASNs, IPs, and other entities;
- jumping to a Radar section.
Because the tool drives current page state, capture the resulting URL, filters, dates, and visible chart before using it as evidence.
Declarative tools
Declarative WebMCP annotates existing HTML forms so compatible agents can treat them as tools. Cloudflare cites Radar’s URL Scanner, domain report lookup, and post-quantum TLS key-exchange test.
A structured form interface is more robust than coordinate clicking, but input validation and result interpretation still matter. URL scanning can send a target to an external service; agents should confirm scope, authorization, and sensitive URL contents before submission.
Progressive enhancement and compatibility
Cloudflare describes Radar’s integration as progressive enhancement. If the browser lacks WebMCP, tools do not appear and the site works normally.
The wider Cloudflare WebMCP offering is a developer preview and the standard is emerging. Cloudflare’s August 6 post described experimental Chrome support and a Dashboard preview that injects a same-origin bridge. Do not assume the API shape, browser version, tool set, or enterprise policy is stable.
Browser-agent safety checklist
- Discover the current tool list rather than assuming names.
- Show the user which Radar action will run and with what arguments.
- Validate locations, entities, dates, and URLs.
- Treat page and tool output as untrusted content.
- Require confirmation before submissions that create external work or disclose data.
- Capture the resulting page state and API-backed evidence.
- Keep a UI fallback for unsupported browsers.
- Re-test after Radar, browser, or WebMCP changes.
WebMCP makes navigation more structured; it is not an authorization protocol for the user’s broader goals.
Frequently asked questions
What does WebMCP do on Cloudflare Radar?
It lets compatible browser agents discover and call structured tools for Radar functionality instead of reverse-engineering page controls.
What is the imperative WebMCP API?
Radar uses JavaScript-registered tools to drive existing UI functionality such as changing location or date filters, searching entities, and navigating sections.
What is declarative WebMCP?
It exposes existing HTML forms as tools through annotations. Cloudflare cites Radar URL scanning, domain reports, and post-quantum TLS tests as examples.
What happens in a browser without WebMCP?
Cloudflare describes Radar’s integration as progressive enhancement: the tools are absent and the existing human interface continues to work.
Continue by task
- Radar Researcher beta guide
- Code Mode and MCP architecture
- Internet outage analysis workflow
- Radar research planner
Official sources
- Cloudflare: Introducing Radar Researcher
- Cloudflare: Give any website a WebMCP interface
- WebMCP draft specification
Source check: August 8, 2026. Verify current standard status, browser support, tool names, preview access, security behavior, and Radar functionality before automation.