XRPL Token Guard
Related Servers
Alternatives to XRPL Token Guard
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to assess the risk of crypto wallets, tokens, and smart contracts by providing read-only on-chain analysis, 0-100 risk scoring with explanations, fund tracing, and contract inspection before interaction.6MIT
- AlicenseAqualityBmaintenanceEnables users and AI agents to verify whether a crypto recipient address is an address-poisoning lookalike or has an invalid EIP-55 checksum before sending funds, and provides access to an on-chain history scan for suspicious transfers.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and apps to check URLs, domains, IP addresses, phone numbers, emails, crypto wallets, IBANs, mobile apps, and payment handles for scam, phishing, and fraud risk, returning verdicts, probabilities, facts, and reason codes.MIT

pnllabs-mcpofficial
AlicenseNot gradedqualityCmaintenanceGives AI trading agents machine-readable trust and risk verdicts on Solana by checking whether a wallet's realized PnL makes it worth copying, where its funds came from, whether a token is structurally safe, and what a given trade size would really cost in slippage. Exposes these four checks as MCP tools callable against a hosted x402 pay-per-call API, so agents can hard-stop bad trades without RPC keys, signup, or local setup.1MIT- AlicenseAqualityBmaintenanceEnables AI assistants to check whether a crypto token, link, or forwarded "gem" message is a scam by running contract rules, live test trades, creator history, and market data across 64 networks, returning plain-English or Pidgin verdicts. Also supports scanning messages, reviewing a token's past checks, and explaining individual findings.5MIT
- AlicenseAqualityCmaintenanceEnables AI agents to check an EVM address on Base for risk (safe, caution, danger) before sending funds, with reasons, paid per call via x402 from the user's own wallet.7309 npm1MIT
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.