# io.github.flowzap-xyz/flowzap (remote · flowzap.xyz)

Create workflow, sequence, architecture, and mind map diagrams via AI assistants.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `flowzap.xyz`: 66/100 (this document), [markdown](https://verifymcp.io/servers/flowzap-xyz-flowzap/flowzap.md), [page](https://verifymcp.io/servers/flowzap-xyz-flowzap/flowzap)
- npm · `flowzap-mcp`: 72/100, [markdown](https://verifymcp.io/servers/flowzap-xyz-flowzap/flowzap-mcp.md), [page](https://verifymcp.io/servers/flowzap-xyz-flowzap/flowzap-mcp)

## Channel facts

- Endpoint: `https://flowzap.xyz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1054 tokens (~81/item across 13 items; 13 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 96% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.github.flowzap-xyz/flowzap MCP server?

io.github.flowzap-xyz/flowzap is a hosted endpoint at https://flowzap.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http flowzap-xyz-flowzap 'https://flowzap.xyz/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "flowzap-xyz-flowzap": {
      "url": "https://flowzap.xyz/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "flowzap-xyz-flowzap": {
      "type": "http",
      "url": "https://flowzap.xyz/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.flowzap-xyz-flowzap]
url = "https://flowzap.xyz/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "flowzap-xyz-flowzap": {
      "type": "remote",
      "url": "https://flowzap.xyz/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add flowzap-xyz-flowzap --url 'https://flowzap.xyz/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  flowzap-xyz-flowzap:
    url: "https://flowzap.xyz/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "flowzap-xyz-flowzap": {
      "Transport": "http",
      "Url": "https://flowzap.xyz/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add flowzap-xyz-flowzap -t streamable-http -u 'https://flowzap.xyz/mcp'
```

### Other

```json
{
  "mcpServers": {
    "flowzap-xyz-flowzap": {
      "type": "http",
      "url": "https://flowzap.xyz/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-20 (score 66)

First indexed and scored.

## MCP tools (13)

### `flowzap_validate` (~52 tokens)

Validate FlowZap Code syntax. Returns errors and stats.

Input parameters:

- `code` (string, required): FlowZap Code to validate
- `lng` (string): Language of the messages returned by this tool. Default: 'en'.

### `flowzap_fix` (~110 tokens)

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.

Input parameters:

- `code` (string, required): FlowZap Code to repair
- `lng` (string): Language of the messages returned by this tool. Default: 'en'.

### `flowzap_mindmap_validate` (~93 tokens)

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.

Input parameters:

- `code` (string, required): FlowZap Code to validate for mind map readiness

### `flowzap_mindmap_approve` (~112 tokens)

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.

Input parameters:

- `code` (string, required): FlowZap Code to inspect for mind map readiness

### `flowzap_mindmap_template` (~130 tokens)

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.

Input parameters:

- `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')

### `flowzap_mindmap_create_playground` (~83 tokens)

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.

Input parameters:

- `code` (string, required): FlowZap Code to load in a mind map playground

### `flowzap_create_playground` (~83 tokens)

Create a shareable FlowZap playground URL. Set view to 'architecture', 'sequence', or 'mindmap' when appropriate.

Input parameters:

- `code` (string, required): FlowZap Code to render
- `lng` (string): Language of the messages returned by this tool. Default: 'en'.
- `view` (string): View mode. Default: 'workflow'.

### `flowzap_get_syntax` (~20 tokens)

Get FlowZap Code syntax documentation and examples.

### `flowzap_export_graph` (~39 tokens)

Parse FlowZap Code into a structured JSON graph (lanes, nodes, edges).

Input parameters:

- `code` (string, required): FlowZap Code to parse

### `flowzap_artifact_to_diagram` (~58 tokens)

Convert HTTP logs, OpenAPI specs, or code snippets into a FlowZap diagram.

Input parameters:

- `artifactType` (string, required)
- `content` (string, required): Raw artifact content
- `view` (string): Preferred view mode

### `flowzap_diff` (~45 tokens)

Compare two FlowZap Code versions and return a structured diff.

Input parameters:

- `newCode` (string, required): Updated FlowZap Code
- `oldCode` (string, required): Original FlowZap Code

### `flowzap_apply_change` (~49 tokens)

Apply structured patch operations (insert/remove/update nodes or edges) to FlowZap Code.

Input parameters:

- `code` (string, required): Current FlowZap Code
- `operations` (array, required): Array of patch operations

### `flowzap_compliance_check` (~180 tokens)

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.

Input parameters:

- `code` (string, required): FlowZap Code to audit
- `lng` (string): Output language for findings. Default: 'en'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/flowzap-xyz-flowzap/flowzap#diagnostics

## Score history

- 2026-09-21: 66
- 2026-09-20: 66

## Common questions

### 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 hosted endpoint (https://flowzap.xyz/mcp).

### Is the io.github.flowzap-xyz/flowzap MCP server safe to use?

io.github.flowzap-xyz/flowzap scores 66 out of 100 on VerifyMCP. 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_mindmap_validate, flowzap_mindmap_approve, flowzap_mindmap_template, and 8 more. Their descriptions and schemas cost roughly 1,054 tokens of context every time the server is loaded.

### Does the io.github.flowzap-xyz/flowzap MCP server require authentication?

No. We connected to io.github.flowzap-xyz/flowzap without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### 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 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://flowzap.xyz/mcp
- Repository: https://github.com/flowzap-xyz/flowzap-mcp
- Changelog RSS feed: https://verifymcp.io/servers/flowzap-xyz-flowzap/flowzap.xml
- Changelog JSON feed: https://verifymcp.io/servers/flowzap-xyz-flowzap/flowzap.json
- HTML version of this page: https://verifymcp.io/servers/flowzap-xyz-flowzap/flowzap