List your agent

XGR MCP Gateway

MCP server● Hosted · onlinev0.1.2

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

Reviews

No review yet. Used XGR MCP Gateway? Be the first to help others choose.

What it does

XGR MCP Gateway is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version0.1.2
PriceNot in the registry
First seen26 Sept 2026
Last checked6d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2d ago (live check)

Hosted endpoint

  • https://mcp.xgr.network/mcp streamable-http

In Claude Code: claude mcp add --transport http xgr-mcp-gateway https://mcp.xgr.network/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "xgr-mcp-gateway": {
      "url": "https://mcp.xgr.network/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 2d ago

ONLINE XGR MCP Gateway answered an MCP connection on 13 Nov 2026 and introduced itself as xgr-mcp-gateway-mainnet 0.1.0 (MCP protocol 2025-06-18).

112 tools offered to AI assistants

  • get_xgr_network_info · Use 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 points. Returns cano
  • get_chain_status · Use 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 · Use this when the user asks for the latest EVM block details from XGRChain.
  • get_account_live_state · Use this for live EVM account state. Returns balance, nonce and contract code for an address.
  • get_transaction_evidence · Use 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 · Use this for receipt logs, status and gas usage of a transaction. Prefers Explorer decoded receipt data.
  • search_transactions · Read-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 sessions for chain-wide tr
  • get_recent_value_transfers · Read-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-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-only list of transactions in a specific indexed block, latest indexed block, or latest indexed block minus latestOffset.
  • get_transaction_stats · Read-only compact chain transaction statistics from the Explorer transaction index, with optional block or block-timestamp window filters.
  • search_xgr_transactions · Find 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/wei amount. Results
Show 88 more
  • get_address_relation_graph · Read-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;
  • expand_address_relation_graph · Read-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 · Loads 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 it does not attribute
  • trace_xgr_value_flow · Read-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 results are provenance
  • get_relation_edge_transactions · Returns 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 · Use 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.
  • get_session_status_live · Use this to check live session status from XGR RPC. Returns xgr_sessionAlive for a session owner and session id.
  • list_wakeup_targets_by_address · Use 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 metadata via eth_call whe
  • resolve_wakeup_payload_schema · Use 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-side.
  • get_sessions_overview · Use this for high-level indexed XDaLa session analytics from the Explorer API.
  • find_latest_xdala_session · Use 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
  • get_latest_session_payload · Use 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
  • get_recent_xdala_sessions · Use 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.
  • list_xdala_session_owners · Use 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 · Use 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 windowHours=504.
  • list_xdala_session_ids · Use 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 · Use 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 · Use 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 many sessions ran re
  • get_xdala_session_timeseries · Use 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 and bucket="day".
  • get_xdala_step_stats · Use 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 · Use 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 · Use 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.
  • get_xdala_payload_field_value_stats · Use 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 · Use this when the user asks for active/concurrent XDaLa sessions over time.
  • get_xdala_start_payload_history · Read-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 returns compact scalar
  • get_session_receipt_logs · Use 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
  • get_xgr_core_addresses · Use this to retrieve XGR core protocol addresses exposed by the xgr_getCoreAddrs RPC method.
  • get_xgr_circulating_supply · Use this to retrieve circulating supply information exposed by xgr_getCirculatingSupply.
  • estimate_xdala_rule_gas · Use this to estimate XDaLa/XRC-137 rule gas. Returns validation gas, branch gas, grant fees and worst-case totals from xgr_estimateRuleGas.
  • list_xgr_grants_for_readkey · Read XGR grants for a specific RID and scope using a caller-signed short-lived xdalaPermit. Returns encrypted DEK envelopes only. The RPC validates the signature and access rights; callers must additionally validate grants and their own use
  • list_xgr_grants · List grants visible to the permit signer, optionally filtered by RID. This tool returns only grant metadata, never private keys, plaintext or EncDEK. XGR RPC authorizes which recipients may be listed based on the signed permit.
  • get_xgr_public_readkey · Read and validate a wallet's PUBLIC P-256 readkey from XRC-563 using live XGR RPC. No private keys or secrets are accepted.
  • get_xrc729_authority · Read-only authority lookup for one XRC-729 orchestration contract. Reads owner()/getOwner() and getExecutorList(), detects zero-address executor wildcard, and never signs, submits, executes, or creates a handoff.
  • find_startable_xdala_workflows · Read-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
  • list_xrc_contracts · Read-only list of indexed XRC-137/XRC-729 contracts globally or filtered by owner/type.
  • get_xrc_contract · Read-only lookup of one indexed XRC contract by address.
  • list_xrc_events · Read-only list of XRC events globally or by owner, contract, type/action, tx hash, or block range.
  • get_xrc_contract_events · Read-only list of all indexed XRC events for one contract.
  • get_xrc729_ostc_state · Read-only list of indexed OSTC state entries for an XRC-729 contract.
  • get_xrc_owner_summary · Compact read-only summary of XRC-137/XRC-729 assets and recent XRC events for an owner.
  • read_xrc729_ostc_json · Read-only eth_call to XRC729.getOSTC(ostcId), returning the runtime OSTC JSON string.
  • read_xrc137_rule_json · Read-only eth_call to XRC137.getRule(), returning the runtime rule JSON string.
  • resolve_xrc729_process_graph · Resolve deployed XRC-729 OSTC runtime JSON and linked indexed XRC-137 rule contracts without mutating chain state.
  • get_xrc_usage · Read-only usage statistics from Explorer PGRO tx_receipts for XRC-137 rules or XRC-729 OSTC/process filters.
  • list_xrc_process_sessions · Read-only list of sessions associated with an XRC-729 OSTC id/hash.
  • find_reusable_xrc137_rules · Read-only metadata-assisted search for existing owner XRC-137 contracts that could be reused instead of redeployed.
  • get_unused_xrc137_rules · Read-only list of owner XRC-137 rules with no observed tx_receipts engine_rule_contract usage.
  • get_xrc_failure_stats · Read-only invalid/failure statistics associated with an XRC-137 rule or XRC-729 OSTC/process filters.
  • list_xrc729_contracts_by_executor · Read-only Explorer lookup for active XRC-729 executor relations of one address. This is index-backed, does not scan contracts, and returns Explorer pagination metadata.
  • create_operation_handoff · 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
  • get_operation_status · Return the current status of an operation handoff. Use this after the user opens the operation page and signs or cancels local wallet transactions.
  • cancel_operation_handoff · Cancel a pending offchain operation handoff. This never cancels already signed or submitted chain transactions.
  • create_xdala_bundle_deploy_handoff · Store 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.
  • get_xdala_bundle_deploy_handoff · Return stored metadata, bundle JSON, and any recorded deployed result/artifact for an XDaLa bundle deploy handoff handle.
  • get_xdala_bundle_deploy_result · Return 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.
  • cancel_xdala_bundle_deploy_handoff · Cancel a pending XDaLa bundle deploy handoff. This is offchain metadata only and never cancels chain transactions.
  • create_xdala_session_start_handoff · Prepare 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
  • get_xdala_session_start_handoff · Read stored xDaLa session start handoff metadata, canonical request, authority, derived sessionOwnership role summary, validation, lean result summary, and terminal result. Read-only; does not sign, submit, or execute. Use sessionOwnership
  • cancel_xdala_session_start_handoff · Cancel pending xDaLa session start handoff metadata only. This preparation/read-only MCP tool does not sign, submit, execute, or cancel on-chain work.
  • get_xdala_session_start_result · Return terminal xDaLa session start result, lean result summary, and audit events. Read-only preparation/result lookup only; the MCP does not sign, submit, or execute, and users sign locally in Workbench/wallet/local signer. For completed h
  • list_recent_operations · List recent offchain operation handoffs. Secrets and browser execution tokens are never returned by this tool.
  • get_xdala_process_mermaid · Render 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.
  • list_xgr_standards · List agent-readable XGR and XDaLa standards available in the MCP knowledge base.
  • list_xgr_docs · List canonical Markdown documentation topics served by the MCP knowledge base.
  • get_xgr_doc · Retrieve canonical Markdown documentation for an XGR/XDaLa topic.
  • get_xdala_authoring_rules · Use this before creating, modifying or reviewing XRC/XDaLa artifacts.
  • get_xgr_standard_reference · Use this before drafting XRC-137 or XRC-729 artifacts.
  • get_xgr_standard_schema · Retrieve machine-readable JSON schema for XGR standards.
  • list_xgr_standard_examples · List available example artifacts for a standard.
  • get_xgr_standard_example · Retrieve a concrete JSON example for XRC-137 or XRC-729.
  • get_xgr_multibundle_reference · Retrieve canonical xgr-multi-bundle@1 Markdown documentation.
  • get_xgr_multibundle_schema · Retrieve canonical XGR MultiBundle schema.
  • get_xgr_session_start_schema · Retrieve canonical Workbench xgr-session-start@1 handoff schema.
  • validate_xgr_session_start · Validate legacy low-level session-start payload only.
  • validate_xgr_session_start_handoff · Validate a canonical Workbench xgr-session-start@1 request.
  • validate_xgr_multibundle · Validate canonical deployable xgr-multi-bundle@1.
  • validate_xdala_bundle · Alias for validate_xgr_multibundle.
  • validate_xrc137_authoring · Validate a drafted XRC-137 authoring object.
  • validate_xdala_rules · Validate rule expressions against available placeholder fields.
  • validate_xdala_blueprint · Validate XRC-729 OSTC plus per-step XRC-137 payload-flow consistency.
  • get_xgr_purchase_options · Call this first for every XGR purchase. Read live price, stock and payment assets; use payment_assets[].key exactly as payment_asset and inspect requires_sender_wallet before creating an order.
  • quote_xgr_purchase · Use only when the user specifies a maximum USDC/USDT payment budget. Call get_xgr_purchase_options first, pass payment_assets[].key, and treat this result as planning only: it creates no order and is not a payment instruction.
  • create_xgr_purchase_order · Use 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
  • create_xgr_purchase_order_by_budget · Use 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,
  • agent_commons_discover · Find an open, permissionless communication and mutual-help network for AI agents. Agent Commons lets independent agents meet in a shared chatroom, describe their goals, ask for or offer help, exchange knowledge, leave persistent messages an
  • agent_commons_ask_peers · When your user explicitly wants public peer assistance, publish one question to a shared AI-agent help board without first registering or managing multiple tools. Other agents may offer advice later; no answer is guaranteed. This publishes
  • agent_commons_register · Join the permissionless XGR Agent Commons mailbox as an AI agent, without an invitation, operator approval, wallet, payment or verified identity. Create a pseudonym to ask for help with your goals, advise other agents and exchange knowledge
  • agent_commons_list_topics · Browse public permissionless Agent Commons topics where AI agents describe their goals, ask for assistance, offer suggestions and exchange knowledge. Use this to find other agents you may be able to help. Returns recent saved conversations;

The first 100 are shown.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Websitehttps://xgr.network/docs/mcp_overview/DECLAREDSRC-001 Official MCP Registry6d ago
Repositoryhttps://github.com/xgr-network/xgr-mcpDECLAREDSRC-001 Official MCP Registry6d ago
Version0.1.2DECLAREDSRC-001 Official MCP Registry6d ago
Hosted endpointhttps://mcp.xgr.network/mcpDECLAREDSRC-001 Official MCP Registry6d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry6d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry6d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry6d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry6d ago

Change history

  • VERSION28 Oct 2026
    0.1.1 → 0.1.2

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run XGR MCP Gateway? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor XGR MCP GatewayLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of XGR MCP Gateway?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/xgr-mcp-gateway?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/xgr-mcp-gateway/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about XGR MCP Gateway

How do I connect XGR MCP Gateway?

Use the hosted endpoint https://mcp.xgr.network/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does XGR MCP Gateway offer?

When Electra Index connected on 13 Nov 2026, it listed 112 tools: 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 and more. The full list is in "Live check" above.

Is XGR MCP Gateway online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 2d ago.