Is the Flowzap Xyz Flowzap MCP server down?

mcp-registry/io.github.flowzap-xyz/flowzap · v2.1.0

Also listed as awesome/flowzap-xyz/flowzap-mcp

healthy
Last checked 2026-10-17 19:44 UTC · handshake 592ms

As of 2026-10-17 19:44 UTC, the Flowzap Xyz Flowzap MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 12 minutes.

uptime (30d checks)
100%
checks observed
3,309
outages (90d)
1
tools
13

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

Install Flowzap Xyz Flowzap MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http flowzap-xyz-flowzap-mcp-server https://flowzap.xyz/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (76/100)

C (76/100): 0 error(s), 4 warning(s) across 13 tool(s); ~1,706 tokens of tool definitions.
Scores higher than 14% of 15,315 MCP servers Glimind has audited.
Its tool list costs an agent ~1,706 tokens per session — more than 40% of servers.
no tool-poisoning patterns
Schemas100
Descriptions85
Safety hints2
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (5)

13 of 13 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.

Tools: flowzap_apply_change, flowzap_artifact_to_diagram, flowzap_compliance_check, flowzap_create_playground, flowzap_diff and 8 more

3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads.

Tools: flowzap_create_playground, flowzap_mindmap_approve, flowzap_mindmap_create_playground

1 parameter(s) across 1 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.

Tools: flowzap_artifact_to_diagram

Handshake + tools/list takes ~1,780 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.

Auto-fix: 8 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.flowzap-xyz%2Fflowzap/fixes

flowzap_compliance_check 1 change
{
  "name": "flowzap_compliance_check",
  "description": "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 Deep",
  "inputSchema": {
    "type": "object",
    "required": [
      "code"
    ],
    "properties": {
      "lng": {
        "enum": [
          "en",
          "fr",
          "zh"
        ],
        "type": "string",
        "description": "Output language for findings. Default: 'en'."
      },
      "code": {
        "type": "string",
        "description": "FlowZap Code to audit"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
flowzap_create_playground 1 change
{
  "name": "flowzap_create_playground",
  "description": "Create a shareable FlowZap playground URL. Set view to 'architecture', 'sequence', or 'mindmap' when appropriate.",
  "inputSchema": {
    "type": "object",
    "required": [
      "code"
    ],
    "properties": {
      "lng": {
        "enum": [
          "en",
          "fr",
          "zh"
        ],
        "type": "string",
        "description": "Language of the messages returned by this tool. Default: 'en'."
      },
      "code": {
        "type": "string",
        "description": "FlowZap Code to render"
      },
      "view": {
        "enum": [
          "workflow",
          "sequence",
          "architecture",
          "mindmap"
        ],
        "type": "string",
        "description": "View mode. Default: 'workflow'."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
flowzap_export_graph 1 change
{
  "name": "flowzap_export_graph",
  "description": "Parse FlowZap Code into a structured JSON graph (lanes, nodes, edges).",
  "inputSchema": {
    "type": "object",
    "required": [
      "code"
    ],
    "properties": {
      "code": {
        "type": "string",
        "description": "FlowZap Code to parse"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.flowzap-xyz/flowzap"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.flowzap-xyz/flowzap"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.flowzap-xyz%2Fflowzap.svg)](https://glimind.com/server/mcp-registry%2Fio.github.flowzap-xyz%2Fflowzap?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.flowzap-xyz%2Fflowzap?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.flowzap-xyz%2Fflowzap.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.flowzap-xyz%2Fflowzap.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.flowzap-xyz%2Fflowzap?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:bbdf71aab1815ac0…, first seen 2026-10-17, included at leaf 14751 of 18,312. Version history · verify what your client received.

Tools (13)

Compare: most reliable data servers · most reliable other servers · most reliable security servers · most reliable productivity servers · most reliable code servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Flowzap Xyz Flowzap MCP server down right now?

As of 2026-10-17 19:44 UTC, the Flowzap Xyz Flowzap MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 12 minutes.

How many tools does Flowzap Xyz Flowzap MCP server provide?

Flowzap Xyz Flowzap MCP server advertises 13 tools, including flowzap_apply_change, flowzap_artifact_to_diagram, flowzap_compliance_check, flowzap_create_playground, flowzap_diff.

How do I install Flowzap Xyz Flowzap MCP server?

Point your MCP client at this streamable-http endpoint: https://flowzap.xyz/mcp

Is the Flowzap Xyz Flowzap MCP server safe to connect to an AI agent?

Glimind scanned all 13 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Flowzap Xyz Flowzap MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.