Home / MCP registry index / io.github.xgr-network/xdala-workflow-builder

XGR MCP Gateway

io.github.xgr-network/xdala-workflow-builder in the official MCP registry. Endpoint https://mcp.xgr.network/mcp. Source: github.com/xgr-network/xgr-mcp.

The registry describes it as: Public Streamable HTTP MCP gateway for XGRChain, XDaLa sessions, Explorer data and XGR standards.

We read its 112 tools on 2026-11-01. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code
claude mcp add --transport http xdala-workflow-builder https://mcp.xgr.network/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "xdala-workflow-builder": {
      "url": "https://mcp.xgr.network/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"xdala-workflow-builder","type":"http","url":"https://mcp.xgr.network/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard
claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

get_xgr_network_info get_chain_status get_latest_block get_account_live_state get_transaction_evidence get_transaction_receipt search_transactions get_recent_value_transfers get_account_transactions get_block_transactions get_transaction_stats search_xgr_transactions get_address_relation_graph expand_address_relation_graph trace_xgr_transaction trace_xgr_value_flow get_relation_edge_transactions get_session_transactions get_session_status_live list_wakeup_targets_by_address resolve_wakeup_payload_schema get_sessions_overview find_latest_xdala_session get_latest_session_payload get_recent_xdala_sessions list_xdala_session_owners list_xdala_sessions list_xdala_session_ids get_xdala_session_detail get_xdala_session_stats get_xdala_session_timeseries get_xdala_step_stats get_xdala_payload_key_stats get_xdala_payload_term_stats get_xdala_payload_field_value_stats get_xdala_active_sessions_timeseries get_xdala_start_payload_history get_session_receipt_logs get_xgr_core_addresses get_xgr_circulating_supply estimate_xdala_rule_gas list_xgr_grants_for_readkey list_xgr_grants get_xgr_public_readkey get_xrc729_authority find_startable_xdala_workflows list_xrc_contracts get_xrc_contract list_xrc_events get_xrc_contract_events get_xrc729_ostc_state get_xrc_owner_summary read_xrc729_ostc_json read_xrc137_rule_json resolve_xrc729_process_graph get_xrc_usage list_xrc_process_sessions find_reusable_xrc137_rules get_unused_xrc137_rules get_xrc_failure_stats and 52 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-01): 96839b6f806f6c63. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-xgr-network-xdala-workflow-builder/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-xgr-network-xdala-workflow-builder)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.