XRPLink
REMOTE · XRP-LINK.COM
Verify XRP payments on Flare FDC. Agents subscribe or pay per attestation via x402 on XRPL.
Available components
Last scanned (19 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Crypto and Web3
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. How we score → Why this is hard to score →
Endpoint Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 469 tokens (~58/item across 8 items; 4 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability check failed: schema churn in the 9 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 1 to 4.
- 28 Oct 26 +1
- Stability: 0.03 → fail ▼ security
- A breaking change shipped without a version bump: still 0.3.0 ▼ security
- Tool “get_attestation_by_round” was removed ▼ security
- 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 security
- Schema quality: 49 → 58 ▼ functional
- Resource “Live Network Status” was removed ▼ functional
- 27 Oct 26 0
- Tool “verify_xrp_payment” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 26 Oct 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://xrp-link.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=xrp-link.com | CN=YE2,O=Let's Encrypt,C=US | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6ca542e68ac9a33db31b563672e2dfeb5e4 |
| SANs: *.xrp-link.com, xrp-link.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of xrp-link.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| xrp-link.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://xrp-link.com/mcp | Verified | 200 | |
| http (plaintext) | http://xrp-link.com/mcp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_attestation_status ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Attestation UUID returned from verify_xrp_payment |
No output schema declared.
No examples provided.
get_server_info ~26
Get XRPLink server information, network details, contract addresses, and white-label branding.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_attestation_by_tx ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| txHash | string | yes | XRP transaction hash (64 hex characters). Example: 388076B7245A60A13D6A764C8D0B5919F8A77E04E720C32CA1E30E9B7A291F22 |
No output schema declared.
No examples provided.
verify_xrp_payment ~215
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.
| Name | Type | Req | Description |
|---|---|---|---|
| txHash | string | yes | XRP transaction hash (64 hex characters, with or without 0x prefix). Example: 388076B7245A60A13D6A764C8D0B5919F8A77E04E720C32CA1E30E9B7A291F22 |
No output schema declared.
No examples provided.
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.
remote · xrp-link.com
claude mcp add --transport http joverman-xrplink 'https://xrp-link.com/mcp'
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 64 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.