Webflow Webflow MCP Server

@iflow-mcp/webflow-webflow-mcp-server npm v1.0.1

Published by @iflow-mcp — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

A Node.js server implementing Model Context Protocol (MCP) for Webflow using the [Webflow JavaScript SDK](https://github.com/webflow/js-webflow-api). Enable AI agents to interact with Webflow APIs. Learn more about Webflow's Data API in the [developer doc

View on npm ↗ Raw report (JSON) ↗

Trust grade

95/100

Last scanned 2026-09-07 get badge →

Trust

A · 95/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.

A Why this grade threat 100 − adoption risk = 95/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 − 5 = 95. 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:

Points	Adoption-risk factor
−3	capability blast radius (moderate) — client exposure if the model is manipulated
−2	publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 20

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

data_pages_toolingests untrusted input
ask_webflow_aino sensitive capability
asset_toolno sensitive capability
data_cms_toolno sensitive capability
data_comments_toolno sensitive capability
data_components_toolno sensitive capability
data_enterprise_toolno sensitive capability
data_scripts_toolno sensitive capability
data_sites_toolno sensitive capability
de_component_toolno sensitive capability

Show 10 more tools ↓

de_learn_more_about_stylesno sensitive capability
de_page_toolno sensitive capability
element_builderno sensitive capability
element_snapshot_toolno sensitive capability
element_toolno sensitive capability
get_designer_app_connection_infono sensitive capability
get_image_previewno sensitive capability
style_toolno sensitive capability
variable_toolno sensitive capability
webflow_guide_toolno sensitive capability

What this scan could not see

Tools were statically extracted from the published source (20 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

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.

Version	Score	Findings	Engine	Scanned
`v1.0.1` latest	A 95/100	0	1.13.0	2026-09-07

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.

Markdown (GitHub README)

[![MCP Trust Score](https://mcptrustchecker.com/registry/iflow-mcp-webflow-webflow-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/iflow-mcp-webflow-webflow-mcp-server)

HTML

<a href="https://mcptrustchecker.com/registry/iflow-mcp-webflow-webflow-mcp-server"><img src="https://mcptrustchecker.com/registry/iflow-mcp-webflow-webflow-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>

Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/iflow-mcp-webflow-webflow-mcp-server/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 @iflow-mcp/webflow-webflow-mcp-server --online

Use the free API → How scoring works