# XRPLink (remote · xrp-link.com)

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

- Trust score: 65/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `xrp-link.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/joverman-xrplink/xrp-link.md), [page](https://verifymcp.io/servers/joverman-xrplink/xrp-link)

## Channel facts

- Endpoint: `https://xrp-link.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 469 tokens (~58/item across 8 items; 4 tools + 4 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 11/100
  - Stability check failed: schema churn in the 10 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the XRPLink MCP server?

XRPLink is a hosted endpoint at https://xrp-link.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http joverman-xrplink 'https://xrp-link.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "joverman-xrplink": {
      "url": "https://xrp-link.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "joverman-xrplink": {
      "type": "http",
      "url": "https://xrp-link.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.joverman-xrplink]
url = "https://xrp-link.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "joverman-xrplink": {
      "type": "remote",
      "url": "https://xrp-link.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add joverman-xrplink --url 'https://xrp-link.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  joverman-xrplink:
    url: "https://xrp-link.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "joverman-xrplink": {
      "Transport": "http",
      "Url": "https://xrp-link.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add joverman-xrplink -t streamable-http -u 'https://xrp-link.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "joverman-xrplink": {
      "type": "http",
      "url": "https://xrp-link.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 11.

### 2026-11-03 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 1 to 4.

### 2026-10-28 (score 63, +1)

- [security regression] Stability: 0.03 → fail
- [security regression] A breaking change shipped without a version bump: still 0.3.0
- [security regression] Tool “get_attestation_by_round” was removed
- [security improvement] HSTS header: fail → pass
- [security] Tool “get_attestation_status” rewrote its description, which is the text the model reads
- [security] Tool “lookup_attestation_by_tx” rewrote its description, which is the text the model reads
- [security] Tool “verify_xrp_payment” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 49 → 58
- [functional regression] Resource “Live Network Status” was removed

### 2026-10-27 (score 62, 0)

- [security] Tool “verify_xrp_payment” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 62)

First indexed and scored.

## MCP tools (4)

### `verify_xrp_payment` (~215 tokens)

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.

Input parameters:

- `txHash` (string, required): XRP transaction hash (64 hex characters, with or without 0x prefix). Example: 388076B7245A60A13D6A764C8D0B5919F8A77E04E720C32CA1E30E9B7A291F22

### `get_attestation_status` (~56 tokens)

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.

Input parameters:

- `id` (string, required): Attestation UUID returned from verify_xrp_payment

### `lookup_attestation_by_tx` (~102 tokens)

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.

Input parameters:

- `txHash` (string, required): XRP transaction hash (64 hex characters). Example: 388076B7245A60A13D6A764C8D0B5919F8A77E04E720C32CA1E30E9B7A291F22

### `get_server_info` (~26 tokens)

Get XRPLink server information, network details, contract addresses, and white-label branding.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/joverman-xrplink/xrp-link#diagnostics

## Score history

- 2026-11-05: 65
- 2026-11-04: 64
- 2026-11-03: 64
- 2026-11-02: 63
- 2026-11-01: 63
- 2026-10-31: 63
- 2026-10-30: 63
- 2026-10-29: 63
- 2026-10-28: 63
- 2026-10-27: 62
- 2026-10-26: 62

## Common questions

### What is the XRPLink MCP server?

XRPLink is an MCP server listed in the public MCP registry as io.github.joverman/xrplink. Verify XRP payments on Flare FDC. Agents subscribe or pay per attestation via x402 on XRPL. This page covers its hosted endpoint (https://xrp-link.com/mcp).

### Is the XRPLink MCP server safe to use?

XRPLink scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the XRPLink MCP server expose?

XRPLink exposes 4 tools: verify_xrp_payment, get_attestation_status, lookup_attestation_by_tx, get_server_info. Their descriptions and schemas cost roughly 399 tokens of context every time the server is loaded.

### Does the XRPLink MCP server require authentication?

No. We connected to XRPLink without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the XRPLink MCP server still maintained?

XRPLink is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://xrp-link.com/mcp
- Repository: https://github.com/joverman/xrplink
- Changelog RSS feed: https://verifymcp.io/servers/joverman-xrplink/xrp-link.xml
- Changelog JSON feed: https://verifymcp.io/servers/joverman-xrplink/xrp-link.json
- HTML version of this page: https://verifymcp.io/servers/joverman-xrplink/xrp-link