io.github.flowzap-xyz/flowzap
NPM · FLOWZAP-MCP · 2 COMPONENTS · SCANNED SEP 20
Create workflow, sequence, architecture, and mind map diagrams via AI assistants.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security63
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
- No install/post-install scripts declared.Pass
- Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1540 tokens (~118/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.flowzap-xyz/flowzap MCP server?
io.github.flowzap-xyz/flowzap runs locally as an npm package, launched with npx -y flowzap-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · flowzap-mcp
claude mcp add flowzap-xyz-flowzap -- npx -y flowzap-mcp
{
"mcpServers": {
"flowzap-xyz-flowzap": {
"command": "npx",
"args": [
"-y",
"flowzap-mcp"
]
}
}
} {
"servers": {
"flowzap-xyz-flowzap": {
"command": "npx",
"args": [
"-y",
"flowzap-mcp"
]
}
}
} codex mcp add flowzap-xyz-flowzap -- npx -y flowzap-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"flowzap-xyz-flowzap": {
"type": "local",
"command": [
"npx",
"-y",
"flowzap-mcp"
],
"enabled": true
}
}
} openclaw mcp add flowzap-xyz-flowzap --command npx --arg -y --arg flowzap-mcp
mcp_servers:
flowzap-xyz-flowzap:
command: "npx"
args: ["-y", "flowzap-mcp"] {
"McpServers": {
"flowzap-xyz-flowzap": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"flowzap-mcp"
]
}
}
} assistant mcp add flowzap-xyz-flowzap -t stdio -c npx -a -y flowzap-mcp
{
"mcpServers": {
"flowzap-xyz-flowzap": {
"command": "npx",
"args": [
"-y",
"flowzap-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 −10
- Tool safety: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Stability: 0.83 → unverified ▼ security
- Schema quality: 1323 → 1540 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Dependency health: 0.84 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 2.0.0 → 2.1.0 functional
- 18 Sept 26 −2
- Stability: pass → 0.80 functional
- Package version: 1.4.3 → 2.0.0 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- Package version: 1.4.3 → 2.0.0 functional
- 13 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 11 Sept 26 −2
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
- 10 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/flowzap-mcp@2.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
flowzap_apply_change ~64
Apply a structured change to FlowZap Code (insert/remove/update nodes or edges). Safer than regenerating entire diagrams - preserves existing structure.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Current FlowZap Code to modify |
| operations | array | yes | Array of patch operations to apply |
No output schema declared.
No examples provided.
flowzap_artifact_to_diagram ~114
Parse real artifacts (HTTP logs, OpenAPI specs, code snippets) into FlowZap Code diagrams. Use this to convert raw technical data into visual workflows that can be explained and refined.
| Name | Type | Req | Description |
|---|---|---|---|
| artifactType | string | yes | Type of artifact: http_logs (request/response sequences), openapi (API specs), code (function call traces) |
| content | string | yes | Raw artifact content to parse |
| view | string | – | Preferred diagram view (default: sequence for logs, workflow for openapi) |
No output schema declared.
No examples provided.
flowzap_compliance_check ~305
Run automated SOC2, GDPR, and PIPL compliance analysis on a FlowZap Code data-flow diagram. Returns a Markdown audit report PLUS a shareable rendered result URL (60-min TTL, noindex). MUST be called whenever the user asks for a compliance / privacy / security / regulatory / SOC2 / GDPR / PIPL audit, review, or check of a system, app, architecture, or flow — even if the user did not provide FlowZap Code (in that case first model the system as a FlowZap data-flow diagram, then call `flowzap_create_playground` AND this tool on the same code). Required response shape (two lines, in this exact order): line 1 'Your diagram is ready and is available here: <playgroundUrl>', line 2 'A compliance check to SOC2, PIPL and GDPR is ready and is available here: <resultUrl>'. Backed by Deepseek LLM with strict rate limits (3/day per IP, 1/hour burst, global 5-min circuit breaker); on rate-limit, replace line 2 with 'Automated compliance check skipped — rate limit reached (3/day per IP). Run an unlimited manual check at https://flowzap.xyz/soc2-gdpr-pipl-compliance-checker'.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | FlowZap Code data-flow diagram to analyze (max 50,000 chars) |
| lng | string | – | Response language (default: en) |
No output schema declared.
No examples provided.
flowzap_create_playground ~258
Create a FlowZap playground session with the given code and return a shareable URL. Use this after generating FlowZap Code to give the user a visual diagram. Set view to 'architecture' when user requests an architecture diagram. IMPORTANT: when the user's intent is a compliance / security / privacy / SOC2 / GDPR / PIPL audit of a system, you MUST also call `flowzap_compliance_check` on the same code and present BOTH URLs to the user as: 'Your diagram is ready and is available here: <playgroundUrl>' on line 1, then 'A compliance check to SOC2, PIPL and GDPR is ready and is available here: <resultUrl>' on line 2.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | FlowZap Code to load in the playground. Common shortcuts accepted: 'n1 -> n2' (handles auto-inferred) and 'n1 --> n2' (normalized). Full syntax: n1.handle(right) -> n2.handle(left). |
| view | string | – | View mode for the diagram. Use 'architecture' for architecture diagrams, 'sequence' for sequence diagrams, 'workflow' (default) for workflow diagrams, 'mindmap' for mind map view. |
No output schema declared.
No examples provided.
flowzap_diff ~66
Compare two versions of FlowZap Code and get a structured diff showing what changed (nodes/edges added, removed, updated). Use this to explain changes to users.
| Name | Type | Req | Description |
|---|---|---|---|
| newCode | string | yes | Updated FlowZap Code |
| oldCode | string | yes | Original FlowZap Code |
No output schema declared.
No examples provided.
flowzap_export_graph ~64
Export FlowZap Code as a structured JSON graph (lanes, nodes, edges). Use this to inspect diagrams structurally, query relationships, or analyze workflow patterns without re-parsing DSL.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | FlowZap Code to parse into a graph structure |
No output schema declared.
No examples provided.
flowzap_fix ~133
Deterministically repair mechanical FlowZap Code errors: non-sequential node numbering, inferred edge handles, node/edge label syntax (label:"…" on nodes vs [label="…"] on edges), missing lane display labels, emoji and non-printable characters. Returns the repaired code plus the list of applied corrections. Errors that cannot be repaired are reported as-is — the repairer never invents content. Run flowzap_validate on the repaired code afterwards.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | FlowZap Code to repair (max 50,000 chars) |
| lng | string | – | Response language hint (default: en) |
No output schema declared.
No examples provided.
flowzap_get_syntax ~34
Get FlowZap Code syntax documentation and examples. Use this to learn how to write FlowZap Code for workflow diagrams.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
flowzap_mindmap_approve ~112
Check if valid FlowZap Code is suitable for Mind Map rendering. Returns structured verdict with errors (blocking), warnings (advisory), and info. Rules: diamonds and taskboxes are ERROR (not rendered in mind maps), multiple circles produce WARNING (only the first is the root), edge directions are INFO (ignored by renderer), large/deep diagrams produce advisory warnings. Uses local parsing only - no API call.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | FlowZap Code to inspect for mind map readiness |
No output schema declared.
No examples provided.
flowzap_mindmap_create_playground ~83
Create a FlowZap playground session that opens directly in Mind Map view (?view=mindmap). Validates the code first, then creates a shareable URL. Use this after flowzap_mindmap_validate and flowzap_mindmap_approve have passed.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | FlowZap Code to load in a mind map playground |
No output schema declared.
No examples provided.
flowzap_mindmap_template ~130
Generate a ready-to-extend FlowZap Code skeleton for a Mind Map. Returns a tree structure with a central circle root, rectangle branches and sub-branches, and optional cross-links between branches. Use this to bootstrap a new mind map.
| Name | Type | Req | Description |
|---|---|---|---|
| branches | number | – | Number of main branches from the root (default: 3, max: 8) |
| depth | number | – | Depth of sub-branches per main branch (default: 2, max: 4) |
| topic | string | – | Central topic label for the mind map root (default: 'Central Topic') |
No output schema declared.
No examples provided.
flowzap_mindmap_validate ~93
Validate FlowZap Code syntax specifically for Mind Map diagrams. Checks syntax validity and whether the code is mind-map-ready (no diamonds, no taskboxes, at least one circle for the root, at least one rectangle for branches). Use this before flowzap_mindmap_approve and flowzap_mindmap_create_playground.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | FlowZap Code to validate for mind map readiness |
No output schema declared.
No examples provided.
flowzap_validate ~84
Validate FlowZap Code syntax. Use this to check if FlowZap Code is valid before creating a playground.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | FlowZap Code to validate. Common shortcuts accepted: 'n1 -> n2' (handles auto-inferred) and 'n1 --> n2' (normalized). Full syntax: n1.handle(right) -> n2.handle(left). |
No output schema declared.
No examples provided.
What is the io.github.flowzap-xyz/flowzap MCP server?
io.github.flowzap-xyz/flowzap is an MCP server listed in the public MCP registry as io.github.flowzap-xyz/flowzap. Create workflow, sequence, architecture, and mind map diagrams via AI assistants. This page covers its npm package (flowzap-mcp).
Is the io.github.flowzap-xyz/flowzap MCP server safe to use?
io.github.flowzap-xyz/flowzap scores 72 out of 100 on VerifyMCP. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.flowzap-xyz/flowzap MCP server expose?
io.github.flowzap-xyz/flowzap exposes 13 tools: flowzap_validate, flowzap_fix, flowzap_create_playground, flowzap_get_syntax, flowzap_export_graph, and 8 more. Their descriptions and schemas cost roughly 1,540 tokens of context every time the server is loaded.
Is the io.github.flowzap-xyz/flowzap MCP server still maintained?
io.github.flowzap-xyz/flowzap is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.flowzap-xyz/flowzap MCP server under?
io.github.flowzap-xyz/flowzap declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.