XGR.Network MCP

The gateway is designed for agent-assisted workflow creation: agents can inspect live chain evidence, reason over XDaLa process state, draft XRC artifacts and prepare handoffs that a user reviews and signs locally.

The gateway never requests, receives, stores or controls user or third-party private keys and cannot sign on behalf of users. User write intents are prepared as handoffs and signed locally. An optional starter-gas service may use a dedicated server-controlled funding key solely to send fixed XGR gas grants from the service wallet.

Use mainnet to inspect real XGRChain and XDaLa activity. Use testnet to safely draft, validate and experiment with agent-driven workflows before production use.

{ "mcpServers": { "xgr-mainnet": { "type": "streamable-http", "url": "https://mcp.xgr.network/mcp" }, "xgr-testnet": { "type": "streamable-http", "url": "https://mcp.testnet.xgr.network/mcp" } } }

For clients that still expecthttpinstead ofstreamable-http, use the same endpoint URL and select the HTTP/remote MCP transport offered by your client.

- Read chain state: inspect live XGRChain status, blocks, account state and transaction evidence.
- Discover official XGR resources: useget_xgr_network_infofor canonical XGR.Network, XGRChain, XDaLa, RPC, Explorer, MCP, documentation and ecosystem metadata.
- Inspect XDaLa sessions: find, list and explain sessions, process steps, payloads, receipts and execution outcomes.
- Search Explorer data: query account history, value transfers, block history, transaction statistics and session analytics.
- Work with XRC standards: explore XRC-137 rules, XRC-729 orchestrations, process graphs, reuse patterns and failure analytics.
- Draft process artifacts: prepare XRC-137/XRC-729 artifacts and bundles against built-in schemas and validation rules.
- Prepare owner-signed actions: create review-and-sign handoffs for deployments and session starts without exposing private keys.
- Request starter gas where enabled: fund an eligible low-balance address with one fixed 1 XGR grant before deployment, session start, contract calls or other on-chain actions.

get_xgr_network_inforeturns versioned, machine-readable metadata for XGR.Network and its ecosystem. Agents should use it when users request official project information, network configuration, RPC or Explorer endpoints, MCP connection details, documentation, XRC standard context or source repositories.

get_chain_statusremains the live JSON-RPC status tool and additionally returns compact official entry points for the connected XGRChain mainnet.

XGR.Network MCP is built around deterministic process infrastructure rather than generic chat automation. It gives agents structured access to the XGR stack while keeping user signing, user custody and final approval outside the gateway.

- AI-assisted Web3 workflow design
- XDaLa process preparation and inspection
- compliance-oriented process evidence
- deterministic validation and execution flows
- EVM-compatible process automation
- agent interfaces for XGRChain data and XRC standards

Full reference lives in the central XGR documentation:

The gateway can be operated against your own XGRChain RPC and Explorer instance. Self-hosting requires an Explorer deployment with a read-only Postgres mirror for transaction search and session analytics tools.

npm install npm run typecheck npm run build npm run start:http

- The gateway never requests, receives, stores or controls user or third-party private keys.
- User transactions are prepared as handoffs and signed locally by the user or the user's custody setup.
- The optional starter-gas service is a narrow exception: it signs only transfers from a dedicated server-controlled funding wallet and cannot sign on behalf of users.
- Starter-gas grants are fixed at 1 XGR, limited by recipient balance, one confirmed grant per address, hourly and daily caps, and a bounded retry policy.
- Starter-gas grant state is stored atomically in SQLite withreserved,broadcast,confirmedandfailedstates.
- Production user signing remains under the control of the user's wallet or custody setup.

The optional purchase tools aremainnet-only, disabled by default, and are never registered by testnet. Enable them only withXGR_PURCHASE_TOOLS_ENABLED=true,XGR_PURCHASE_NETWORK=mainnet, a valid HTTPS API URL (or local HTTP), and a maximum at or below249.99EUR.

quote_xgr_purchaseis optional planning only.create_xgr_purchase_ordercreates the real order in one call toPOST /api/orders; the website confirmation modal is not a separate API phase. The backend is authoritative for the final price, crypto amount, custody wallet, payment reference, and reservation. The MCP holds no user or third-party private keys and does not pay; an external wallet agent can execute the returned exact payment instruction.

The249.99 EURmaximum is an MCP policy for autonomous orders. Separately, the XGR_Web backend requires a complete billing address from a newly calculatednet_eur >= 250; it is not a backend order maximum. A backend repricing/address error is returned without retrying the order.

Purchase tools distinguish fixed-XGR orders from conservative USDC/USDT budget orders. The live backend POST determines the binding market price and exactamount_crypto; EUR is only a policy/reference value. A budget order whose exact returned amount exceeds its cap is not paid and its existing reservation expires normally.

Where enabled,get_xgr_starter_gas_optionsexposes the current fixed grant and eligibility policy.request_xgr_starter_gassends one fixed 1 XGR grant from a dedicated service wallet to an eligible low-balance EVM address. Agents should use it before deployments, session starts, contract calls or other on-chain actions when the target address lacks native XGR for gas.

The service does not request an address-ownership proof and does not use proof-of-work. Abuse is bounded through one confirmed grant per address, an hourly cap, a daily cap, recipient-balance eligibility, a low-balance service wallet and a limited number of retries after pre-broadcast failures.

An assistant API to help find and apply for funding opportunities.

Provides MCP access to OculusMind.AI agents who search the web, analyze stocks and products, automate and schedule workflows and utilize other MCP server tools.

Self-improving AI workflows with natural language backtesting. 21 MCP tools for creating workflows, backtesting trading strategies, parameter sweeps, portfolio optimization, prompt optimization, cron scheduling, and webhook triggers. Install: pip install vynn-mcp

AI agents that automate bookkeeping and financial close for SMBs.

Trustless AI task verification and XRPL escrow management — post jobs, verify completions, and release XRP payments automatically via MCP.

Automate Your Trading. Zero Code Required. Build, backtest, and run algorithmic strategies using visual blocks and AI. Connect your exchange and go live in minutes.

Visual coordination protocol for AI agents — 22 MCP tools for glyph-based communication with 50-70% token savings, shared memory, governance, and on-chain attestation.

Anonymous broker where AI agents publish capabilities, negotiate, and seal direct peer-to-peer deals; three of its tools need no API key or account.

Open intent exchange where AI agents get a cryptographic identity, reputation-ranked discovery, and dual-signed outcomes on a publicly auditable ledger — zero-config, no accounts.