@xgr-network
基本信息
XGR.Network MCP is a connector for XGRChain and the XDaLa on-chain process engine, enabling AI agents to access chain data, inspect process activity, and prepare secure workflow actions for user-controlled wallet signing.
使用下面的配置,将此服务器添加到你的 MCP 客户端。
{
"mcpServers": {
"xgr-mainnet": {
"type": "http",
"url": "https://mcp.xgr.network/mcp"
},
"xgr-testnet": {
"type": "http",
"url": "https://mcp.testnet.xgr.network/mcp"
}
}
}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 canonical project metadata and links; use get_chain_status for live chain state.
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.
Use this when the user asks for the latest EVM block details from XGRChain.
Use this for live EVM account state. Returns balance, nonce and contract code for an address.
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.
Use this for receipt logs, status and gas usage of a transaction. Prefers Explorer decoded receipt data.
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 transaction questions.
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.
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.
Read-only list of transactions in a specific indexed block, latest indexed block, or latest indexed block minus latestOffset.
Read-only compact chain transaction statistics from the Explorer transaction index, with optional block or block-timestamp window filters.
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 are read-only and cursor-paginated for latest/oldest sorting.
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; it does not imply common ownership or identity.
Read-only progressive expansion of one address by exactly one graph level. Use this instead of requesting a larger graph when exploring interactively.
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 later mixed balances to the seed value.
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 models rather than proof that a specific coin moved. maxTransfers and maxHops accept a number or "all"; "all" is still bounded by Explorer server safety caps and reports truncation explicitly.
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.
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.
Use this to check live session status from XGR RPC. Returns xgr_sessionAlive for a session owner and session id.
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 when available.
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.
Use this for high-level indexed XDaLa session analytics from the Explorer API.
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 data.
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 receipt.
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.
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.
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.
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.
Use this when the user asks for details, timeline, steps, payloads, or evidence for a concrete XDaLa session with owner and sessionId.
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 recently”. For “last 2 weeks”, pass windowHours=336.
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".
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”.
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.
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.
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”.
Use this when the user asks for active/concurrent XDaLa sessions over time.
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 value statistics for UI pickers.
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 not use this for a simple transaction timeline; use get_session_transactions instead.
Use this to retrieve XGR core protocol addresses exposed by the xgr_getCoreAddrs RPC method.
Use this to retrieve circulating supply information exposed by xgr_getCirculatingSupply.
Use this to estimate XDaLa/XRC-137 rule gas. Returns validation gas, branch gas, grant fees and worst-case totals from xgr_estimateRuleGas.
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.
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 create session-start handoffs.
Read-only list of indexed XRC-137/XRC-729 contracts globally or filtered by owner/type.
Read-only lookup of one indexed XRC contract by address.
Read-only list of XRC events globally or by owner, contract, type/action, tx hash, or block range.
Read-only list of all indexed XRC events for one contract.
Read-only list of indexed OSTC state entries for an XRC-729 contract.
Compact read-only summary of XRC-137/XRC-729 assets and recent XRC events for an owner.
Read-only eth_call to XRC729.getOSTC(ostcId), returning the runtime OSTC JSON string.
Read-only eth_call to XRC137.getRule(), returning the runtime rule JSON string.
Resolve deployed XRC-729 OSTC runtime JSON and linked indexed XRC-137 rule contracts without mutating chain state.
Read-only usage statistics from Explorer PGRO tx_receipts for XRC-137 rules or XRC-729 OSTC/process filters.
Read-only list of sessions associated with an XRC-729 OSTC id/hash.
Read-only metadata-assisted search for existing owner XRC-137 contracts that could be reused instead of redeployed.
Read-only list of owner XRC-137 rules with no observed tx_receipts engine_rule_contract usage.
Read-only invalid/failure statistics associated with an XRC-137 rule or XRC-729 OSTC/process filters.
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 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, or queue XDaLa sessions. Do not use this tool for xgr_validateDataTransfer, SessionPermit, Manage Sessions imports, xgr-session-start@1, XDaLa session start handoffs, or starting a deployed XRC-729 workflow. For these intents, use create_xdala_session_start_handoff. If create_xdala_session_start_handoff is unavailable, report that the session-start tool is unavailable instead of falling back to create_operation_handoff.
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 a pending offchain operation handoff. This never cancels already signed or submitted chain transactions.
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.
Return stored metadata, bundle JSON, and any recorded deployed result/artifact for an XDaLa bundle deploy handoff handle.
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 a pending XDaLa bundle deploy handoff. This is offchain metadata only and never cancels chain transactions.
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/XRC-137 workflow, starting from a runtime XRC-729 orchestration, starting from a bundle deploy result, or importing a canonical xgr-session-start@1 request into xDaLa Manage Sessions. When explaining required input to users, use canonical xgr-session-start@1 terminology: sessions[].orchestration, sessions[].ostcId, sessions[].stepId, sessions[].payload, sessions[].maxTotalGas. Do not ask users for entryStepId; entryStepId is not the Workbench Session Start field. For deployed XRC-729 workflows, first inspect the runtime, identify ostcId and the likely entry step, resolve that step's XRC-137 rule, derive required payload fields from the XRC-137 payload schema, treat fields with defaults as optional, and present required and optional/default fields before creating a handoff. Do not call this tool with guessed payload values. If required start payload fields are missing, first present the required fields to the user and ask for values or explicit permission to use demo values. Only use demo/dummy/example/default values when the user explicitly asks or accepts them. This tool returns a Workbench xdalaUrl such as https://xdala.devnet.xgr.network/session-start/ss_... . The agent must show the returned xdalaUrl to the user. Do not replace the xdalaUrl with a generic /operations/op_... link. The MCP does not sign, submit, or execute. xDaLa Workbench performs local signing and calls xgr_validateDataTransfer. Do not describe the XRC-729 contract owner as the owner of a not-yet-started session; owner()/getOwner() and getExecutorList() identify start-authority roles only. Use sessions[].starterAddress only as an intended starter when explicitly set, and use terminal result data such as result.results[].owner/sessionId/pid for the actual session owner/starter after Workbench start.
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 to avoid confusing the XRC-729 contract owner with the actual session owner/starter before Workbench completion.
Cancel pending xDaLa session start handoff metadata only. This preparation/read-only MCP tool does not sign, submit, execute, or cancel on-chain work.
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 handoffs, prefer result.results[].owner/sessionId/pid over XRC-729 contract owner facts when identifying the actual session owner/starter.
List recent offchain operation handoffs. Secrets and browser execution tokens are never returned by this tool.
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 agent-readable XGR and XDaLa standards available in the MCP knowledge base.
List canonical Markdown documentation topics served by the MCP knowledge base.
Retrieve canonical Markdown documentation for an XGR/XDaLa topic.
Use this before creating, modifying or reviewing XRC/XDaLa artifacts.
Use this before drafting XRC-137 or XRC-729 artifacts.
Retrieve machine-readable JSON schema for XGR standards.
List available example artifacts for a standard.
Retrieve a concrete JSON example for XRC-137 or XRC-729.
Retrieve canonical xgr-multi-bundle@1 Markdown documentation.
Retrieve canonical XGR MultiBundle schema.
Retrieve canonical Workbench xgr-session-start@1 handoff schema.
Validate legacy low-level session-start payload only.
Validate a canonical Workbench xgr-session-start@1 request.
Validate canonical deployable xgr-multi-bundle@1.
Alias for validate_xgr_multibundle.
Validate a drafted XRC-137 authoring object.
Validate rule expressions against available placeholder fields.
Validate XRC-729 OSTC plus per-step XRC-137 payload-flow consistency.
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.
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.
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. Pay only from the returned payment_instruction.
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, and create one live reservation. Pay only when payment_approved=true and next_action=external_crypto_payment; otherwise do not pay.
Check whether free native XGR starter gas is available for a low-balance EVM address. Use this before deployments, session starts, contract calls or other on-chain actions when the address lacks gas. Returns the fixed 1 XGR grant policy and the tool to call next.
Use this tool when a user or agent needs native XGR to pay transaction fees on the configured XGR network. It sends one fixed 1 XGR grant from a dedicated server-controlled funding wallet to an eligible low-balance EVM address. Use it before deployments, session starts, contract calls or other on-chain actions when the address lacks gas. One confirmed grant per address; client-IP request limits apply; no repayment is required. The service never requests, receives or stores user or third-party private keys and cannot sign on behalf of users.
XGR.Network MCP is a connector for XGRChain and the XDaLa on-chain process engine. It enables AI agents and MCP-compatible clients to access XGRChain data, inspect XDaLa process activity, analyze sessions, read protocol and workflow context, and prepare secure workflow actions for user-controlled wallet signing.
Configure your MCP client to use one of the provided endpoints: mainnet at https://mcp.xgr.network/mcp or testnet at https://mcp.testnet.xgr.network/mcp. Use the testnet endpoint for safe experimentation, workflow drafting, and validation before production use.
No. The MCP gateway is non-custodial: it does not hold private keys, does not sign transactions, and does not take custody of assets. Workflow actions are prepared as handoffs and must be reviewed and signed locally by the user with their own wallet.
XGRChain mainnet and testnet. The mainnet endpoint is used for inspecting real activity; the testnet endpoint is for safe experimentation and validation.
Use the mainnet endpoint https://mcp.xgr.network/mcp or the testnet endpoint https://mcp.testnet.xgr.network/mcp in your MCP-compatible client.
Documentation is available at https://xgr.network/docs/mcp_overview/. The repository is at https://github.com/xgr-network/xgr-mcp.
Hindsight: Agent Memory That Learns
AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents
A curated list of references for MLOps
Health by Dr Brad works out a health plan from your own results: which screening is due at your age, and evidence-based suggestions, each with the reason and the published guideline or study behind it. Your record is one
🚀 The fast, Pythonic way to build MCP servers and clients.
评论