xrpl.mcp.amendments_active_count

get_amendment_status returns enabled/in-flight/superseded counts + hashes from the Amendments ledger object, with cross_check_status derived against the responding node's feature-RPC view.

yellow Public-infrastructure dependent OR no independent cross-check path yet. Free-tier only until Batch B walker migration lands (post-soak, ~2026-08-31) and/or an independent verification walker is wired for this series.

Machine-readable status: /claims/xrpl.mcp.amendments_active_count.json or send Accept: application/json on this URL. URI is permanent — safe to cite.

What this claim says

label: get_amendment_status returns enabled/in-flight/superseded counts + hashes from the Amendments ledger object, with cross_check_status derived against the responding node's feature-RPC view.
page: /mcp
claim id (yaml): amendments_active_count
behavior: STEP_CHANGE
Layer 2 rules: R6
Layer 3 source: xrpl_amendments_ledger_object

Risk note

Cross-check is the moat: unrecognized-enabled hashes present in the ledger object but not in the responding node's build produce `cross_check_status='disagree'` in the envelope. Any silent divergence between /amendments on-page counts and this tool's `enabled_count` would surface here + on the /amendments claim `amendments_enabled_count` (line 503) — same fact, two readers.

Evidence — code paths that back this claim

mcp_tools_ledger.py:tool_get_amendment_status
amendments_state.fetch_amendments_state_cached (300s cache; same one /amendments reads)
cross_check_walker.py: cross_check_pair_4 (localhost feature vs mainnet Amendments ledger object on s1)

Verify

CLAIMS.yaml on GitHub walker_health signed snapshot chain methodology · for AI agents

Sovereignty classification derives from the claim's Layer 3 source per /methodology. Last verified 2026-08-05. This surface is documented in docs/PAID_MACHINE_TIER_DESIGN.md § 3.1.