XRPL Wallet Risk Score

io.github.kynto2001-ctrlPublished by GitHub account kynto2001-ctrlv1.3.0Updated Oct 24, 2026

XRPL wallet risk scoring. Behavioral tags, sub-scores, graph analysis. Pay per call in XRP.

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

A local MCP server that scores the risk of XRPL wallets, returning behavioral tags, sub-scores and graph analysis, paid per call in XRP.

What you can do
Score XRPL wallets for risk, with behavioral tags and sub-scores returned for each address looked up. Provide graph analysis of wallet relationships as part of the risk assessment. Charge each call in XRP, so the assistant's lookups are billed per request.
When to use it
Useful when an assistant needs a quick risk read on XRPL addresses, for example before interacting with an unfamiliar wallet or reviewing counterparties. Less relevant if you do not work with the XRP Ledger or cannot pay per call in XRP.
Requirements
Runs as a local process over stdio, installed from the npm package, so Node.js and npm are needed. No authentication, environment variables or headers are declared. Calls are paid in XRP, so a funded means of payment is implied.
Before you install
Each call is billed in XRP, so usage spends real funds; set limits before letting an assistant query freely. Wallet addresses you submit are sent to the scoring service, which may reveal which accounts you are investigating. Risk scores are third-party assessments and should not be treated as definitive.

Installation

In SourceWeft

  1. Open XRPL Wallet Risk Score in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.3.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.