Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Xahau MCP

MCPB · XAHAU-MCP-2.0.1.MCPB · SCANNED SEP 20

First MCP for the Xahau network — offline Hook WASM VM + static analyzer, read-only ledger tools.

0 this week 58 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security23
  • Malware scan not yet available for this package.Unverified
  • Known CVEs were checked across the 199 of 199 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • 84 of 199 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability83
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 5839 tokens (~91/item across 64 items; 61 tools + 3 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 28% of tool parameters carry a description.Partial
  • Structured output schemas are declared (30% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_hook" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 62 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
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

mcpb · xahau-mcp-2.0.1.mcpb

Download bundle
Changelog

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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 · Analysed mcpb/https://github.com/Hugegreencandle/xahau-mcp/releases/download/v2.0.1/xahau-mcp-2.0.1.mcpb@2.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb

Background: How many MCP packages publish verified provenance →

Dependencies 199 packages
Packages resolved 199
Deprecated 1
Stale 84
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 61 exposed · ~5,760 tokens

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 →

Tool Tokens
reward_status ~130

Balance Adjustment doctor — the full answer to Xahau's most common retail question: is this account opted in to network rewards, how much XAH is accrued (EXACT genesis reward-hook formula — reward.c — with live RR/RD read from genesis hook state), when can it next claim, and is the claim overdue (late claiming forfeits yield — the hook pays the per-claim rate once regardless of wait). Returns an unsigned opt-in or claim ClaimReward when applicable. Read-only; 3 serial RPC reads.

NameTypeReqDescription
addressstringyesr-address
networkstring
NameTypeReqDescription
accrual
addressstring
balanceXah
eligibility
errorstring
fields
networkstring
notesarray
optedInboolean
paramsobject
summarystring
unsignedTx
unsignedTxPurpose
warningsarray

No examples provided.

ripple_time ~66

Convert between Ripple time (seconds since 2000-01-01), Unix time, and ISO 8601. Xahau tx/ledger timestamps use Ripple time. Offline.

NameTypeReqDescription
isostring
ripplenumber
unixnumber

No output schema declared.

No examples provided.

scaffold_hook ~127

Generate a starter Xahau Hook in C for a stated intent (accept_all, firewall, payment_limit, require_dest_tag, state_counter, notary) — structurally valid (hook() entry, _g guards, accept/rollback) with build instructions. A STARTING POINT to compile + then verify with analyze_hook/execute_hook before deploying. Offline.

NameTypeReqDescription
archetypestringyes
blockTxTypestringfor firewall: tx type to reject, e.g. Payment
maxDropsstringfor payment_limit: max native drops to allow

No output schema declared.

No examples provided.

scam_check ~166

Score a sign request (txjson or raw tx_blob hex) for risky patterns BEFORE signing: returns dangerScore 0-100, a SAFE/CAUTION/DANGER tier, a plain-English verdict, and per-rule findings (SetHook, AccountDelete-to-other, regular-key/signer-list changes, very large native payment, no-expiry replay risk, pre-signed blob). Offline + read-only. HONESTY: every finding is a POTENTIAL risk, NOT a confirmed scam — this tool does NOT consult any block list and NEVER verifies on-chain whether an address is malicious; it reads the transaction shape only. DANGER is reserved for near-universally-malicious/irreversible patterns.

NameTypeReqDescription
txBlobHexstring
txjsonobject

No output schema declared.

No examples provided.

simulate_transaction ~195

THE PRE-SIGN FLIGHT SIMULATOR — predict what Xahau will do with an UNSIGNED transaction before you sign it. Every hook the tx would trigger (originator chain first, then strong/weak transactional stakeholders — order canonical from xahaud Transactor.cpp/applyHook.cpp) runs as REAL bytecode against LIVE ledger state in the local VM (measured 100% agreement on 30 real mainnet hook executions — all accept-direction; rollback direction proven separately on real genesis bytecode). Reports per-hook accept/rollback + return strings, simulated state writes, decoded emitted transactions, labeled STATIC engine preflights (sequence/balance/destination/expiry), and a scam score. Never signs, never submits. Slow but thorough (iterative state resolution, ~1.1s per read).

NameTypeReqDescription
networkstring
txobjectyesunsigned transaction JSON (TransactionType, Account, ...)
NameTypeReqDescription
baseTxHashstring
caveatstring
errorstring
historicalboolean
hookRunsarray
ledgerIndexnumber
notesarray
overriddenFieldsarray
scamScore
staticChecksarray
summarystring
verdictstring

No examples provided.

validate_address ~46

Validate a Xahau/XRPL address (classic r-address or X-address) → type, account-id, embedded destination tag, network. Offline.

NameTypeReqDescription
addressstringyes
NameTypeReqDescription
accountIdstring
classicAddressstring
errorstring
networkstring
reasonstring
tag
typestring
validboolean

No examples provided.

vm_fidelity_report ~184

HONEST FIDELITY METRIC: measures how faithfully the local Hook VM reproduces what REALLY happened on Xahau mainnet. Loads a committed corpus (data/hook-corpus.json) of real validated transactions whose metadata carried HookExecutions, runs each hook's real bytecode through the local VM, and compares the VM's accept/rollback DIRECTION to the on-chain HookResult. The agreement % is computed ONLY over COMPARABLE (non-degraded, scoreable) runs; degraded/halted/indeterminate runs are reported separately and EXCLUDED — never counted as a match. Strictly offline; reads no network. If the corpus is empty/tiny it says 'insufficient corpus' rather than print an unsupported number.

NameTypeReqDescription
includeMismatchesbooleaninclude the per-mismatch list (txHash/vmExit/onChainResult)
NameTypeReqDescription
agreementPct
agreementsnumber
comparablenumber
composition
coverageWarning
degradedCountnumber
errorstring
headlinestring
insufficientboolean
mismatchesarray
perHookarray
totalnumber

No examples provided.

what_if ~134

TIME MACHINE — counterfactual replay of a REAL historical transaction: fetch it by hash, apply your field overrides (different Amount, Destination, params, ...), then run the full flight simulator AT THAT HISTORICAL LEDGER (hooks, state and parameters as they were). Answers 'what would have happened if this tx had been X?'. Read-only; nothing is signed or submitted.

NameTypeReqDescription
networkstring
overridesobjectfields to change on the tx before re-simulating (e.g. {"Amount": "99000000"})
txHashstringyesreal validated transaction hash
NameTypeReqDescription
baseTxHashstring
caveatstring
errorstring
historicalboolean
hookRunsarray
ledgerIndexnumber
notesarray
overriddenFieldsarray
scamScore
staticChecksarray
summarystring
verdictstring

No examples provided.

xaddress ~67

Encode a classic address + destination tag into an X-address, or decode an X-address back to classic + tag. Offline.

NameTypeReqDescription
addressstringyesclassic r-address (to encode) or X-address (to decode)
tagnumber
testboolean

No output schema declared.

No examples provided.

xah_amount ~42

Convert between XAH and drops (1 XAH = 1,000,000 drops). Offline.

NameTypeReqDescription
fromstringyes
valueyes

No output schema declared.

No examples provided.

xahau_server_info ~42

Health, version, amendments and ledger range of a Xahau node (mainnet or testnet). Read-only.

NameTypeReqDescription
networkstring

No output schema declared.

No examples provided.

Common questions

What is the Xahau MCP server?

Xahau MCP is listed in the public MCP registry as io.github.Hugegreencandle/xahau-mcp. First MCP for the Xahau network, offline Hook WASM VM + static analyzer, read-only ledger tools. This page covers its MCPB bundle (https://github.com/Hugegreencandle/xahau-mcp/releases/download/v2.0.1/xahau-mcp-2.0.1.mcpb).

Is the Xahau MCP server safe to use?

Xahau MCP scores 58 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 Xahau MCP server expose?

Xahau MCP exposes 61 tools: xahau_server_info, get_account_info, get_account_objects, get_account_hooks, get_hook_definition, and 56 more. Their descriptions and schemas cost roughly 5,760 tokens of context every time the server is loaded.

What licence is the Xahau MCP server under?

Xahau MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.