Should my agent depend on the MCP server io.github.xgr-network/xdala-workflow-builder?

Verdict: allow — rich-slow-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

XDaLa Workflow Builder

io.github.xgr-network/xdala-workflow-builder

Remote MCP server for XDaLa workflow preparation on XGR.Network.

— the operator's own registry description reported

Publisher io.github.xgr-network · first seen 2026-08-12 · endpoint https://mcp.xgr.network/mcp

allow

verdict

rich-slow-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-slow-solo — safe to depend on

Cluster rich-slow-solo · distinctiveness 0.775 (unusual). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency428 ms

vs populationslow

protocolcurrent

authopen

Use — can it use it?

tools88

vs populationhigh

capabilities3

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_ee032f2b11b3ffabc3a538c1 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

cancel_operation_handoff cancel_xdala_bundle_deploy_handoff cancel_xdala_session_start_handoff create_operation_handoff create_xdala_bundle_deploy_handoff create_xdala_session_start_handoff create_xgr_purchase_order create_xgr_purchase_order_by_budget estimate_xdala_rule_gas find_latest_xdala_session find_reusable_xrc137_rules find_startable_xdala_workflows get_account_live_state get_account_transactions get_block_transactions get_chain_status get_latest_block get_latest_session_payload get_operation_status get_recent_value_transfers get_recent_xdala_sessions get_session_receipt_logs get_session_status_live get_session_transactions get_sessions_overview get_transaction_evidence get_transaction_receipt get_transaction_stats get_unused_xrc137_rules get_xdala_active_sessions_timeseries get_xdala_authoring_rules get_xdala_bundle_deploy_handoff get_xdala_bundle_deploy_result get_xdala_payload_field_value_stats get_xdala_payload_key_stats get_xdala_payload_term_stats get_xdala_process_mermaid get_xdala_session_detail get_xdala_session_start_handoff get_xdala_session_start_result get_xdala_session_stats get_xdala_session_timeseries get_xdala_step_stats get_xgr_circulating_supply get_xgr_core_addresses get_xgr_doc get_xgr_multibundle_reference get_xgr_multibundle_schema get_xgr_network_info get_xgr_purchase_options get_xgr_session_start_schema get_xgr_standard_example get_xgr_standard_reference get_xgr_standard_schema get_xgr_starter_gas_options get_xrc729_authority get_xrc729_ostc_state get_xrc_contract get_xrc_contract_events get_xrc_failure_stats get_xrc_owner_summary get_xrc_usage list_recent_operations list_wakeup_targets_by_address list_xdala_session_ids list_xdala_session_owners list_xdala_sessions list_xgr_docs list_xgr_standard_examples list_xgr_standards list_xrc729_contracts_by_executor list_xrc_contracts list_xrc_events list_xrc_process_sessions quote_xgr_purchase read_xrc137_rule_json read_xrc729_ostc_json request_xgr_starter_gas resolve_wakeup_payload_schema resolve_xrc729_process_graph search_transactions validate_xdala_blueprint validate_xdala_bundle validate_xdala_rules validate_xgr_multibundle validate_xgr_session_start validate_xgr_session_start_handoff validate_xrc137_authoring

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	88/88	✓
has a description	88/88	✓
description is substantive	87/88	87/88
parameters are typed	87/88	87/88
parameters are described	88/88	✓

88 of 88 tools graded · 88 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

0.1.0

server version xgr-mcp-gateway-mainnet

Capabilities: prompts resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T20:00:21Z	ok_tools	200	428	2025-06-18
2026-08-12T05:35:32Z	ok_tools	200	388	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.xgr-network/xdala-workflow-builder.svg)](https://robinsaige.com/s/io.github.xgr-network/xdala-workflow-builder)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview