get_chain_statusLABSCO SUMMARY
It never holds your keys.
Write intents come back as handoffs you sign locally; the gateway cannot sign for you. The one exception is narrow and disclosed: the optional starter-gas service signs transfers from its own funding wallet, bounded to one confirmed grant per address plus hourly and daily caps. Purchase tools are a separate opt-in, mainnet only and capped at 249.99 EUR per autonomous order. Draft on testnet first — it exists precisely so a bad artifact costs nothing.
What it is
A hosted gateway to the XGR.Network stack. Agents can inspect chain evidence, reason over XDaLa process state, draft XRC artifacts and prepare on-chain actions — with the signing step deliberately left outside the gateway.
What you get
- Read live chain state: status, blocks, account state and transaction evidence, via
get_chain_status get_xgr_network_inforeturns versioned metadata for the network — RPC and Explorer endpoints, MCP connection details, documentation and XRC standard context- Inspect XDaLa sessions: find, list and explain sessions, process steps, payloads, receipts and execution outcomes
- Search Explorer data — account history, value transfers, block history, transaction statistics and session analytics
- Work with XRC standards: explore XRC-137 rules and XRC-729 orchestrations, then draft artifacts and bundles against the built-in schemas and validation
- Prepare owner-signed actions as review-and-sign handoffs for deployments and session starts
- Where enabled,
get_xgr_starter_gas_optionsandrequest_xgr_starter_gasfund an eligible low-balance address with one fixed 1 XGR grant
Requirements
Nothing to install. Add the mainnet endpoint https://mcp.xgr.network/mcp or the testnet endpoint https://mcp.testnet.xgr.network/mcp as a streamable-http server; clients that only offer plain HTTP use the same URL. Version 0.1.0. Self-hosting is possible against your own XGRChain RPC and an Explorer deployment with a read-only Postgres mirror, built with npm install, npm run build and npm run start:http.
Setup effort
Paste a URL — add the endpoint to your client
USE CASES
01
Investigating what actually happened in a process run
Read the XDaLa session, its steps, payloads and receipts, against live chain evidence.
02
Drafting an XRC artifact with the schema enforced
Prepare XRC-137 or XRC-729 artifacts and validate them before anything is deployed.
03
Preparing a deployment you sign yourself
The agent assembles the action and returns a handoff; your wallet performs the signature.
04
Getting gas into a fresh address before a first action
Check eligibility and request the fixed grant, where the service is enabled.
6 tools
Listed in project docs. Your client may show a different list.
get_xgr_network_infoget_xgr_starter_gas_optionsrequest_xgr_starter_gasquote_xgr_purchasecreate_xgr_purchase_orderBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
INSTALLATION
Connect your client
Add the endpoint to your client.
Server setup
ENDPOINT URL
https://mcp.xgr.network/mcp
