@mrfentmen/cloudflare-mcp

MCPcommunity
v1.1.2UnknownMITUpdated 9d agonpmGitHub

Query Cloudflare v4 (API token; set CLOUDFLARE_API_TOKEN, Bearer): zones, accounts, DNS records.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
13Downloads/wk
9d agoLast update
Package
AuthorUnknown
LicenseMIT
Version1.1.2
Sourcenpm+mcp-registry
npm@mrfentmen/cloudflare-mcp
GitHubmrfentmen/premium-mcps
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface13 tools · none privileged
Security scan✓ Cleanv1.1.2 · 7d agoHow well does this scan work?
EvalsNone
IndexedOct 19, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

13 tools · none privileged
Statically extracted from the published packagev1.1.2 · 7d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_zonesCloudflare zones (domains) in the account.

Cloudflare zones (domains) in the account.

No input schema was published for this tool.

list_accountsCloudflare accounts the token can reach.

Cloudflare accounts the token can reach.

No input schema was published for this tool.

list_dnsDNS records in one zone id, with type and TTL.

DNS records in one zone id, with type and TTL.

No input schema was published for this tool.

zone_detailsSingle zone.

Single zone.

No input schema was published for this tool.

dns_recordSingle record.

Single record.

No input schema was published for this tool.

firewall_rulesZone firewall.

Zone firewall.

No input schema was published for this tool.

page_rulesZone page rules.

Zone page rules.

No input schema was published for this tool.

workersAccount scripts.

Account scripts.

No input schema was published for this tool.

analytics24h dashboard.

24h dashboard.

No input schema was published for this tool.

tunnelsCloudflare tunnels.

Cloudflare tunnels.

No input schema was published for this tool.

zone_settingsEvery tunable on a Cloudflare zone, defaulting to just the ones that differ from Cloudflare's default. Marks the settings that affect TLS, HTTPS enforcement, bot checks, protocol support and caching, and warns when the API returned fewer settings than it reports.

Every tunable on a Cloudflare zone, defaulting to just the ones that differ from Cloudflare's default. Marks the settings that affect TLS, HTTPS enforcement, bot checks, protocol support and caching, and warns when the API returned fewer settings than it reports.

No input schema was published for this tool.

zone_rulesetsThe rulesets configured on a zone, grouped by phase, with each phase explained in plain words. Phase rules are where WAF custom rules, Super Bot Fight Mode, IP blocking, dynamic redirects, transforms and rate limiting actually live, and they sit alongside any legacy page rules.

The rulesets configured on a zone, grouped by phase, with each phase explained in plain words. Phase rules are where WAF custom rules, Super Bot Fight Mode, IP blocking, dynamic redirects, transforms and rate limiting actually live, and they sit alongside any legacy page rules.

No input schema was published for this tool.

origin_pull_certificatesOrigin pull (authenticated origin pull) certificates on a zone, with bound hostnames, issuer, upload time and days until expiry. Flags anything already expired or expiring within a fortnight, and says what an empty result means for origin exposure.

Origin pull (authenticated origin pull) certificates on a zone, with bound hostnames, issuer, upload time and days until expiry. Flags anything already expired or expiring within a fortnight, and says what an empty result means for origin exposure.

No input schema was published for this tool.

13 of 13 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Query Cloudflare v4 (API token; set CLOUDFLARE_API_TOKEN, Bearer): zones, accounts, DNS records.

Keywords
mcpcloudflarednscdninfra
Alternatives
Comparing tool surfaces…

Tools exposed

13 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-19 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

55 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+43 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in cloud platforms