Skip to content

XRPLink MCP server

io.github.joverman/xrplinkjovermanstreamable-httpv0.3.1Scanned

Verify XRP payments on Flare FDC. Agents subscribe or pay per attestation via x402 on XRPL.

4 tools: 1 do something that can't be undone and 3 only read.

Tools: 0 delete, 1 irreversible, 0 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the XRPLink MCP server can do

The XRPLink MCP server is published by the GitHub account joverman. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (verify_xrp_payment), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 0.3.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Can't be undone 1Claude Code: ask
  • verify_xrp_paymentSubmit a native XRP Payment hash for FDC attestation on Flare.No findings

    Why it is in this group

    • The name "verify_xrp_payment" says "payment": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Submit a native XRP Payment hash for FDC attestation on Flare. Only Payments from the last 14 days can be proven. Subscription API keys inside quota are not charged extra (Paid: 20 mainnet attestations per billing period; Pro: 100). Failed prepares do not consume quota. Without a key, or over quota, the tool returns an x402 payment challenge (RLUSD first, then XRP via the XRPL facilitator). Over-quota subscribers can upgrade or buy a single extra attestation. A valid PAYMENT-SIGNATURE pays for exactly one attestation. Status checks are free. Proof takes ~90-180 seconds; use get_attestation_status.
Only reads 3Show 3 read-only tools
  • get_attestation_statusGet the current status of an attestation by its UUID.No findings

    Why it is in this group

    • The name "get_attestation_status" says "get": a word for reading.
    Description, as the server wrote it
    Get the current status of an attestation by its UUID. Unauthenticated callers receive the public receipt subset. The owning API key receives the full proof.
  • get_server_infoGet XRPLink server information, network details, contract addresses, and white-label branding.No findings

    Why it is in this group

    • The name "get_server_info" says "get": a word for reading.
    Description, as the server wrote it
    Get XRPLink server information, network details, contract addresses, and white-label branding.
  • lookup_attestation_by_txLook up an attestation by its original XRP transaction hash.No findings

    Why it is in this group

    • The name "lookup_attestation_by_tx" says "lookup": a word for reading.
    Description, as the server wrote it
    Look up an attestation by its original XRP transaction hash. Unauthenticated callers receive the public receipt subset. The owning API key receives the full proof.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 17, 2026, 15:24 UTC, unchanged since Oct 26, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 irreversible). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://xrp-link.com/mcp: tools/list returned 4 tools to an anonymous client, including verify_xrp_payment (irreversible)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 removed, 3 changed.−1 removed~3 changedView diff

Install

Pinned to version 0.3.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http xrplink https://xrp-link.com/mcp
claude mcp add --transport http xrplink https://xrp-link.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__xrplink__get_attestation_status",
      "mcp__xrplink__lookup_attestation_by_tx",
      "mcp__xrplink__get_server_info"
    ],
    "ask": [
      "mcp__xrplink__verify_xrp_payment"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as xrplink. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.joverman/xrplink/verify?hash=e838220326ad9ef9ed5760fa4b5657edbfc49dcfeed4b9d3096ed571fefe7d3c" | jq -e '.changed == false'

Pinned hash e838220326ad, from Nov 9, 2026, 09:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.joverman/xrplink/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.joverman/xrplink
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.joverman/xrplink.svg)](https://radar.anlyon.com/servers/io.github.joverman/xrplink)

Source: MCP Registry · repository. Synced Nov 9, 2026, 09:17 UTC.

XRPLink MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the XRPLink MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the XRPLink MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the XRPLink MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: verify_xrp_payment.

What tools does the XRPLink MCP server have?

4 tools: 1 irreversible, 3 read. verify_xrp_payment, get_attestation_status, lookup_attestation_by_tx and get_server_info.

Does the XRPLink MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the XRPLink MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the XRPLink MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.