XGR MCP Gateway

ติดตั้ง

เลือกโปรแกรม AI ที่คุณใช้ แล้วคัดลอกค่าตั้งไปวาง

ผลตรวจผ่าน 5/5 · สิ่งที่คุณถามผ่านเซิร์ฟเวอร์ของผู้ทำ (mcp.xgr.network) · ✓ ตรวจคำสั่งแล้ว 13 พ.ย. 2569

claude mcp add --transport http --scope user xdala-workflow-builder https://mcp.xgr.network/mcp

{
  "mcpServers": {
    "xdala-workflow-builder": {
      "url": "https://mcp.xgr.network/mcp"
    }
  }
}

{
  "servers": {
    "xdala-workflow-builder": {
      "type": "http",
      "url": "https://mcp.xgr.network/mcp"
    }
  }
}

ใช้กับโปรแกรมไหนได้

ดูจากแบบการต่อของ server ตัวนี้ และเอกสารของผู้ทำโปรแกรมแต่ละตัว ตรวจเมื่อ 10 พ.ย. 2569

ต่อผ่านคลาวด์ได้ใน

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

ดูโปรแกรมทั้งหมดพร้อมข้อดีข้อเสีย →

ทำอะไรได้บ้าง

ชื่อและคำอธิบายเครื่องมือตามที่ server ตอบมาเมื่อ 12 พ.ย. 2569 ผู้ทำเป็นคนเขียน ไม่ใช่เรา แสดงเป็นข้อความล้วน

• 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 canonical project metadata and links; use ge

• 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 transaction questions.

• 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 are read-only and cursor-paginated for

• 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; it does not imply common ownership or id

• 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 later mixed balances to the seed value.

• 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 models rather than proof that a specifi

• 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 when available.

• 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 data.

• 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 receipt.

• 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 recently”. For “last 2 weeks”, pass window

• 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 value statistics for UI pickers.

• 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 not use this for a simple transaction tim

• 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 user permissions before local decryption. N

• 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 create session-start handoffs.

• 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.

ผลตรวจเบื้องต้นi

เราตรวจจากข้อมูลที่ใครก็เปิดดูได้ ยังไม่ได้อ่านโค้ด ข้อที่ไม่เกี่ยวกับตัวนี้ไม่นับในตัวหาร · ตรวจเมื่อ 13 พ.ย. 2569

• ✓ ผ่าน

  ตัวตนผู้ทำตรงกับ repo

  ชื่อใน registry ยืนยันด้วยบัญชี GitHub xgr-network ซึ่งเป็นเจ้าของ repo

• ✓ ผ่าน

  ยังมีคนดูแล

  มีการแก้โค้ดล่าสุด 15 วันที่ผ่านมา

• ✓ ผ่าน

  มีสัญญาอนุญาต (license)

  ใช้ Apache-2.0

• ✓ ผ่าน

  endpoint ตอบ

  ตอบกลับใน 499 ms (HTTP 200)

• – ไม่เกี่ยว

  ล็อกอินแบบ OAuth

  ไม่ต้องล็อกอิน

• ✓ ผ่าน

  คำอธิบายเครื่องมือไม่มีคำสั่งแอบแฝง

  อ่านคำอธิบายเครื่องมือ 60 ตัวแล้ว ไม่พบคำสั่งแอบแฝงถึง AI

รีวิวจากผู้ใช้

ยังไม่มีรีวิว

เข้าสู่ระบบด้วย Google เพื่อเขียนรีวิว

เทียบกับตัวอื่นในหมวด อื่น ๆi

• ดาวมากกว่า 0% ของอีก 19667 ตัวในหมวดนี้
• ส่งรุ่นใหม่เข้า registry ล่าสุดกว่า 72% ของอีก 19667 ตัวในหมวดนี้
• ผลตรวจเบื้องต้นดีกว่าหรือเท่ากับ 100% ของอีก 19667 ตัวในหมวดนี้

เทียบกับทุก server ที่ยังใช้งานในหมวดนี้ทั้งทะเบียน ดาวนับเฉพาะเมื่อผู้ลงทะเบียนเป็นเจ้าของ repo

ตัวอื่นในหมวดเดียวกัน

server หมวดเดียวกันจากผู้ทำคนอื่น เรียงตามดาว

อ่านการ์ด:↓ ดาวน์โหลดต่อสัปดาห์i★ ดาว GitHubiสามเสา: รีวิว · ผลตรวจ · การใช้งานiอัปเดต = วันที่ส่งรุ่นล่าสุดเข้า registryi

World Monitor

ข่าวกรองโลกแบบเรียลไทม์: ความขัดแย้ง ตลาด พลังงาน การค้า การขนส่ง และไซเบอร์

โดย koala73·ใช้กันมาก·★ 90.6K·อัปเดต วันนี้

รันบนคลาวด์✓ เจ้าของบริการ · worldmonitor.app

วิธีต่อ

Claude Flow

AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.

โดย ruvnet·ใช้กันมาก·↓ 13.5K/สัปดาห์·★ 81.6K·อัปเดต 14 เดือนที่ผ่านมา

รันบนเครื่อง

ติดตั้ง

Windmill

Run Windmill scripts and flows and manage jobs, schedules, resources and variables.

โดย windmill-labs·ใช้กันมาก·★ 18.6K·อัปเดต เมื่อวาน

รันบนคลาวด์

วิธีต่อ

README จากผู้ทำ

https://mcp.xgr.network/mcp

https://mcp.testnet.xgr.network/mcp

{

npm install