Index / MCP servers / XGR MCP Gateway

XGR MCP Gateway MCP server

XGR MCP Gateway is an MCP server with 95 tools an agent can call, among them cancel_operation_handoff, cancel_xdala_bundle_deploy_handoff, cancel_xdala_session_start_handoff. It answers at https://mcp.xgr.network/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 24 October 2026, succeeded.

Status
Answering
Tools
95
Reliability
6 of 6 checks
Response time
66 ms
Transport
streamable HTTP
Last checked
24 October 2026

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

Description as the publisher wrote it.

The 95 tools XGR MCP Gateway offers

ToolWhat it does
cancel_operation_handoffCancel a pending offchain operation handoff. This never cancels already signed or submitted chain transactions.
Inputs: operationId, secret
cancel_xdala_bundle_deploy_handoffCancel a pending XDaLa bundle deploy handoff. This is offchain metadata only and never cancels chain transactions.
Inputs: handle
cancel_xdala_session_start_handoffCancel pending xDaLa session start handoff metadata only. This preparation/read-only MCP tool does not sign, submit, execute, or cancel on-chain work.
Inputs: handle
create_operation_handoffCreate 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
Inputs: type, network, chainId, summary, payload, validation
create_xdala_bundle_deploy_handoffStore a validated xgr-multi-bundle@1 bundle offchain under an unguessable bearer handle and return an XDaLa Workbench import URL. The MCP does not sign, submit, or execute transactions.
Inputs: network, chainId, bundle, summary, validation, ttlSeconds
create_xdala_session_start_handoffPrepare and store a read-only xgr-session-start@1 handoff for xDaLa Workbench. Use this tool whenever the user wants to start, run, launch, execute, queue, or prepare an XDaLa session. Use this tool for starting an existing deployed XRC-729
Inputs: source, network, chainId, orchestration, ostcId, ostcHash
create_xgr_purchase_orderUse when the user specifies an exact integer amount_xgr. Call get_xgr_purchase_options first, use payment_assets[].key, collect user-supplied identity and wallet fields, require explicit terms acceptance, and create one live reservation. Pa
Inputs: payment_asset, name, email, country_code, xgr_wallet, sender_wallet
create_xgr_purchase_order_by_budgetUse when the user specifies a maximum USDC/USDT payment amount rather than an XGR quantity. Call get_xgr_purchase_options first, use payment_assets[].key, collect user-supplied identity and wallet fields, require explicit terms acceptance,
Inputs: payment_asset, name, email, country_code, xgr_wallet, sender_wallet
estimate_xdala_rule_gasUse this to estimate XDaLa/XRC-137 rule gas. Returns validation gas, branch gas, grant fees and worst-case totals from xgr_estimateRuleGas.
Inputs: json, encrypted, validSpawns, invalidSpawns
expand_address_relation_graphRead-only progressive expansion of one address by exactly one graph level. Use this instead of requesting a larger graph when exploring interactively.
Inputs: address, direction, minValueWei, fromTimestamp, toTimestamp, aggregate
find_latest_xdala_sessionUse this when the user asks for the latest XDaLa session but does not provide owner and sessionId. This read-only tool resolves the newest indexed XDaLa session from the Explorer database and can optionally include final receipt payload dat
Inputs: owner, windowHours, includePayload
find_reusable_xrc137_rulesRead-only metadata-assisted search for existing owner XRC-137 contracts that could be reused instead of redeployed.
Inputs: owner, draftRule, ruleHash, requiredInputKeys, requiredOutputKeys, allowEncrypted
find_startable_xdala_workflowsRead-only discovery of deployed XRC-729 workflows that a given address can start as owner, executor, or wildcard executor. Use this whenever the user provides an address and asks which sessions/workflows they can start. This tool does not c
Inputs: address, network, owner, includeOwner, includeExecutor, includeWildcard
get_account_live_stateUse this for live EVM account state. Returns balance, nonce and contract code for an address.
Inputs: address
get_account_transactionsRead-only chain-wide Explorer DB transaction lookup for one account as sender, recipient, or both. Use this instead of XDaLa session tools for account-wide transaction history.
Inputs: address, direction, valueOnly, windowHours, page, limit
get_address_relation_graphRead-only bounded graph of indexed native XGR transfers around an address. Returns aggregated on-chain relations, verified Explorer labels, depth and truncation metadata. A relation proves only that transactions occurred between addresses;
Inputs: address, direction, depth, minValueWei, fromTimestamp, toTimestamp
get_block_transactionsRead-only list of transactions in a specific indexed block, latest indexed block, or latest indexed block minus latestOffset.
Inputs: blockNumber, latestOffset, page, limit
get_chain_statusUse this for live XGRChain status. Returns chain id, latest block number and gas price from JSON-RPC, plus official XGR.Network entry points for the connected mainnet.
get_latest_blockUse this when the user asks for the latest EVM block details from XGRChain.
get_latest_session_payloadUse this when the user asks for the payload of the latest XDaLa session. This read-only tool resolves the latest indexed session without requiring owner plus sessionId, then returns payload, apiSaves, contractSaves and extras from the final
Inputs: owner, windowHours
get_operation_statusReturn the current status of an operation handoff. Use this after the user opens the operation page and signs or cancels local wallet transactions.
Inputs: operationId, secret
get_recent_value_transfersRead-only shortcut for recent native XGR value transfers from the Explorer transaction index. Native value transfer means transactions.value > minValueWei and does not include gas fees.
Inputs: windowHours, minValueWei, from, to, page, limit
get_recent_xdala_sessionsUse this to list recent indexed XDaLa sessions from the read-only Explorer database, especially when the user does not know owner and sessionId. Supports optional owner filtering, time windows, result limits and payload enrichment.
Inputs: owner, windowHours, limit, includePayload
get_relation_edge_transactionsReturns the indexed native XGR transactions represented by one directed graph edge, with the same minimum-value and time filters used by the relation graph.
Inputs: source, target, minValueWei, fromTimestamp, toTimestamp, page
get_session_receipt_logsUse this to inspect what an XDaLa session actually did. Returns decoded engine receipt data such as input payload, API saves, contract saves, execution contract, rule contract, valid flag, inner gas usage and optional raw receipt logs. Do n
Inputs: sessionId, owner, stepIds, includeTx, includeBlock, includeRaw
get_session_status_liveUse this to check live session status from XGR RPC. Returns xgr_sessionAlive for a session owner and session id.
Inputs: sessionId, owner
get_session_transactionsUse this to list the blockchain transactions belonging to an XDaLa session. This returns the timeline of transaction hashes, blocks, fees and iteration steps. It does not return full engine payloads, API saves or contract read results.
Inputs: sessionId, owner, page, limit
get_sessions_overviewUse this for high-level indexed XDaLa session analytics from the Explorer API.
Inputs: window
get_transaction_evidenceUse this when the user asks what happened in a specific transaction. Combines indexed Explorer transaction data, receipt data and live RPC fallback if available.
Inputs: txHash
get_transaction_receiptUse this for receipt logs, status and gas usage of a transaction. Prefers Explorer decoded receipt data.
Inputs: txHash
get_transaction_statsRead-only compact chain transaction statistics from the Explorer transaction index, with optional block or block-timestamp window filters.
Inputs: windowHours, fromBlock, toBlock
get_unused_xrc137_rulesRead-only list of owner XRC-137 rules with no observed tx_receipts engine_rule_contract usage.
Inputs: owner, limit
get_xdala_active_sessions_timeseriesUse this when the user asks for active/concurrent XDaLa sessions over time.
Inputs: windowHours
get_xdala_authoring_rulesUse this before creating, modifying or reviewing XRC/XDaLa artifacts.
get_xdala_bundle_deploy_handoffReturn stored metadata, bundle JSON, and any recorded deployed result/artifact for an XDaLa bundle deploy handoff handle.
Inputs: handle
get_xdala_bundle_deploy_resultReturn the stored XDaLa bundle deploy result, canonical deployed artifact, and audit events for a handoff handle. This is read-only and never signs, submits, or executes transactions.
Inputs: handle
get_xdala_payload_field_value_statsUse this when the user asks which values occurred for a specific payload field, for example “which DocumentType values occurred?” or “top values for ReasonCategory”.
Inputs: owner, windowHours, outcome, source, field, limit
get_xdala_payload_key_statsUse this when the user asks which payload fields/keys occurred, how often payload fields appeared, or which payload fields were empty/non-empty. For “last 14 days”, pass windowHours=336.
Inputs: owner, windowHours, outcome, source, limit
get_xdala_payload_term_statsUse this when the user asks for payload terms, payload words, payload Begriff statistics, or a statistic over all payload terms in a time range. For “last 14 days”, pass windowHours=336. Do not sample sessions for this task.
Inputs: owner, windowHours, outcome, source, mode, minTermLength
get_xdala_process_mermaidRender an XDaLa XRC-729 process graph from runtime, bundle, or bundle handoff data as Mermaid flowchart text. Read-only; does not sign, submit, or execute transactions.
Inputs: source, xrc729Address, ostcId, includeRules, bundle, handle
55 more tools

get_xdala_session_detail, get_xdala_session_start_handoff, get_xdala_session_start_result, get_xdala_session_stats, get_xdala_session_timeseries, get_xdala_start_payload_history, get_xdala_step_stats, get_xgr_circulating_supply, get_xgr_core_addresses, get_xgr_doc, get_xgr_multibundle_reference, get_xgr_multibundle_schema, get_xgr_network_info, get_xgr_purchase_options, get_xgr_session_start_schema, get_xgr_standard_example, get_xgr_standard_reference, get_xgr_standard_schema, get_xgr_starter_gas_options, get_xrc729_authority, get_xrc729_ostc_state, get_xrc_contract, get_xrc_contract_events, get_xrc_failure_stats, get_xrc_owner_summary, get_xrc_usage, list_recent_operations, list_wakeup_targets_by_address, list_xdala_session_ids, list_xdala_session_owners, list_xdala_sessions, list_xgr_docs, list_xgr_standard_examples, list_xgr_standards, list_xrc729_contracts_by_executor, list_xrc_contracts, list_xrc_events, list_xrc_process_sessions, quote_xgr_purchase, read_xrc137_rule_json, read_xrc729_ostc_json, request_xgr_starter_gas, resolve_wakeup_payload_schema, resolve_xrc729_process_graph, search_transactions, search_xgr_transactions, trace_xgr_transaction, trace_xgr_value_flow, validate_xdala_blueprint, validate_xdala_bundle, validate_xdala_rules, validate_xgr_multibundle, validate_xgr_session_start, validate_xgr_session_start_handoff, validate_xrc137_authoring

Add XGR MCP Gateway to your AI client

Every block below points at https://mcp.xgr.network/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http xgr-mcp-gateway https://mcp.xgr.network/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "xgr-mcp-gateway": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.xgr.network/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "xgr-mcp-gateway": {
      "url": "https://mcp.xgr.network/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "xgr-mcp-gateway": {
      "type": "http",
      "url": "https://mcp.xgr.network/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "xgr-mcp-gateway": {
      "url": "https://mcp.xgr.network/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "xgr-mcp-gateway": {
      "serverUrl": "https://mcp.xgr.network/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "xgr-mcp-gateway": {
      "url": "https://mcp.xgr.network/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: XGR MCP Gateway
version: 0.0.1
schema: v1
mcpServers:
  - name: XGR MCP Gateway
    type: streamable-http
    url: https://mcp.xgr.network/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "xgr-mcp-gateway": {
      "httpUrl": "https://mcp.xgr.network/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "xgr-mcp-gateway": {
      "type": "http",
      "url": "https://mcp.xgr.network/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "xgr-mcp-gateway": {
      "url": "https://mcp.xgr.network/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fmcp.xgr.network%2Fmcp&type=streamable_http&id=xgr-mcp-gateway&name=XGR%20MCP%20Gateway

Is XGR MCP Gateway up right now?

It answered our last check on 24 October 2026 in 66 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to XGR MCP Gateway

Questions about XGR MCP Gateway

How many tools does XGR MCP Gateway have?

95, as returned by the server's own tools/list on 22 September 2026: cancel_operation_handoff, cancel_xdala_bundle_deploy_handoff, cancel_xdala_session_start_handoff, create_operation_handoff, create_xdala_bundle_deploy_handoff, create_xdala_session_start_handoff, create_xgr_purchase_order, create_xgr_purchase_order_by_budget, and 87 more.

Is XGR MCP Gateway down?

It answered our last check on 24 October 2026 in 66 ms. Over 6 checks since 11 September 2026 it answered 6.

How do I add XGR MCP Gateway to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.xgr.network/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does XGR MCP Gateway need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.xgr-network. Endpoint host: mcp.xgr.network. ARD identifier: urn:air:io.github.xgr-network:mcp:xdala-workflow-builder. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.