Cloudflare Blade MCP Server

cloudflare-blade-mcp npm v0.8.0 Source verified

Published by groupthink-dev — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Cloudflare platform MCP server — DNS, KV, D1, Tunnels, Workers, Pages, R2, Vectorize, AI, Cache with token-efficient defaults

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 78

Each tool and what it can reach — statically extracted from the published source.

  • cf_d1_queryreads sensitive data
  • cf_kv_list_keysreads sensitive data
  • cf_workers_list_secretsreads sensitive data
  • cf_ai_gateway_create_gatewayno sensitive capability
  • cf_ai_gateway_delete_gatewayno sensitive capability
  • cf_ai_gateway_get_gatewayno sensitive capability
  • cf_ai_gateway_get_logno sensitive capability
  • cf_ai_gateway_list_gatewaysno sensitive capability
  • cf_ai_gateway_list_logsno sensitive capability
  • cf_ai_gateway_update_gatewayno sensitive capability
Show 68 more tools ↓
  • cf_ai_search_queryno sensitive capability
  • cf_cache_purgeno sensitive capability
  • cf_d1_create_databaseno sensitive capability
  • cf_d1_delete_databaseno sensitive capability
  • cf_d1_describe_tableno sensitive capability
  • cf_d1_executeno sensitive capability
  • cf_d1_exportno sensitive capability
  • cf_d1_get_databaseno sensitive capability
  • cf_d1_list_databasesno sensitive capability
  • cf_d1_list_tablesno sensitive capability
  • cf_dns_bulk_createno sensitive capability
  • cf_dns_bulk_updateno sensitive capability
  • cf_dns_create_recordno sensitive capability
  • cf_dns_delete_recordno sensitive capability
  • cf_dns_export_recordsno sensitive capability
  • cf_dns_get_recordno sensitive capability
  • cf_dns_get_zoneno sensitive capability
  • cf_dns_list_recordsno sensitive capability
  • cf_dns_list_zonesno sensitive capability
  • cf_dns_update_recordno sensitive capability
  • cf_kv_bulk_deleteno sensitive capability
  • cf_kv_bulk_putno sensitive capability
  • cf_kv_create_namespaceno sensitive capability
  • cf_kv_deleteno sensitive capability
  • cf_kv_delete_namespaceno sensitive capability
  • cf_kv_getno sensitive capability
  • cf_kv_list_namespacesno sensitive capability
  • cf_kv_putno sensitive capability
  • cf_pages_get_deploymentno sensitive capability
  • cf_pages_get_projectno sensitive capability
  • cf_pages_list_deploymentsno sensitive capability
  • cf_pages_list_domainsno sensitive capability
  • cf_pages_list_projectsno sensitive capability
  • cf_pages_purge_build_cacheno sensitive capability
  • cf_pages_rollbackno sensitive capability
  • cf_r2_create_bucketno sensitive capability
  • cf_r2_delete_bucketno sensitive capability
  • cf_r2_get_bucketno sensitive capability
  • cf_r2_list_bucketsno sensitive capability
  • cf_tunnel_createno sensitive capability
  • cf_tunnel_deleteno sensitive capability
  • cf_tunnel_getno sensitive capability
  • cf_tunnel_listno sensitive capability
  • cf_tunnel_list_configsno sensitive capability
  • cf_tunnel_list_connectionsno sensitive capability
  • cf_tunnel_update_configno sensitive capability
  • cf_vectorize_create_indexno sensitive capability
  • cf_vectorize_create_metadata_indexno sensitive capability
  • cf_vectorize_delete_indexno sensitive capability
  • cf_vectorize_delete_metadata_indexno sensitive capability
  • cf_vectorize_get_indexno sensitive capability
  • cf_vectorize_get_index_infono sensitive capability
  • cf_vectorize_list_indexesno sensitive capability
  • cf_vectorize_list_metadata_indexesno sensitive capability
  • cf_workers_ai_list_modelsno sensitive capability
  • cf_workers_ai_run_modelno sensitive capability
  • cf_workers_create_deploymentno sensitive capability
  • cf_workers_delete_bindingno sensitive capability
  • cf_workers_delete_secretno sensitive capability
  • cf_workers_get_schedulesno sensitive capability
  • cf_workers_get_scriptno sensitive capability
  • cf_workers_get_settingsno sensitive capability
  • cf_workers_list_deploymentsno sensitive capability
  • cf_workers_list_scriptsno sensitive capability
  • cf_workers_list_versionsno sensitive capability
  • cf_workers_put_schedulesno sensitive capability
  • cf_workers_put_secretno sensitive capability
  • cf_workers_upsert_bindingno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.8.0 latest A 97/100 0 1.12.1 2026-07-28

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/cloudflare-blade-mcp/badge.svg)](https://mcptrustchecker.com/registry/cloudflare-blade-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/cloudflare-blade-mcp"><img src="https://mcptrustchecker.com/registry/cloudflare-blade-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/cloudflare-blade-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan cloudflare-blade-mcp --online

Use the free API → How scoring works

More in Developer Tools