XGR MCP Gateway
REMOTE · MCP.XGR.NETWORK · SCANNED SEP 20
Public Streamable HTTP MCP gateway for XGRChain, XDaLa sessions, Explorer data and XGR standards.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 10617 tokens (~111/item across 95 items; 95 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety88
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 2 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_xdala_bundle_deploy_handoff" implies "deploy" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 95 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the XGR MCP Gateway server?
XGR MCP Gateway is a hosted endpoint at https://mcp.xgr.network/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.xgr.network
claude mcp add --transport http xgr-network-xdala-workflow-builder 'https://mcp.xgr.network/mcp'
{
"mcpServers": {
"xgr-network-xdala-workflow-builder": {
"url": "https://mcp.xgr.network/mcp"
}
}
} {
"servers": {
"xgr-network-xdala-workflow-builder": {
"type": "http",
"url": "https://mcp.xgr.network/mcp"
}
}
} [mcp_servers.xgr-network-xdala-workflow-builder] url = "https://mcp.xgr.network/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xgr-network-xdala-workflow-builder": {
"type": "remote",
"url": "https://mcp.xgr.network/mcp",
"enabled": true
}
}
} openclaw mcp add xgr-network-xdala-workflow-builder --url 'https://mcp.xgr.network/mcp' --transport streamable-http
mcp_servers:
xgr-network-xdala-workflow-builder:
url: "https://mcp.xgr.network/mcp" {
"McpServers": {
"xgr-network-xdala-workflow-builder": {
"Transport": "http",
"Url": "https://mcp.xgr.network/mcp"
}
}
} assistant mcp add xgr-network-xdala-workflow-builder -t streamable-http -u 'https://mcp.xgr.network/mcp'
{
"mcpServers": {
"xgr-network-xdala-workflow-builder": {
"type": "http",
"url": "https://mcp.xgr.network/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Aug 26 0
- New tool “search_xgr_transactions” functional
- 16 Aug 26 0
- Tool “create_xgr_purchase_order” rewrote its description, which is the text the model reads security
- Tool “create_xgr_purchase_order_by_budget” rewrote its description, which is the text the model reads security
- Tool “get_xgr_purchase_options” rewrote its description, which is the text the model reads security
- Tool “quote_xgr_purchase” rewrote its description, which is the text the model reads security
- Schema quality: 8922 → 10387 ▼ functional
- Schema quality: good → excellent functional
- New tool “expand_address_relation_graph” functional
- New tool “get_address_relation_graph” functional
- New tool “get_relation_edge_transactions” functional
- New tool “get_xdala_start_payload_history” functional
- New tool “trace_xgr_transaction” functional
- New tool “trace_xgr_value_flow” functional
- “create_xdala_session_start_handoff” reworded the description of “bundleDeployHandle” cosmetic
- “create_xgr_purchase_order” reworded the description of “amount_xgr” cosmetic
- “create_xgr_purchase_order” reworded the description of “country_code” cosmetic
- “create_xgr_purchase_order” reworded the description of “email” cosmetic
- “create_xgr_purchase_order” reworded the description of “name” cosmetic
- “create_xgr_purchase_order” reworded the description of “payment_asset” cosmetic
- “create_xgr_purchase_order” reworded the description of “sender_wallet” cosmetic
- “create_xgr_purchase_order” reworded the description of “terms_accepted” cosmetic
- “create_xgr_purchase_order” reworded the description of “xgr_wallet” cosmetic
- “create_xgr_purchase_order_by_budget” reworded the description of “country_code” cosmetic
- “create_xgr_purchase_order_by_budget” reworded the description of “email” cosmetic
- “create_xgr_purchase_order_by_budget” reworded the description of “max_payment_amount” cosmetic
- “create_xgr_purchase_order_by_budget” reworded the description of “name” cosmetic
- “create_xgr_purchase_order_by_budget” reworded the description of “payment_asset” cosmetic
- “create_xgr_purchase_order_by_budget” reworded the description of “safety_margin_bps” cosmetic
- “create_xgr_purchase_order_by_budget” reworded the description of “sender_wallet” cosmetic
- “create_xgr_purchase_order_by_budget” reworded the description of “terms_accepted” cosmetic
- “create_xgr_purchase_order_by_budget” reworded the description of “xgr_wallet” cosmetic
- “quote_xgr_purchase” reworded the description of “max_payment_amount” cosmetic
- “quote_xgr_purchase” reworded the description of “payment_asset” cosmetic
- “quote_xgr_purchase” reworded the description of “safety_margin_bps” cosmetic
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.xgr.network/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.xgr.network | CN=YE1,O=Let's Encrypt,C=US | 6 Aug 2026 | 4 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 52c5d1386f0e9102bed6e6eb6a646af0c7c |
| SANs: mcp.xgr.network | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.xgr.network. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| network. | present | 40414 | 8 | Verified |
| xgr.network. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.xgr.network/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.xgr.network/mcp | HTTPS enforced | 301 | https://mcp.xgr.network/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cancel_operation_handoff Cancel operation handoff ~65
Cancel a pending offchain operation handoff. This never cancels already signed or submitted chain transactions.
| Name | Type | Req | Description |
|---|---|---|---|
| operationId | string | yes | Identifier of a stored offchain operation handoff. |
| secret | string | yes | Secret token required to read or cancel protected handoff state. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
cancel_xdala_bundle_deploy_handoff Cancel XDaLa bundle deploy handoff ~59
Cancel a pending XDaLa bundle deploy handoff. This is offchain metadata only and never cancels chain transactions.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Opaque handoff handle returned by a previous XDaLa MCP tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
cancel_xdala_session_start_handoff Cancel XDaLa session start handoff ~66
Cancel pending xDaLa session start handoff metadata only. This preparation/read-only MCP tool does not sign, submit, execute, or cancel on-chain work.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Opaque handoff handle returned by a previous XDaLa MCP tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
create_operation_handoff Create operation handoff ~305
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | integer | yes | Numeric EVM chain id for the target network. |
| network | string | yes | Target network name or environment, for example mainnet or devnet. |
| payload | – | – | Structured payload object for an XDaLa step or workflow request. |
| policy | object | – | Policy metadata controlling human review, approval or execution constraints. |
| steps | array | – | Ordered workflow or operation steps included in the handoff. |
| summary | object | – | Structured summary metadata for human review and audit context. |
| ttlSeconds | integer | – | Time-to-live in seconds for temporary offchain handoff data. |
| type | string | yes | Operation or handoff type identifier. |
| validation | – | – | Validation metadata or validation result object for the handoff. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
create_xdala_bundle_deploy_handoff Create XDaLa bundle deploy handoff ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle | object | yes | Canonical XDaLa bundle JSON object to validate, store or hand off. |
| chainId | integer | yes | Numeric EVM chain id for the target network. |
| network | string | yes | Target network name or environment, for example mainnet or devnet. |
| summary | object | – | Structured summary metadata for human review and audit context. |
| ttlSeconds | integer | – | Time-to-live in seconds for temporary offchain handoff data. |
| validation | object | – | Validation metadata or validation result object for the handoff. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
create_xdala_session_start_handoff Create XDaLa session start handoff ~879
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 ses…
| Name | Type | Req | Description |
|---|---|---|---|
| bundleDeployHandle | string | – | Opaque handle returned by a previous XDaLa bundle deploy handoff flow. |
| chainId | integer | – | Numeric EVM chain id for the target network. |
| execution | object | – | Execution metadata for prepared XDaLa workflow requests. |
| executorGrants | object | – | Executor grant metadata for prepared XDaLa session-start requests. |
| expectedSigner | string | – | Expected wallet address that should sign or execute the prepared handoff. |
| expiry | integer | – | Unix timestamp or expiry value for the prepared request. |
| maxTotalGas | integer | – | Maximum total gas budget allowed for the prepared XDaLa session request. |
| network | string | yes | Target network name or environment, for example mainnet or devnet. |
| orchestration | string | – | Address or identifier of the deployed XDaLa orchestration contract. |
| ostcHash | string | – | Hash or identifier of the orchestration step contract artifact. |
| ostcId | string | – | Orchestration step contract id for the XDaLa workflow. |
| payload | object | – | Structured payload object for an XDaLa step or workflow request. |
| request | object | – | Canonical request object used by the target XDaLa workflow operation. |
| security | object | – | Optional security metadata for handoff preparation. |
| sessions | array | – | Array of canonical xgr-session-start@1 session requests. |
| signing | object | – | Signing metadata for Workbench or local wallet handoff preparation. |
| source | string | yes | Source type for deriving the prepared XDaLa request. |
| stepId | string | – | Canonical XDaLa step id used by Workbench/session-start requests. |
| summary | object | – | Structured summary metadata for human review and audit context. |
| ttlSeconds | integer | – | Time-to-live in seconds for temporary offchain handoff data. |
| ui | object | – | Optional user-interface metadata for Workbench import and display. |
| walletAddress | string | – | Wallet address used as intended signer, starter or actor context. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
create_xgr_purchase_order Create XGR purchase order ~260
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_xgr | integer | yes | Exact integer XGR amount requested by the user. |
| country_code | string | yes | Two-letter uppercase country code supplied by the user, for example DE. |
| string | yes | Purchaser email supplied by the user. Do not invent it. | |
| name | string | yes | Purchaser name supplied by the user. Do not invent it. |
| payment_asset | string | yes | Exact payment_assets[].key returned by get_xgr_purchase_options, for example usdc_eth. Do not use the display symbol. |
| sender_wallet | string | – | User-controlled wallet that will send the stablecoin payment on the listed payment chain. Required when the selected payment asset has requires_sender_wallet=true. |
| terms_accepted | boolean | yes | Set to true only after the user explicitly accepts the purchase terms. Never infer or invent acceptance. |
| xgr_wallet | string | yes | User-controlled XGRChain wallet that will receive the purchased XGR. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
create_xgr_purchase_order_by_budget Create XGR purchase order by budget ~323
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | yes | Two-letter uppercase country code supplied by the user, for example DE. |
| string | yes | Purchaser email supplied by the user. Do not invent it. | |
| max_payment_amount | number | yes | Maximum amount of the selected payment asset the user authorizes. This is USDC or USDT, not EUR. |
| name | string | yes | Purchaser name supplied by the user. Do not invent it. |
| payment_asset | string | yes | Exact payment_assets[].key returned by get_xgr_purchase_options, for example usdc_eth. Do not use the display symbol. |
| safety_margin_bps | integer | – | Conservative planning margin in basis points. Omit to use the default 100 bps. |
| sender_wallet | string | – | User-controlled wallet that will send the stablecoin payment on the listed payment chain. Required when the selected payment asset has requires_sender_wallet=true. |
| terms_accepted | boolean | yes | Set to true only after the user explicitly accepts the purchase terms. Never infer or invent acceptance. |
| xgr_wallet | string | yes | User-controlled XGRChain wallet that will receive the purchased XGR. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
estimate_xdala_rule_gas Estimate XDaLa rule gas ~103
Use this to estimate XDaLa/XRC-137 rule gas. Returns validation gas, branch gas, grant fees and worst-case totals from xgr_estimateRuleGas.
| Name | Type | Req | Description |
|---|---|---|---|
| encrypted | boolean | – | Value for the encrypted parameter. |
| invalidSpawns | integer | – | Value for the invalid spawns parameter. |
| json | string | yes | Value for the json parameter. |
| validSpawns | integer | – | Value for the valid spawns parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
expand_address_relation_graph Expand XGR address graph neighbors ~155
Read-only progressive expansion of one address by exactly one graph level. Use this instead of requesting a larger graph when exploring interactively.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | EVM wallet, Safe or contract address in 0x-prefixed hexadecimal format. |
| aggregate | boolean | – | Value for the aggregate parameter. |
| direction | string | – | Value for the direction parameter. |
| fromTimestamp | integer | – | Value for the from timestamp parameter. |
| maxEdges | integer | – | Value for the max edges parameter. |
| maxNodes | integer | – | Value for the max nodes parameter. |
| minValueWei | string | – | Value for the min value wei parameter. |
| toTimestamp | integer | – | Value for the to timestamp parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
find_latest_xdala_session Find latest XDaLa session ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| includePayload | boolean | – | Value for the include payload parameter. |
| owner | string | – | EVM address of the XDaLa session owner or relevant account. |
| windowHours | integer | – | Value for the window hours parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
find_reusable_xrc137_rules Find reusable XRC-137 rules ~156
Read-only metadata-assisted search for existing owner XRC-137 contracts that could be reused instead of redeployed.
| Name | Type | Req | Description |
|---|---|---|---|
| allowEncrypted | boolean | – | Value for the allow encrypted parameter. |
| draftRule | object | – | Value for the draft rule parameter. |
| includeUsage | boolean | – | Value for the include usage parameter. |
| limit | integer | – | Maximum number of records to return. |
| owner | string | yes | EVM address of the XDaLa session owner or relevant account. |
| requiredInputKeys | array | – | Value for the required input keys parameter. |
| requiredOutputKeys | array | – | Value for the required output keys parameter. |
| ruleHash | string | – | Value for the rule hash parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
find_startable_xdala_workflows Find startable XDaLa workflows ~214
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | EVM wallet, Safe or contract address in 0x-prefixed hexadecimal format. |
| includeExecutor | boolean | – | Value for the include executor parameter. |
| includeGraph | boolean | – | Value for the include graph parameter. |
| includeOwner | boolean | – | Value for the include owner parameter. |
| includePayloadSchema | boolean | – | Value for the include payload schema parameter. |
| includeWildcard | boolean | – | Value for the include wildcard parameter. |
| limit | integer | – | Maximum number of records to return. |
| network | string | – | Target network name or environment, for example mainnet or devnet. |
| owner | string | – | EVM address of the XDaLa session owner or relevant account. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_account_live_state Get account live state ~53
Use this for live EVM account state. Returns balance, nonce and contract code for an address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | EVM wallet, Safe or contract address in 0x-prefixed hexadecimal format. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_account_transactions Get account transactions ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | EVM wallet, Safe or contract address in 0x-prefixed hexadecimal format. |
| direction | string | – | Value for the direction parameter. |
| limit | integer | – | Maximum number of records to return. |
| page | integer | – | One-based page number for paginated explorer/API results. |
| valueOnly | boolean | – | Value for the value only parameter. |
| windowHours | integer | – | Value for the window hours parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_address_relation_graph Get XGR address relation graph ~190
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | EVM wallet, Safe or contract address in 0x-prefixed hexadecimal format. |
| aggregate | boolean | – | Value for the aggregate parameter. |
| depth | integer | – | Value for the depth parameter. |
| direction | string | – | Value for the direction parameter. |
| fromTimestamp | integer | – | Value for the from timestamp parameter. |
| maxEdges | integer | – | Value for the max edges parameter. |
| maxNodes | integer | – | Value for the max nodes parameter. |
| minValueWei | string | – | Value for the min value wei parameter. |
| toTimestamp | integer | – | Value for the to timestamp parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_block_transactions Get block transactions ~94
Read-only list of transactions in a specific indexed block, latest indexed block, or latest indexed block minus latestOffset.
| Name | Type | Req | Description |
|---|---|---|---|
| blockNumber | integer | – | Block number or block identifier used for the chain lookup. |
| latestOffset | integer | – | Value for the latest offset parameter. |
| limit | integer | – | Maximum number of records to return. |
| page | integer | – | One-based page number for paginated explorer/API results. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_chain_status Get XGRChain status ~46
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_latest_block Get latest block ~27
Use this when the user asks for the latest EVM block details from XGRChain.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_latest_session_payload Get latest XDaLa session payload ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | – | EVM address of the XDaLa session owner or relevant account. |
| windowHours | integer | – | Value for the window hours parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_operation_status Get operation status ~72
Return the current status of an operation handoff. Use this after the user opens the operation page and signs or cancels local wallet transactions.
| Name | Type | Req | Description |
|---|---|---|---|
| operationId | string | yes | Identifier of a stored offchain operation handoff. |
| secret | string | – | Secret token required to read or cancel protected handoff state. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_recent_value_transfers Get recent value transfers ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Sender address or lower bound used for the query. |
| limit | integer | – | Maximum number of records to return. |
| minValueWei | string | – | Value for the min value wei parameter. |
| page | integer | – | One-based page number for paginated explorer/API results. |
| to | string | – | Recipient address, contract address or upper bound used for the query. |
| windowHours | integer | – | Value for the window hours parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_recent_xdala_sessions Get recent XDaLa sessions ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| includePayload | boolean | – | Value for the include payload parameter. |
| limit | integer | – | Maximum number of records to return. |
| owner | string | – | EVM address of the XDaLa session owner or relevant account. |
| windowHours | integer | – | Value for the window hours parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_relation_edge_transactions Get transactions behind an XGR graph relation ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fromTimestamp | integer | – | Value for the from timestamp parameter. |
| limit | integer | – | Maximum number of records to return. |
| minValueWei | string | – | Value for the min value wei parameter. |
| page | integer | – | One-based page number for paginated explorer/API results. |
| source | string | yes | Source EVM address of the directed graph relation. |
| target | string | yes | Target EVM address of the directed graph relation. |
| toTimestamp | integer | – | Value for the to timestamp parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_session_receipt_logs Get XDaLa session receipt logs ~195
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Value for the filters parameter. |
| includeBlock | boolean | – | Value for the include block parameter. |
| includeRaw | boolean | – | Value for the include raw parameter. |
| includeTx | boolean | – | Value for the include tx parameter. |
| limit | integer | – | Maximum number of records to return. |
| owner | string | yes | EVM address of the XDaLa session owner or relevant account. |
| sessionId | string | yes | XDaLa session identifier used to query runtime or explorer data. |
| stepIds | array | – | Value for the step ids parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_session_status_live Get live XDaLa session status ~75
Use this to check live session status from XGR RPC. Returns xgr_sessionAlive for a session owner and session id.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | EVM address of the XDaLa session owner or relevant account. |
| sessionId | string | yes | XDaLa session identifier used to query runtime or explorer data. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_session_transactions Get XDaLa session transactions ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of records to return. |
| owner | string | yes | EVM address of the XDaLa session owner or relevant account. |
| page | integer | – | One-based page number for paginated explorer/API results. |
| sessionId | string | yes | XDaLa session identifier used to query runtime or explorer data. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_sessions_overview Get XDaLa sessions overview ~41
Use this for high-level indexed XDaLa session analytics from the Explorer API.
| Name | Type | Req | Description |
|---|---|---|---|
| window | string | – | Time window for aggregated analytics or overview data. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_transaction_evidence Get transaction evidence ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| txHash | string | yes | 0x-prefixed transaction hash to inspect or resolve. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_transaction_receipt Get transaction receipt ~50
Use this for receipt logs, status and gas usage of a transaction. Prefers Explorer decoded receipt data.
| Name | Type | Req | Description |
|---|---|---|---|
| txHash | string | yes | 0x-prefixed transaction hash to inspect or resolve. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_transaction_stats Get transaction stats ~73
Read-only compact chain transaction statistics from the Explorer transaction index, with optional block or block-timestamp window filters.
| Name | Type | Req | Description |
|---|---|---|---|
| fromBlock | integer | – | Value for the from block parameter. |
| toBlock | integer | – | Value for the to block parameter. |
| windowHours | integer | – | Value for the window hours parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_unused_xrc137_rules Get unused XRC-137 rules ~66
Read-only list of owner XRC-137 rules with no observed tx_receipts engine_rule_contract usage.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of records to return. |
| owner | string | yes | EVM address of the XDaLa session owner or relevant account. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_xdala_active_sessions_timeseries Get XDaLa active sessions timeseries ~44
Use this when the user asks for active/concurrent XDaLa sessions over time.
| Name | Type | Req | Description |
|---|---|---|---|
| windowHours | integer | – | Value for the window hours parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_xdala_authoring_rules Get XDaLa authoring rules ~27
Use this before creating, modifying or reviewing XRC/XDaLa artifacts.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_xdala_bundle_deploy_handoff Get XDaLa bundle deploy handoff ~60
Return stored metadata, bundle JSON, and any recorded deployed result/artifact for an XDaLa bundle deploy handoff handle.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Opaque handoff handle returned by a previous XDaLa MCP tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_xdala_bundle_deploy_result Get XDaLa bundle deploy result ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Opaque handoff handle returned by a previous XDaLa MCP tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_xdala_payload_field_value_stats Get XDaLa payload field value statistics ~133
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”.
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | yes | Value for the field parameter. |
| limit | integer | – | Maximum number of records to return. |
| outcome | string | – | Value for the outcome parameter. |
| owner | string | – | EVM address of the XDaLa session owner or relevant account. |
| source | string | – | Source type for deriving the prepared XDaLa request. |
| windowHours | integer | – | Value for the window hours parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_xdala_payload_key_stats Get XDaLa payload key statistics ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of records to return. |
| outcome | string | – | Value for the outcome parameter. |
| owner | string | – | EVM address of the XDaLa session owner or relevant account. |
| source | string | – | Source type for deriving the prepared XDaLa request. |
| windowHours | integer | – | Value for the window hours parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_xdala_payload_term_stats Get XDaLa payload term statistics ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of records to return. |
| minTermLength | integer | – | Value for the min term length parameter. |
| mode | string | – | Value for the mode parameter. |
| outcome | string | – | Value for the outcome parameter. |
| owner | string | – | EVM address of the XDaLa session owner or relevant account. |
| source | string | – | Source type for deriving the prepared XDaLa request. |
| windowHours | integer | – | Value for the window hours parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_xdala_process_mermaid Get XDaLa process Mermaid ~237
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle | object | – | Canonical XDaLa bundle JSON object to validate, store or hand off. |
| direction | string | – | Value for the direction parameter. |
| handle | string | – | Opaque handoff handle returned by a previous XDaLa MCP tool. |
| includeAddresses | boolean | – | Value for the include addresses parameter. |
| includePayloadFields | boolean | – | Value for the include payload fields parameter. |
| includeRuleSummary | boolean | – | Value for the include rule summary parameter. |
| includeRules | boolean | – | Value for the include rules parameter. |
| includeWarnings | boolean | – | Value for the include warnings parameter. |
| ostcId | string | – | Orchestration step contract id for the XDaLa workflow. |
| source | string | yes | Source type for deriving the prepared XDaLa request. |
| xrc729Address | string | – | Value for the xrc729 address parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_xdala_session_detail Get XDaLa session detail ~128
Use this when the user asks for details, timeline, steps, payloads, or evidence for a concrete XDaLa session with owner and sessionId.
| Name | Type | Req | Description |
|---|---|---|---|
| includeFinalPayload | boolean | – | Value for the include final payload parameter. |
| includePayloads | boolean | – | Value for the include payloads parameter. |
| limitSteps | integer | – | Value for the limit steps parameter. |
| owner | string | yes | EVM address of the XDaLa session owner or relevant account. |
| sessionId | string | yes | XDaLa session identifier used to query runtime or explorer data. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_xdala_session_start_handoff Get XDaLa session start handoff ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Opaque handoff handle returned by a previous XDaLa MCP tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_xdala_session_start_result Get XDaLa session start result ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Opaque handoff handle returned by a previous XDaLa MCP tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_xdala_session_stats Get XDaLa session statistics ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | – | EVM address of the XDaLa session owner or relevant account. |
| windowHours | integer | – | Value for the window hours parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_xdala_session_timeseries Get XDaLa session timeseries ~119
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".
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | – | Value for the bucket parameter. |
| owner | string | – | EVM address of the XDaLa session owner or relevant account. |
| windowHours | integer | – | Value for the window hours parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_xdala_start_payload_history Get XDaLa start payload history ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of records to return. |
| ostcId | string | yes | Orchestration step contract id for the XDaLa workflow. |
| owner | string | – | EVM address of the XDaLa session owner or relevant account. |
| stepId | string | yes | Canonical XDaLa step id used by Workbench/session-start requests. |
| windowHours | integer | – | Value for the window hours parameter. |
| xrc729Address | string | yes | Value for the xrc729 address parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_xdala_step_stats Get XDaLa step statistics ~121
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”.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | – | Value for the bucket parameter. |
| owner | string | – | EVM address of the XDaLa session owner or relevant account. |
| sessionId | string | – | XDaLa session identifier used to query runtime or explorer data. |
| windowHours | integer | – | Value for the window hours parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_xgr_circulating_supply Get XGR circulating supply ~31
Use this to retrieve circulating supply information exposed by xgr_getCirculatingSupply.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_xgr_core_addresses Get XGR core addresses ~32
Use this to retrieve XGR core protocol addresses exposed by the xgr_getCoreAddrs RPC method.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
get_xgr_doc Get XGR documentation topic ~35
Retrieve canonical Markdown documentation for an XGR/XDaLa topic.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | Value for the topic parameter. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Structured result data returned by the XGR MCP gateway. |
No examples provided.
What is the XGR MCP Gateway server?
XGR MCP Gateway is listed in the public MCP registry as io.github.xgr-network/xdala-workflow-builder. Public Streamable HTTP MCP gateway for XGRChain, XDaLa sessions, Explorer data and XGR standards. This page covers its hosted endpoint (https://mcp.xgr.network/mcp).
Is the XGR MCP Gateway server safe to use?
XGR MCP Gateway scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the XGR MCP Gateway server expose?
XGR MCP Gateway exposes 95 tools: get_xgr_network_info, get_chain_status, get_latest_block, get_account_live_state, get_transaction_evidence, and 90 more. Their descriptions and schemas cost roughly 10,617 tokens of context every time the server is loaded.
Does the XGR MCP Gateway server require authentication?
No. We connected to XGR MCP Gateway without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the XGR MCP Gateway server still maintained?
XGR MCP Gateway is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.