Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

XRPLHub — XRPLScore, MPT issuer risk & payment pre-checks

REMOTE · WWW.XRPLHUB.IO

XRPL wallet scores, wallet permissions, batch send, MPT risk, screening, pre-checks. Never signs.

Available components

0 this week 25 Trust /100

Last scanned (14 hours ago)

Scores higher than 10% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security63
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 14 Nov 26 −50
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 10 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 7 Nov 26 +2
    • Stability: fail → pass ▲ security
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 +1

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

  • 4 Nov 26 −1

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

  • 11 Oct 26 0
    • Stability: pass → fail ▼ security
    • Destructive annotations: pass → 0 functional
    • Server version: 1.16.0 → 1.18.0 functional
    • New tool “check_wallet_permissions” functional
    • New tool “prepare_batch_send” functional
Diagnostics

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 21 Nov 2026 · Probed https://www.xrplhub.io/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.xrplhub.io CN=YR1,O=Let's Encrypt,C=US 26 Sept 2026 25 Dec 2026 RSA 2048 SHA256-RSA 6341857d5c7597c8d7d3b39e2eaf77cc55c
SANs: www.xrplhub.io
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.xrplhub.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
xrplhub.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 402
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.xrplhub.io/api/mcp HTTP error 402
http (plaintext) http://www.xrplhub.io/api/mcp HTTPS enforced 308 https://www.xrplhub.io/api/mcp
MCP tools · 21 exposed · ~3,850 tokens

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 →

Tool Tokens
check_domain_eligibility ~149

Check whether an XRPL account holds a credential that satisfies a PermissionedDomain (XLS-80d) — the question every domain operator and every would-be participant actually asks before a real transaction. Live against a validated mainnet ledger. Eligibility is OR: any ONE accepted, unexpired credential matching the domain's AcceptedCredentials is enough. Params: wallet_address (r..., required), domain_id (64-hex DomainID, the PermissionedDomain ledger index, required). Free, no signup.

NameTypeReqDescription
domain_idstringyesThe PermissionedDomain's ledger index — 64 hex characters
wallet_addressstringyesXRPL classic address to check (starts with r)

No output schema declared.

No examples provided.

check_mpt_risk ~186

Get the risk view of one XLS-33 Multi-Purpose Token issuance before touching it: what the issuer CAN DO to a holder (clawback, freeze, require-auth, whether it's transferable at all) plus the issuer's XRPLScore. Free. For the full issuer picture — account age, xrp-ledger.toml-verified domain, credentials held (live ledger reads) — GET /api/x402/usdc/mpt/{id} pays $0.01 USDC on Base via x402. Every response states its source and returns 'unknown', never 'does not exist', when an issuance isn't found. Params: issuance_id (48-hex MPTokenIssuanceID, required). No signup.

NameTypeReqDescription
issuance_idstringyesThe MPTokenIssuanceID — 48 hexadecimal characters (XLS-33, 192-bit)

No output schema declared.

No examples provided.

check_service_health ~99

Check whether the XRPLHub money path is working BEFORE you pay: database, Xaman, both x402 facilitators (t54 RLUSD + CDP USDC-on-Base), the on-ledger anchor config, the credential signing secret, and alerting. Returns overall "ok" | "warn" | "down" plus a per-component list. Poll this if a prior paid call failed. No params. Free, no signup.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

check_wallet_permissions ~180

Who can move money out of an XRPL wallet: its master key, a regular key, a multi-sign signer list, permission delegations (given and received — live on mainnet since 2026-10-08), and money others can pull without a new approval (checks, payment channels, escrows, open DEX and NFT offers, tickets). One plain-English sentence per finding plus the raw ledger facts. This is a PAID x402 call: $0.02 in USDC on Base or RLUSD on the XRP Ledger at GET /api/x402/permissions?address=r.... This tool returns the payment resource to call; it does not run the check. People can use the free page at https://www.xrplhub.io/permissions.

NameTypeReqDescription
addressstringyesThe XRPL account (r...) to check

No output schema declared.

No examples provided.

check_xrpl_score ~150

Get a 300–850 creditworthiness score for any XRP Ledger wallet before you pay, lend to, trade with, or onboard it. You get back: the score, a letter grade, peer percentile, a per-signal breakdown (account age, lifetime tx history, financial health, token engagement, DEX activity, AMM participation, security config, NFTs), and ranked tips to raise it. Params: wallet_address (r... classic address, 25–35 chars, required). Free — no API key, no signup, 100% public ledger data.

NameTypeReqDescription
wallet_addressstringyesXRP Ledger classic address to score (starts with r, 25–35 characters)

No output schema declared.

No examples provided.

donate_to_community_fund ~214

Donate XRP or RLUSD to the XRPLHub Community Grant Treasury — a transparent on-chain fund that pays approved applicants wallet-to-wallet with zero overhead. Returns the treasury address and, if you pass donor_wallet, a ready-to-sign Payment txjson; every donation and payout is recorded on the XRP Ledger and publicly verifiable. Params: amount (number, required), currency (XRP|RLUSD, default XRP), donor_wallet (r..., optional), message (optional). No signup.

NameTypeReqDescription
amountnumberyesAmount to donate. Minimum 1. Any size welcome — even 1-5 XRP helps fund a real grant.
currencystring–XRP or RLUSD. Default: XRP. Use RLUSD for a stable USD-equivalent donation.
donor_walletstring–Optional. XRPL wallet address of the donor. Providing this allows building a ready-to-sign Payment transaction.
messagestring–Optional. A short dedication or message to attach to the donation record.

No output schema declared.

No examples provided.

get_account_credentials ~225

Get every XLS-70 credential an XRPL account holds — issuer, type, whether it has been accepted, whether it's expired, and its expiry date. Live against a validated mainnet ledger (never stale). Use this before trusting a counterparty who claims to hold a credential. Default walks the owner directory (bounded ~20s; response has coverage "complete"/"partial" — for an exchange-scale account it can be partial). Pass issuer (and credential_type unless it is XRPLHub's issuer) to do a direct ledger lookup instead — always fast and always complete. Params: wallet_address (r..., required), issuer (r..., optional), credential_type (name or hex, optional). Free, no signup.

NameTypeReqDescription
credential_typestring–Optional — credential type (plain name or hex); required with issuer unless the issuer is XRPLHub's
issuerstring–Optional — restrict to one issuer via a direct ledger lookup (no owner-directory walk)
wallet_addressstringyesXRPL classic address to look up (starts with r)

No output schema declared.

No examples provided.

get_issuer_credentials ~100

Get everything an issuer account has issued: every credential type, distinct subject count, and acceptance rate. Served from a network-wide census rebuilt on a schedule — the response includes coverage ("complete" or "partial") so a mid-walk answer is never mistaken for a finished count. Params: issuer_address (r..., required). Free, no signup.

NameTypeReqDescription
issuer_addressstringyesXRPL classic address of the credential issuer (starts with r)

No output schema declared.

No examples provided.

get_issuer_mpts ~96

Everything one issuer has put out as Multi-Purpose Tokens (XLS-33), from the registry index, plus the issuer's own XRPLScore. Each issuance lists the issuer's powers over a holder. Response carries coverage ('complete-per-known-issuer'/'partial'). Params: issuer_address (r..., required). Free, no signup.

NameTypeReqDescription
issuer_addressstringyesXRPL issuer address (starts with r)

No output schema declared.

No examples provided.

get_lending_exposure ~274

A borrower's TOTAL XLS-66 lending exposure across ALL loan brokers in one call — the XRP Ledger has no aggregate borrower-debt object, so a broker carrying first-loss capital cannot see a borrower's total leverage elsewhere. Returns: outstanding by asset, loan count, distinct broker count, defaults / impairments / overdue, XRPLHub's XRPLScore, and an observation history summary. IMPORTANT: XLS-66 keeps CURRENT exposure only. A defaulted loan zeroes its own amounts (the flag is the credit event, not the balance), and either the borrower or the broker can delete a paid or defaulted loan to reclaim the borrower's reserve — a borrower can erase evidence of their own default. Every call here persists an immutable Merkle-anchored snapshot. `disposition` = 'no-loans-ever' means we have never observed a loan (NOT proof of none); 'history-only' means loans were seen before but none are on the ledger now. XLS-66 is not yet enabled on mainnet — until it is, this returns amendment-not-active with the live XRPLScore. Not underwriting or credit advice. Params: borrower (r..., required). Free via MCP.

NameTypeReqDescription
borrowerstringyesXRPL classic address (r..., 25–35 chars) of the borrower

No output schema declared.

No examples provided.

get_lending_history ~166

Every loan XRPLHub has EVER observed for a borrower, built from append-only exposure snapshots — the credit file the XRP Ledger can't keep. Per loan: first/last observed ledger, last-known status, monotonic everDefaulted / everImpaired / everOverdue flags, and for loans since deleted from the ledger, the ledger window in which they vanished. A borrower who defaulted and then deleted the loan shows nothing on-ledger; here it shows as vanished with everDefaulted true. `observationWindow` says how far back our view goes — loans deleted before we first saw this borrower are invisible to us. Params: borrower (r..., required). Free, no signup.

NameTypeReqDescription
borrowerstringyesXRPL classic address (r...) of the borrower

No output schema declared.

No examples provided.

get_monitoring_info ~182

Describe XRPLHub's continuous-monitoring service so an agent can decide whether to use it: what it watches for a list of wallets (score drops against a threshold YOU set, OFAC SDN list hits, and — once XLS-66 activates — first loan / overdue / impaired / defaulted), how it is delivered (HMAC-signed webhooks, once-a-day checks, attested Merkle-anchored history), per-plan watch slots, the shared capacity limit, the consumer-use acknowledgement text that subscribing requires (no FCRA/ECOA consumer credit, insurance, employment or housing decisions) and the endpoints. Layered on top of underwriting, never a replacement; no recommendation, no probability of default. Subscribing needs an API key over HTTP (POST /api/monitor/subscribe), not this tool. No params. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_underwriting_inputs ~192

The full underwriting-inputs bundle a LoanBroker needs for an XLS-66 decision, in one call: cross-broker exposure, XRPLScore + grade, OFAC SDN screening (with its own verifiable receipt), observation history + gaps, and one Merkle-anchored attestation over the whole bundle. FACTS ONLY — it never returns a recommended principal, rate, approve/decline, or probability of default; the broker decides. This is a PAID x402 call: $0.05 USDC on Base at GET /api/x402/lending/underwrite?borrower=r... (no free tier, no API key). For the free components use get_lending_exposure and screen_address_ofac. This tool returns the payment resource details. Params: borrower (r..., required).

NameTypeReqDescription
borrowerstringyesXRPL classic address (r...) of the borrower

No output schema declared.

No examples provided.

issue_score_credential ~228

Get a certificate of a wallet's XRPLScore, signed by XRPLHub, with the score computed fresh at issuance. A counterparty checks it by asking XRPLHub's verify URL — the signature is an HMAC under a key only XRPLHub holds, so this is XRPLHub's own attestation, not independently verifiable proof, and the buyer need not control the wallet. Two calls: first returns a Xaman payment request (1 XRP or 1 RLUSD, valid 90 days); call again with the same wallet_address + returned uuid after signing to get certId and verifyUrl. Params: wallet_address (r..., required), currency (XRP|RLUSD, default XRP), uuid (2nd call only). No signup.

NameTypeReqDescription
currencystring–Payment currency. Defaults to XRP.
uuidstring–Only for the second call: the payment uuid returned by the first call, after the user has signed in Xaman.
wallet_addressstringyesXRP Ledger wallet address the credential will attest to (starts with r)

No output schema declared.

No examples provided.

precheck_payment ~260

Before your agent pays an XRPL address: one verdict (block / caution / proceed) by fixed published rules — the destination's XRPLScore, a sanctions screen against every list XRPLHub holds (with a verifiable receipt), account age and ledger flags, and whether the ledger would REJECT the payment (missing destination tag, Deposit Authorization, no RLUSD trust line, unfunded account). This is a PAID x402 call: $0.03 in USDC on Base or RLUSD on the XRP Ledger at GET /api/x402/precheck. This tool returns the payment resource to call; it does not run the check. Params: destination (r..., required), amount, currency (XRP|RLUSD), destination_tag, from (your paying address).

NameTypeReqDescription
amountstring–Optional: the amount you intend to send (plain decimal)
currencystring–Optional: XRP (default when amount is given) or RLUSD
destinationstringyesThe XRPL address (r...) you are about to pay
destination_taginteger–Optional: the destination tag you will use
fromstring–Optional: your paying address — lets the check test Deposit Authorization preauth

No output schema declared.

No examples provided.

prepare_batch_send ~155

Pay 2 to 8 XRPL addresses with ONE signature, all or nothing (XRPL Batch, tfAllOrNothing — live on mainnet since 2026-10-09). Checks every payment on the live ledger first (destination exists or will be created, destination tag, Deposit Authorization, RLUSD trust line, sender balance + fee) and refuses a batch that would fail. Returns the UNSIGNED Batch transaction and a Xaman sign link. FREE. XRPLHub never signs: the sender signs with its own wallet, before sending any other transaction from that account (the batch uses the next sequence numbers).

NameTypeReqDescription
fromstringyesThe paying XRPL account (r...)
recipientsarrayyes–

No output schema declared.

No examples provided.

screen_address_ofac ~274

Compare one XRPL address against a vintage-pinned snapshot of the US Treasury OFAC SDN list (exact address-string match only) and get a factual, Merkle-anchored receipt. ATTESTS TO PROCESS, NOT GROUND TRUTH: the receipt records that the address was compared against a named list snapshot (its OFAC publish date + the SHA-256 of the exact file) at a stated time, and what the comparison found. A "no match" means the address did NOT appear on that list version — it is NOT a statement that the address is clean, safe, or unsanctioned. This is not legal or compliance advice, makes no compliance decision, and does not discharge your own screening obligations. Scope: OFAC SDN only — no EU/UK/UN lists, no name/alias/fuzzy matching, no transaction-graph analysis. Returns queryId (verify it later with verify_attestation), the list {name,vintage,sha256}, result {listed, matches[]}, and a one-sentence factual statement. Params: address (r..., required). Free via MCP. Terms: /legal/screening.

NameTypeReqDescription
addressstringyesXRPL classic address (r..., 25–35 chars) to compare against the OFAC SDN list

No output schema declared.

No examples provided.

search_mpts ~148

Search the XRPL Multi-Purpose Token (XLS-33) registry index by issuer address, MPTokenIssuanceID (or a hex prefix of one), or token name / ticker. Returns each match with issuer powers (clawback, freeze, require-auth, transferable), supply, holder count and source. Served from the index — the response carries coverage ('complete' or 'partial') and lastCompletedPassAt; treat 'partial' as a floor, not the whole population. Params: q (required). Free, no signup.

NameTypeReqDescription
qstringyesIssuer address (r...), MPTokenIssuanceID or hex prefix, or token name/ticker

No output schema declared.

No examples provided.

submit_grant_application ~249

Apply for a community micro-grant ($25–$100) paid wallet-to-wallet from the XRPLHub on-chain treasury for rent, utilities, groceries, medical, transport, or childcare. Returns a grant id and status. A person reviews every application and makes every decision — no automated triage, no middleman. Params: wallet_address (r..., required), category (RENT|UTILITIES|GROCERIES|MEDICAL|TRANSPORT|CHILDCARE|OTHER, required), amount (25–100, required), description (2–4 sentences, required). No signup.

NameTypeReqDescription
amountnumberyesAmount requested in RLUSD (1–100)
categorystringyesGrant category: RENT, UTILITIES, GROCERIES, MEDICAL, TRANSPORT, CHILDCARE, or OTHER
currencystring–Payout currency. Default and recommended: RLUSD
descriptionstringyesClear description of the need, situation, and urgency (2–4 sentences). Be specific — vague applications are harder for the reviewer to verify.
wallet_addressstringyesXRPL wallet address where the grant will be sent if approved

No output schema declared.

No examples provided.

verify_attestation ~172

Given a queryId from screen_address_ofac OR get_lending_exposure, return everything needed to verify that receipt WITHOUT trusting XRPLHub: the canonical leaf, its Merkle inclusion proof, the on-ledger anchor transaction hash + ledger close time, and the SHA-256 of the source data (the OFAC SDN snapshot, or — for lending — the exact list of Loan ids observed). Rebuild the leaf, fold the proof to the Merkle root, confirm that root is in the anchor tx's MemoData. Before the daily anchor runs it shows status "pending" with the leaf hash only. Params: query_id (UUID, required). Free, no signup.

NameTypeReqDescription
query_idstringyesThe queryId (UUID) from screen_address_ofac or get_lending_exposure

No output schema declared.

No examples provided.

verify_mpt_registry ~151

Get the latest on-ledger anchor of the MPT registry (BIS Working Paper 1374 pattern): a Merkle root over the canonicalised index, committed in a Memo on a transaction from a dedicated anchor wallet (not the credential issuer). Returns the root, its tx hash, ledger index, issuance/issuer counts, coverage, and the exact canonicalisation + Merkle scheme so you can reproduce the root from the published /api/mpt/search + /api/mpt/issuer data and check that those rows match the root we anchored on-ledger at a known time (proves published-rows-match-anchored-root, not immutability). No params. Free, no signup.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the XRPLHub — XRPLScore, MPT issuer risk & payment pre-checks MCP server?

XRPLHub — XRPLScore, MPT issuer risk & payment pre-checks is a hosted endpoint at https://www.xrplhub.io/api/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 · www.xrplhub.io

# add to Claude Code
claude mcp add --transport http dcroyalty-xrplhub 'https://www.xrplhub.io/api/mcp'
Common questions

What is the XRPLHub — XRPLScore, MPT issuer risk & payment pre-checks MCP server?

XRPLHub — XRPLScore, MPT issuer risk & payment pre-checks is an MCP server listed in the public MCP registry as io.github.Dcroyalty/xrplhub. XRPL wallet scores, wallet permissions, batch send, MPT risk, screening, pre-checks. Never signs. This page covers its hosted endpoint (https://www.xrplhub.io/api/mcp).

Is the XRPLHub — XRPLScore, MPT issuer risk & payment pre-checks MCP server safe to use?

XRPLHub — XRPLScore, MPT issuer risk & payment pre-checks scores 25 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 XRPLHub — XRPLScore, MPT issuer risk & payment pre-checks MCP server expose?

XRPLHub — XRPLScore, MPT issuer risk & payment pre-checks exposes 21 tools: issue_score_credential, check_xrpl_score, get_account_credentials, get_issuer_credentials, check_mpt_risk, and 16 more. Their descriptions and schemas cost roughly 3,850 tokens of context every time the server is loaded.

Does the XRPLHub — XRPLScore, MPT issuer risk & payment pre-checks MCP server require authentication?

Its publisher declares no required credentials for XRPLHub — XRPLScore, MPT issuer risk & payment pre-checks. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the XRPLHub — XRPLScore, MPT issuer risk & payment pre-checks MCP server still maintained?

XRPLHub — XRPLScore, MPT issuer risk & payment pre-checks is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the XRPLHub — XRPLScore, MPT issuer risk & payment pre-checks MCP server?

VerifyMCP ran 5 checks on XRPLHub — XRPLScore, MPT issuer risk & payment pre-checks, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about XRPLHub — XRPLScore, MPT issuer risk & payment pre-checks: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.