io.github.flowzap-xyz/flowzap
REMOTE · FLOWZAP.XYZ · 2 COMPONENTS
Create workflow, sequence, architecture, and mind map diagrams via AI assistants.
Available components
Last scanned (14 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Design and Media
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1130 tokens (~86/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 2 Nov 26 0
- Tool “flowzap_apply_change” rewrote its description, which is the text the model reads security
- Tool “flowzap_create_playground” rewrote its description, which is the text the model reads security
- Server version: 2.1.0 → 2.2.0 functional
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 67. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 47 to 57. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://flowzap.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=flowzap.xyz | CN=YE1,O=Let's Encrypt,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6ea9c310191545d1fbf3157f5652da22c01 |
| SANs: flowzap.xyz, www.flowzap.xyz | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of flowzap.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | DS published | 3599, 18130 | 8, 8 | Verified |
| flowzap.xyz. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://flowzap.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://flowzap.xyz/mcp | HTTPS enforced | 301 | https://flowzap.xyz/mcp |
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 ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Current FlowZap Code |
| operations | array | yes | Array of patch operations |
No output schema declared.
No examples provided.
flowzap_artifact_to_diagram ~58
Convert HTTP logs, OpenAPI specs, or code snippets into a FlowZap diagram.
| Name | Type | Req | Description |
|---|---|---|---|
| artifactType | string | yes | – |
| content | string | yes | Raw artifact content |
| view | string | – | Preferred view mode |
No output schema declared.
No examples provided.
flowzap_compliance_check ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | FlowZap Code to audit |
| lng | string | – | Output language for findings. Default: 'en'. |
No output schema declared.
No examples provided.
flowzap_create_playground ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | FlowZap Code to render |
| lng | string | – | Language of the messages returned by this tool. Default: 'en'. |
| view | string | – | View mode. Default: 'workflow'. |
No output schema declared.
No examples provided.
flowzap_diff ~45
Compare two FlowZap Code versions and return a structured diff.
| 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 ~39
Parse FlowZap Code into a structured JSON graph (lanes, nodes, edges).
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | FlowZap Code to parse |
No output schema declared.
No examples provided.
flowzap_fix ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | FlowZap Code to repair |
| lng | string | – | Language of the messages returned by this tool. Default: 'en'. |
No output schema declared.
No examples provided.
flowzap_get_syntax ~20
Get FlowZap Code syntax documentation and examples.
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 ~52
Validate FlowZap Code syntax. Returns errors and stats.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | FlowZap Code to validate |
| lng | string | – | Language of the messages returned by this tool. Default: 'en'. |
No output schema declared.
No examples provided.
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.
remote · flowzap.xyz
claude mcp add --transport http flowzap-xyz-flowzap 'https://flowzap.xyz/mcp'
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 80 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,130 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.flowzap-xyz/flowzap MCP server?
VerifyMCP ran 12 checks on io.github.flowzap-xyz/flowzap, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.flowzap-xyz/flowzap: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.