ToolsMCP
MCP Cloudflare DNS
Listed in the official MCP Registry with an installable pypi package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- ayo-fam (GitHub)
- Prerequisites
- Install mcp-cloudflare-dns from pypi (stdio transport). Declares 1 secret input. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.1.1 · updated
- Official links
Publisher’s description
Cloudflare DNS MCP server: manage zones, records, cache purge, and page rules.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.1.1, registry status active. 1 package (pypi)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- ayo-fam (GitHub)
- Version observed
- 0.1.1
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.Ayo-Fam%2Fmcp-cloudflare-dns/versions/0.1.1
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Inspect and manage cloud resources | Publisher description mentions “cloudflare”, “dns”. | No connection check or task run. Capability is as described by the publisher. | Rule cloud-infrastructure matched: “cloudflare”, “dns”. Rule cloud-infrastructure. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
mcp-cloudflare-dns(pypi, stdio, 1 secret input)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.Ayo-Fam/mcp-cloudflare-dns
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.