XRPL.to Token Analytics

io.github.xrpltoPublished by GitHub account xrpltov1.20.0Updated Oct 26, 2026

XRP Ledger tokens, AMM pools, NFTs, accounts and transactions: prices, holders, trades and history

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

Remote MCP endpoint giving an assistant XRP Ledger token analytics: prices, holders, trades, AMM pools, NFTs, accounts and transactions.

What you can do
  • Look up XRP Ledger tokens with prices, holders and trade activity
  • Inspect AMM pools and their related data
  • Query NFTs, accounts and transactions, including history
  • No tool list is published, so exact operations are not documented
When to use it
Useful when you need XRP Ledger market and on-chain data inside an assistant conversation, such as checking a token's price, holders or trades, or reviewing an account's transactions and AMM pools.
Requirements
Remote streamable HTTP endpoint at api.xrpl.to; no local install. Requires a paid xrpl.to plan (Developer, Business or Professional) and an API key sent in the X-Api-Key header, obtained from the xrpl.to dashboard.
Before you install
The API key is a paid-plan credential sent as the X-Api-Key header; keep it out of shared logs and prompts. Queries and identifiers you send go to the third-party xrpl.to service. No tool list is published, so review what the server can do before relying on it.

Installation

In SourceWeft

  1. Open XRPL.to Token Analytics in the dashboard and add it to a workspace.
  2. Connect X-Api-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.xrplto%2Fxrpl-to/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "xrpl-to-token-analytics": {
      "type": "http",
      "url": "https://api.xrpl.to/v1/mcp",
      "headers": {
        "X-Api-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.20.0LatestOct 20, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.