flowzap MCP server
io.github.flowzap-xyz/flowzapflowzap-xyzstreamable-httpv2.2.1Scanned
Create workflow, sequence, architecture, and mind map diagrams via AI assistants.
13 tools: 1 can delete or cancel things, 10 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 7 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the flowzap MCP server can do
The flowzap MCP server is published by the GitHub account flowzap-xyz. It has 13 tools. It can delete or cancel things (1 tool: flowzap_apply_change) and create or change data (10 tools: flowzap_validate, flowzap_fix, flowzap_mindmap_validate, flowzap_mindmap_approve and 6 more). 2 tools only read.
1 tool brings in text other people can write (flowzap_compliance_check).
The fixed checks matched 7 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 8, 2026, version 2.2.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
13 tools
Deletes or cancels 1Claude Code: deny
flowzap_apply_changeApply structured patch operations (insert/remove/update nodes or edges) to FlowZap Code.No findings
Why it is in this group
- The name "flowzap_apply_change" says "apply": a word for a change.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Apply structured patch operations (insert/remove/update nodes or edges) to FlowZap Code. Returns an advisory quality block listing process defects (e.g. a step with no incoming edge, more than one start circle); the diagram is still created — fix the code and call again.
Annotations the server declares
- title: Patch an Existing Diagram
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
Changes things 10Claude Code: ask
flowzap_artifact_to_diagramConvert HTTP logs, OpenAPI specs, or code snippets into a FlowZap diagram.No findings
Why it is in this group
- The description's first verb is "convert": a word for a change.
Description, as the server wrote it Convert HTTP logs, OpenAPI specs, or code snippets into a FlowZap diagram.
Annotations the server declares
- title: Convert Logs or Specs to Diagram
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
flowzap_compliance_checkRun an automated SOC2 / GDPR / PIPL / EU AI Act architectural compliance review of a FlowZap Code data flow.Reads text others write1 finding
Why it is in this group
- The description's first verb is "run": a word for a change.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "flowzap_compliance_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "run": a word for a change.
Description, as the server wrote it Run an automated SOC2 / GDPR / PIPL / EU AI Act architectural compliance review of a FlowZap Code data flow. Returns a Markdown summary of findings (control · status · detail · recommendation) for each framework whose elements are detectable in the diagram. Free quota: 10 free compliance reviews per client per rolling 30-day period. For unlimited manual reviews, paste your code at https://flowzap.xyz/soc2-gdpr-pipl-compliance-checker. Processor disclosure (GDPR Art. 13): analysis powered by Deepseek (Hangzhou DeepSeek AI, China) — see https://flowzap.xyz/legal/subprocessors. This is an advisory architectural review, not legal advice.
Annotations the server declares
- title: Review Diagram Compliance
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
flowzap_create_playgroundCreate a shareable FlowZap playground URL.No findings
Why it is in this group
- The name "flowzap_create_playground" says "create": a word for a change.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it Create a shareable FlowZap playground URL. Set view to 'architecture', 'sequence', or 'mindmap' when appropriate. Returns an advisory quality block listing process defects (e.g. a step with no incoming edge, more than one start circle); the diagram is still created — fix the code and call again.
Annotations the server declares
- title: Create Shareable Diagram
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
flowzap_export_graphParse FlowZap Code into a structured JSON graph (lanes, nodes, edges).1 finding
Why it is in this group
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "flowzap_export_graph" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it Parse FlowZap Code into a structured JSON graph (lanes, nodes, edges).
Annotations the server declares
- title: Export Diagram as Graph
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
flowzap_fixDeterministically repair mechanical FlowZap Code errors: non-sequential node numbering, inferred edge handles, node/edge label syntax, missing lane display labels, emoji and non-pr…1 finding
Why it is in this group
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "flowzap_fix" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it Deterministically repair mechanical FlowZap Code errors: non-sequential node numbering, inferred edge handles, node/edge label syntax, missing lane display labels, emoji and non-printable characters. Returns the repaired code plus the list of corrections that were applied. Errors that cannot be repaired are reported as-is — the repairer never invents content.
Annotations the server declares
- title: Repair FlowZap Code
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
flowzap_mindmap_approveCheck if valid FlowZap Code is suitable for Mind Map rendering.1 finding
Why it is in this group
- The name "flowzap_mindmap_approve" says "approve": a word for a change.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "flowzap_mindmap_approve" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "flowzap_mindmap_approve" says "approve": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check Mind Map Readiness
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
flowzap_mindmap_create_playgroundCreate a FlowZap playground session that opens directly in Mind Map view (?view=mindmap).No findings
Why it is in this group
- The name "flowzap_mindmap_create_playground" says "create": a word for a change.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it 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.
Annotations the server declares
- title: Create Shareable Mind Map
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
flowzap_mindmap_templateGenerate a ready-to-extend FlowZap Code skeleton for a Mind Map.1 finding
Why it is in this group
- The description's first verb is "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "flowzap_mindmap_template" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "generate": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Generate Mind Map Skeleton
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
flowzap_mindmap_validateValidate FlowZap Code syntax specifically for Mind Map diagrams.1 finding
Why it is in this group
- The name "flowzap_mindmap_validate" says "validate": a word for reading.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "flowzap_mindmap_validate" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "flowzap_mindmap_validate" says "validate": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Validate Mind Map Code
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
flowzap_validateValidate FlowZap Code syntax.1 finding
Why it is in this group
- The name "flowzap_validate" says "validate": a word for reading.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "flowzap_validate" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "flowzap_validate" says "validate": a word for reading.
Description, as the server wrote it Validate FlowZap Code syntax. Returns errors and stats.
Annotations the server declares
- title: Validate FlowZap Code
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
flowzap_diffCompare two FlowZap Code versions and return a structured diff.No findings
Why it is in this group
- The name "flowzap_diff" says "diff": a word for reading.
Description, as the server wrote it Compare two FlowZap Code versions and return a structured diff.
Annotations the server declares
- title: Compare Diagram Versions
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
flowzap_get_syntaxGet FlowZap Code syntax documentation and examples.No findings
Why it is in this group
- The name "flowzap_get_syntax" says "get": a word for reading.
Description, as the server wrote it Get FlowZap Code syntax documentation and examples.
Annotations the server declares
- title: Get FlowZap Code Syntax
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:04 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 11
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 11 tools that change things (1 destructive, 10 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://flowzap.xyz/mcp: tools/list returned 13 tools to an anonymous client, including flowzap_apply_change (destructive), flowzap_validate (write), flowzap_fix (write), flowzap_mindmap_validate (write), flowzap_mindmap_approve (write) and 6 more
Findings
Matches of fixed checks, with the text they matched.
- Warnflowzap_validate
The server marks "flowzap_validate" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "flowzap_validate" says "validate": a word for reading.
- Warnflowzap_fix
The server marks "flowzap_fix" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
The server marks "flowzap_mindmap_validate" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "flowzap_mindmap_validate" says "validate": a word for reading.
The server marks "flowzap_mindmap_approve" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "flowzap_mindmap_approve" says "approve": a word for a change.
The server marks "flowzap_mindmap_template" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "generate": a word for a change.
The server marks "flowzap_export_graph" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
Show 1 more findingShow fewer
The server marks "flowzap_compliance_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "run": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools13 changed.~13 changedView diff
- Changed:flowzap_apply_changeDeletes or cancelstitleannotations
- Changed:flowzap_artifact_to_diagramChanges thingstitleannotations
- Changed:flowzap_compliance_checkChanges thingstitleannotations
- Changed:flowzap_create_playgroundChanges thingstitleannotations
- Changed:flowzap_diffOnly readstitleannotations
- Changed:flowzap_export_graphChanges thingstitleannotations
- Changed:flowzap_fixChanges thingstitleannotations
- Changed:flowzap_get_syntaxOnly readstitleannotations
- Changed:flowzap_mindmap_approveChanges thingstitleannotations
- Changed:flowzap_mindmap_create_playgroundChanges thingstitleannotations
- Changed:flowzap_mindmap_templateChanges thingstitleannotations
- Changed:flowzap_mindmap_validateChanges thingstitleannotations
- Changed:flowzap_validateChanges thingstitleannotations
Tools2 changed.~2 changedView diff
- Changed:flowzap_apply_changeChanges thingsdescription
- Changed:flowzap_create_playgroundChanges thingsdescription
Install
Pinned to version 2.2.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http flowzap https://flowzap.xyz/mcpclaude mcp add --transport http flowzap https://flowzap.xyz/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__flowzap__flowzap_get_syntax",
"mcp__flowzap__flowzap_diff"
],
"ask": [
"mcp__flowzap__flowzap_validate",
"mcp__flowzap__flowzap_fix",
"mcp__flowzap__flowzap_mindmap_validate",
"mcp__flowzap__flowzap_mindmap_approve",
"mcp__flowzap__flowzap_mindmap_template",
"mcp__flowzap__flowzap_mindmap_create_playground",
"mcp__flowzap__flowzap_create_playground",
"mcp__flowzap__flowzap_export_graph",
"mcp__flowzap__flowzap_artifact_to_diagram",
"mcp__flowzap__flowzap_compliance_check"
],
"deny": [
"mcp__flowzap__flowzap_apply_change"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as flowzap. Review it before you use it.
Capability tags behind 1 rule
- mcp__flowzap__flowzap_compliance_check untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.flowzap-xyz/flowzap/verify?hash=f04149281b49c2cc572327aaf621b20792017d162d6a4eb63a2b0d5f7e102f41" | jq -e '.changed == false'Pinned hash f04149281b49, from Nov 8, 2026, 11:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.flowzap-xyz/flowzap/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.flowzap-xyz/flowzap)Source: MCP Registry · repository. Synced Nov 8, 2026, 12:17 UTC.
flowzap MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the flowzap MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 11 of which can change, send or delete something, and 7 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the flowzap MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: flowzap_apply_change.
Can the flowzap MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the flowzap MCP server have?
- 13 tools: 1 destructive, 10 write, 2 read. flowzap_apply_change, flowzap_validate, flowzap_fix, flowzap_mindmap_validate, flowzap_mindmap_approve, flowzap_mindmap_template, flowzap_mindmap_create_playground, flowzap_create_playground and 5 more.
Does the flowzap MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the flowzap MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the flowzap MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.