XRPL Token Guard
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Bind address for the Streamable HTTP transport | 127.0.0.1 |
| PORT | No | Bind port for the Streamable HTTP transport | 8787 |
| XRPL_RPC_URLS | No | Public XRPL JSON-RPC endpoints, tried in order (comma-separated) | https://xrplcluster.com,https://s1.ripple.com:51234,https://s2.ripple.com:51234 |
| ALLOWED_ORIGINS | No | Comma-separated Origin allow-list for /mcp (any by default) | |
| TOKEN_GUARD_LINKS | No | Adds a link to a free ledger-evidence page for the token when one exists; off disables it | on |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_token_safetyA | Live safety check of an XRP Ledger token (issued currency). Detects fake look-alikes of famous tokens (e.g. a fake RLUSD), issuers that can still mint, freeze or claw back, global freezes, transfer fees, unverified domains, whale concentration, thin AMM liquidity and brand-new issuers. Returns a verdict (High risk / Caution / No red flags found / Not enough data), the reasons behind it with the exact ledger facts, and a one-sentence spoken summary. |
| is_it_the_real_tokenA | Answers "is this the real RLUSD / USDC / SOLO?" using the verified official issuers (RLUSD: rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De; USDC: rGm7WCVp9gb4jZHWTEtGUr4dd74z2XuWhE; SOLO: rsoLo2S1kiGeCcn6hCUXVrCpGMWLrRrLZz). Give the ticker alone to learn the official issuer, or ticker + issuer to confirm or expose an imitation. Instant, no ledger call. |
| check_wallet_securityA | Checks whether anyone besides the owner can sign for an XRPL wallet: an unexpected regular key or multisig signer list (the classic drainer setup), and flags changes made in the last 7 days as urgent. Read-only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| voice_token_check | Guides a voice assistant to answer token-safety questions briefly and honestly. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools target distinct objects: issued tokens, official token identity, and wallet signing authority. There is some overlap between check_token_safety and is_it_the_real_token regarding fake tokens, but the descriptions make the boundary clear: one is an instant official-issuer lookup, the other is a live ledger risk assessment.
Two tools follow a consistent check_* pattern (check_token_safety, check_wallet_security), but is_it_the_real_token breaks the verb_noun convention and is phrased as a question. The set is still readable, but the naming convention is mixed.
Three tools is a narrow but defensible surface for a focused safety-checking server; each tool covers a distinct safety question. It is on the thin side, but not trivially so.
The core workflows are covered: token risk screening, official issuer verification, and wallet signer checks. Minor gaps remain, such as checking trustlines/balances or broader issuer history, but agents can work around these for the stated purpose.