Has this XRPL issuer rugged before?

Issuers that rug once often relaunch. This tool checks an issuer against a blocklist built from rugs caught in production, plus the full history of AMM launches we've observed from that address.

MCP tool: check_issuer_reputation Price: $0.002 / call

Parameters

Param	Description
`issuer`	XRPL issuer address (r...)

Example

Call (MCP tools/call arguments):

{
  "issuer": "rDbS53G2nP3ksrNSea3rjFSZa3grkzVtf6"
}

Result:

{
  "verdict": "blocklisted",
  "blocklisted": true,
  "block_reason": "manual:UW_position_3_rug_relaunch",
  "total_detections": 2
}

FAQ

Why does issuer history matter on XRPL?

Creating a new token is nearly free, so serial ruggers reuse playbooks — and sometimes addresses. An issuer-level blocklist catches relaunches that per-token checks miss.

Where does this blocklist come from?

From a production XRPL sniper pipeline: issuers whose tokens rugged positions we actually held are blocklisted with the reason recorded.

Related tools

check_xrpl_tokenLive safety verdict for any XRP Ledger token: clawback and global-freeze hard rejects, issuer blackhole status, LP-burn fraction, check_addressOne call, any chain: EVM address risk (sanctions, mixer, phishing, drainer, money-laundering) aggregated from GoPlus, plus native get_wallet_activityTurn raw XRPL account_tx into readable activity: sent/received amounts with token names, trustlines, DEX/AMM ops — with rug-blockl check_transactionSimulate an unsigned XRPL transaction against the live ledger: its exact balance changes, whether it would succeed, and a scan for check_endpointOne call before an agent connects to a third-party MCP server or HTTP tool: TLS identity, domain age, and a tool-poisoning scan of

Browse the full tool suite →

Connect via MCP at https://cerberusindex.com/mcp — see the quickstart. Payment is automatic for x402-aware clients. Verdicts are informational risk signals, not financial advice.