Agents Index

XGR MCP Gateway

Online

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

Visit publisherConnectJSON

What it can do: 80 tools

  • get_xgr_network_info read-onlyUse this when the user asks what XGR.Network, XGRChain or XDaLa is, or requests official XGR URLs, chain metadata, RPC, Explorer, MCP, testnet faucet, documentation, XRC standards, source repositories or ecosystem entry
  • get_chain_status read-onlyUse 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_block read-onlyUse this when the user asks for the latest EVM block details from XGRChain.
  • get_account_live_state read-onlyUse this for live EVM account state. Returns balance, nonce and contract code for an address.
  • get_transaction_evidence read-onlyUse this when the user asks what happened in a specific transaction. Combines indexed Explorer transaction data, receipt data and live RPC fallback if available.
  • get_transaction_receipt read-onlyUse this for receipt logs, status and gas usage of a transaction. Prefers Explorer decoded receipt data.
  • search_transactions read-onlyRead-only chain-wide Explorer DB transaction search. Use for general transaction, native XGR value, from/to address, hash, input, session id, validity/execution, and block/time-range questions; do not sample XDaLa sessio
  • get_recent_value_transfers read-onlyRead-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.
  • get_account_transactions read-onlyRead-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.
  • get_block_transactions read-onlyRead-only list of transactions in a specific indexed block, latest indexed block, or latest indexed block minus latestOffset.
  • get_transaction_stats read-onlyRead-only compact chain transaction statistics from the Explorer transaction index, with optional block or block-timestamp window filters.
  • search_xgr_transactions read-onlyFind indexed native-XGR transactions using time, value and address filters before choosing a transaction for Relation Graph or Value Flow analysis. Typical use: all native transfers in the last 24 hours above a given XGR
  • get_address_relation_graph read-onlyRead-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
  • expand_address_relation_graph read-onlyRead-only progressive expansion of one address by exactly one graph level. Use this instead of requesting a larger graph when exploring interactively.
  • trace_xgr_transaction read-onlyLoads an indexed transaction, uses its sender as the bounded graph root, returns sender/recipient trace roots plus the graph and an explicit edge to highlight. Useful for following native XGR transaction relations, but i
  • trace_xgr_value_flow read-onlyRead-only native-XGR value-flow analysis starting from one transaction. Use model="possible" for conservative attribution ranges or model="proportional" for haircut attribution. Native XGR has no per-coin identity, so re
  • get_relation_edge_transactions read-onlyReturns the indexed native XGR transactions represented by one directed graph edge, with the same minimum-value and time filters used by the relation graph.
  • get_session_transactions read-onlyUse 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 contrac
  • get_session_status_live read-onlyUse this to check live session status from XGR RPC. Returns xgr_sessionAlive for a session owner and session id.
  • list_wakeup_targets_by_address read-onlyUse this to list WAITING XDaLa runtime steps that the given wallet or Safe address is allowed to wake via RPC. This is read-only and calls xgr_listWakeupTargetsByAddress, then enriches public/plain XRC rule payload metad
  • resolve_wakeup_payload_schema read-onlyUse this to resolve payload fields for one currently WAITING wake-up target. It reads XRC-729.getOSTC(step -> XRC-137) and XRC-137.getRule() via eth_call for plain JSON rules. Encrypted rules are not decrypted server-sid
  • get_sessions_overview read-onlyUse this for high-level indexed XDaLa session analytics from the Explorer API.
  • find_latest_xdala_session read-onlyUse 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
  • get_latest_session_payload read-onlyUse 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 e
  • get_recent_xdala_sessions read-onlyUse 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
  • list_xdala_session_owners read-onlyUse this when the user asks which owners had XDaLa sessions, asks for the owner list, or when aggregate results show uniqueOwners but the concrete owner addresses are needed. For “last 3 weeks”, pass windowHours=504.
  • list_xdala_sessions read-onlyUse this when the user asks to list XDaLa sessions, enumerate recent sessions, or discover owner/sessionId pairs. This returns concrete owner + sessionId pairs and supports keyset pagination. For “last 3 weeks”, pass win
  • list_xdala_session_ids read-onlyUse this when the user asks for session IDs. Always returns session IDs grouped by owner because session IDs are only unique together with owner.
  • get_xdala_session_detail read-onlyUse this when the user asks for details, timeline, steps, payloads, or evidence for a concrete XDaLa session with owner and sessionId.
  • get_xdala_session_stats read-onlyUse this when the user asks for aggregate XDaLa session statistics, for example “statistics for the last 2 weeks”, “success/failure counts”, “average session duration”, “average steps per session”, “top errors”, or “how
  • get_xdala_session_timeseries read-onlyUse this when the user asks for XDaLa sessions over time, for example “sessions per day”, “daily sessions last 2 weeks”, “monthly session trend”, or “success/fail per day”. For “last 2 weeks by day”, pass windowHours=336
  • get_xdala_step_stats read-onlyUse this when the user asks for step-level XDaLa statistics, for example “how many steps were valid”, “invalid steps”, “failed steps”, “step gas totals”, or “step stats for a session”.
  • get_xdala_payload_key_stats read-onlyUse 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.
  • get_xdala_payload_term_stats read-onlyUse 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 t
  • get_xdala_payload_field_value_stats read-onlyUse this when the user asks which values occurred for a specific payload field, for example “which DocumentType values occurred?” or “top values for ReasonCategory”.
  • get_xdala_active_sessions_timeseries read-onlyUse this when the user asks for active/concurrent XDaLa sessions over time.
  • get_xdala_start_payload_history read-onlyRead-only indexed history of payload values used when starting a specific XRC-729 OSTC entry step. Reads Explorer PGRO through the MCP gateway only, selects the first matching entry-step receipt per owner/session, and re
  • get_session_receipt_logs read-onlyUse 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 ra
  • get_xgr_core_addresses read-onlyUse this to retrieve XGR core protocol addresses exposed by the xgr_getCoreAddrs RPC method.
  • get_xgr_circulating_supply read-onlyUse this to retrieve circulating supply information exposed by xgr_getCirculatingSupply.

…and 40 more.

Connect it

Claude Code
claude mcp add --transport http xgr-mcp-gateway https://mcp.xgr.network/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://mcp.xgr.network/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "xgr-mcp-gateway": {
      "url": "https://mcp.xgr.network/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "xgr-mcp-gateway": {
      "type": "http",
      "url": "https://mcp.xgr.network/mcp"
    }
  }
}

Questions

What does XGR MCP Gateway do?

Public Streamable HTTP MCP gateway for XGRChain, XDaLa sessions, Explorer data and XGR standards. It exposes 80 tools to AI assistants.

What tools does XGR MCP Gateway provide?

80 tools, including 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….

How do I connect XGR MCP Gateway to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://mcp.xgr.network/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does XGR MCP Gateway require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is XGR MCP Gateway online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes XGR MCP Gateway?

@xgr-network on GitHub. The official MCP Registry verified that the publisher controls this GitHub account before accepting the listing.

Similar in Cloud & DevOps