Is the Xgr Network Xdala Workflow Builder MCP server down?

mcp-registry/io.github.xgr-network/xdala-workflow-builder · v0.1.0

healthy
Last checked 2026-10-21 21:48 UTC · handshake 548ms

As of 2026-10-21 21:48 UTC, the Xgr Network Xdala Workflow Builder MCP server is up with a Glimind reliability score of 93/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 8 minutes.

uptime (30d checks)
100%
checks observed
4,159
outages (90d)
1
tools
101

Public Streamable HTTP MCP gateway for XGRChain, XDaLa sessions, Explorer data and XGR standards.

Install Xgr Network Xdala Workflow Builder MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http xgr-network-xdala-workflow-builder-mcp-s https://mcp.xgr.network/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "xgr-network-xdala-workflow-builder-mcp-s": {
      "type": "http",
      "url": "https://mcp.xgr.network/mcp"
    }
  }
}

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

Agent-readiness: B (87/100)

B (87/100): 0 error(s), 4 warning(s) across 95 tool(s); ~21,168 tokens of tool definitions.
Scores higher than 63% of 15,488 MCP servers Glimind has audited.
Its tool list costs an agent ~21,168 tokens per session — more than 95% of servers.
87 → 87 since 2026-10-17
no tool-poisoning patterns
Schemas89
Descriptions100
Safety hints100
Token cost35
Client compatibility100
Protocol100
Reliability85
Stability100

What to fix (4)

95 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: create_operation_handoff

Loading this server's tool list costs an agent ~21,168 tokens before any work — more than 95% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

Handshake + tools/list takes ~2,140 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.

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.xgr-network%2Fxdala-workflow-builder/fixes

create_operation_handoff 1 change
{
  "name": "create_operation_handoff",
  "description": "Create an offchain human-in-the-loop operation and return a browser URL. The MCP never signs or submits transactions; the user executes locally with a browser wallet on the operation page. Do not use this tool to start, run, launch, execute, or queue XDaLa sessions. Do not use this tool for xgr_validateDataTransfer, SessionPermit, Manage Sessions imports, xgr-session-start@1, XDaLa session start handoffs, or starting a deployed XRC-729 workflow. For these intents, use create_xdala_session_start_",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "type",
      "network",
      "chainId"
    ],
    "properties": {
      "type": {
        "type": "string",
        "minLength": 1,
        "description": "Operation or handoff type identifier."
      },
      "steps": {
        "type": "array",
        "items": {
          "type": "object",
          "properties": {
            "id": {
              "type": "string",
              "minLength": 1
            },
            "kind": {
              "type": "string",
              "minLength": 1
            },
            "label": {
              "type": "string",
              "minLength": 1
            },
            "txRequest": {
              "type": "object",
              "propertyNames": {
                "type": "string"
              },
              "additionalProperties": {}
            }
          }
        },
        "description": "Ordered workflow or operation steps included in the handoff."
      },
      "policy": {
        "type": "object",
        "description": "Policy metadata controlling human review, approval or execution constraints.",
        "propertyNames": {
          "type": "string"
        },
        "additionalProperties": {}
      },
      "chainId": {
        "type": "integer",
        "maximum": 9007199254740991,
        "description": "Numeric EVM chain id for the target network.",
        "exclusiveMinimum": 0
      },
      "network": {
        "type": "string",
        "minLength": 1,
        "description": "Target network name or environment, for example mainnet or devnet."
      },
      "payload": {
        "description": "Structured payload object for an XDaLa step or workflow request.",
        "type": "string"
      },
      "summary": {
        "type": "object",
        "description": "Structured summary metadata for human review and audit context.",
        "propertyNames": {
          "type": "string"
        },
        "additionalProperties": {}
      },
      "ttlSeconds": {
        "type": "integer",
        "maximum": 9007199254740991,
        "description": "Time-to-live in seconds for temporary offchain handoff data.",
        "exclusiveMinimum": 0
      },
      "validation": {
        "description": "Validation metadata or validation result object for the handoff.",
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": true,
    "idempotentHint": true,
    "destructiveHint": false
  },
  "title": "Create operation handoff"
}

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.xgr-network/xdala-workflow-builder"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.xgr-network/xdala-workflow-builder"}) 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.xgr-network%2Fxdala-workflow-builder.svg)](https://glimind.com/server/mcp-registry%2Fio.github.xgr-network%2Fxdala-workflow-builder?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.xgr-network%2Fxdala-workflow-builder?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.xgr-network%2Fxdala-workflow-builder.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.xgr-network%2Fxdala-workflow-builder.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.xgr-network%2Fxdala-workflow-builder?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:5be0336d8f583c38…, first seen 2026-10-17, included at leaf 6043 of 41,796. Version history · verify what your client received.

Tools (101)

Compare: most reliable blockchain servers · most reliable other servers · most reliable files servers · most reliable finance servers · most reliable data 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 Xgr Network Xdala Workflow Builder MCP server down right now?

As of 2026-10-21 21:48 UTC, the Xgr Network Xdala Workflow Builder MCP server is up with a Glimind reliability score of 93/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 8 minutes.

How many tools does Xgr Network Xdala Workflow Builder MCP server provide?

Xgr Network Xdala Workflow Builder MCP server advertises 101 tools, including cancel_operation_handoff, cancel_xdala_bundle_deploy_handoff, cancel_xdala_session_start_handoff, create_operation_handoff, create_xdala_bundle_deploy_handoff.

How do I install Xgr Network Xdala Workflow Builder MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.xgr.network/mcp

Is the Xgr Network Xdala Workflow Builder MCP server safe to connect to an AI agent?

Glimind scanned all 95 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 Xgr Network Xdala Workflow Builder 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.

Feedback
Help us improve