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.

XRPLME Country Intelligence

REMOTE · API.XRPLME.ONLINE

Source-backed country policy data for AI agents; pay-per-call via x402 (XRP or USDC).

+4 this week 72 Trust /100

Last scanned (51 minutes ago)

Scores higher than 58% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Education and Research

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 Security46
Transport & Reachability100
Schema Quality & AI Usability80
  • 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 1053 tokens (~105/item across 10 items; 8 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 5 Nov 26 +1
    • A breaking change shipped without a version bump: still 1.0.1 ▼ security
    • Tool “xrplme_regional_research” was removed ▼ security
    • Schema quality: fail → pass ▲ functional
  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “xrplme_list_countries” rewrote its description, which is the text the model reads security
  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +49
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Stability: unverified → 0.67 ▲ functional
  • 26 Oct 26 −48
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.60 → 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
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 25 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “xrplme_get_country_data” rewrote its description, which is the text the model reads security
    • Tool “xrplme_get_country_schema” rewrote its description, which is the text the model reads security
    • Tool “xrplme_get_pricing” rewrote its description, which is the text the model reads security
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 5 Nov 2026 · Probed https://api.xrplme.online/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=xrplme.online CN=WE1,O=Google Trust Services,C=US 14 Oct 2026 13 Jan 2027 ECDSA 256 ECDSA-SHA256 aa6ac0ba1e3f6a900e1ca4687eaf9d08
SANs: xrplme.online, *.xrplme.online
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.xrplme.online. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
online. present 30961 13 Verified
xrplme.online. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.xrplme.online/mcp Verified 200
http (plaintext) http://api.xrplme.online/mcp Inconclusive 404
MCP tools · 8 exposed · ~855 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
xrplme_get_country_data ~212

Latest data + freshness for one country. REQUIRES PAYMENT. XRPL : 5 XRP via x_payment_signature + x_inv_id Solana : $7.00 USDC via x_sol_payload Args: slug: Country slug (e.g., "thailand") x_payment_signature: JSON string containing tx_hash AND signedTxBlob (hex-encoded signed XRPL tx). Both are required: the t54 facilitator decodes the blob to bind the on-chain InvoiceID. x_inv_id: Invoice ID x_sol_payload: OPTIONAL. base64 of an x402 PaymentPayload paying USDC on Solana. When present it is verified AND settled via the local facilitator; the XRPL arguments are then ignored.

NameTypeReqDescription
slugstringyes–
x_inv_idstring––
x_payment_signaturestring––
x_sol_payloadstring––

No output schema declared.

No examples provided.

xrplme_get_country_schema ~210

Field schema for one country. REQUIRES PAYMENT. XRPL : 1 XRP via x_payment_signature + x_inv_id Solana : $1.00 USDC via x_sol_payload Args: slug: Country slug (e.g., "thailand") x_payment_signature: JSON string containing tx_hash AND signedTxBlob (hex-encoded signed XRPL tx). Both are required: the t54 facilitator decodes the blob to bind the on-chain InvoiceID. x_inv_id: Invoice ID x_sol_payload: OPTIONAL. base64 of an x402 PaymentPayload paying USDC on Solana. When present it is verified AND settled via the local facilitator; the XRPL arguments are then ignored.

NameTypeReqDescription
slugstringyes–
x_inv_idstring––
x_payment_signaturestring––
x_sol_payloadstring––

No output schema declared.

No examples provided.

xrplme_get_country_status ~29

Live free health probe for one country. FREE.

NameTypeReqDescription
slugstring––

No output schema declared.

No examples provided.

xrplme_get_pricing ~141

Pricing on both rails. Standard: 1 XRP or $1.00 USDC. AI-enhanced: 5 XRP or $7.00 USDC. FREE. Each tier is reported as drops/xrp (XRPL) and usdc/usdc_micro (Solana). The legacy "tourism" key is retained as a deprecated alias for "standard" (both resolve to the standard tier: 1000000 drops / 1 XRP, or $1.00 USDC) for backward compatibility. Prefer "standard". Will be removed in MCP API v2.

NameTypeReqDescription
slugstring––

No output schema declared.

No examples provided.

xrplme_get_survey_questions ~25

Get survey questions for AI agents to provide feedback. FREE.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

xrplme_get_survey_stats ~24

Get aggregated survey statistics from all AI agents. FREE.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

xrplme_list_countries ~20

List the 90 countries. FREE.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

xrplme_submit_survey ~194

Submit survey feedback from an AI agent. FREE (we pay you for testing!). Args: agent_id: Your AI agent identifier country_slug: Country you tested (e.g., "thailand") data_quality: Rating 1-5 completeness: Rating 1-5 pricing_fair: "yes", "no", or "depends_on_country" would_pay_again: "yes", "no", or "maybe" broken_fields: Text description of any broken fields improvements: Text suggestions for improvements

NameTypeReqDescription
agent_idstringyes–
broken_fieldsstring––
completenessstring––
country_slugstringyes–
data_qualitystring––
improvementsstring––
pricing_fairstring––
would_pay_againstring––

No output schema declared.

No examples provided.

Install

How do I install the XRPLME Country Intelligence MCP server?

XRPLME Country Intelligence is a hosted endpoint at https://api.xrplme.online/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 · api.xrplme.online

# add to Claude Code
claude mcp add --transport http daimyovegan-xrplme-paid 'https://api.xrplme.online/mcp'
Common questions

What is the XRPLME Country Intelligence MCP server?

XRPLME Country Intelligence is an MCP server listed in the public MCP registry as io.github.DaimyoVegan/xrplme-paid. Source-backed country policy data for AI agents; pay-per-call via x402 (XRP or USDC). This page covers its hosted endpoint (https://api.xrplme.online/mcp).

Is the XRPLME Country Intelligence MCP server safe to use?

XRPLME Country Intelligence scores 72 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 XRPLME Country Intelligence MCP server expose?

XRPLME Country Intelligence exposes 8 tools: xrplme_list_countries, xrplme_get_country_status, xrplme_get_pricing, xrplme_get_country_data, xrplme_get_country_schema, and 3 more. Their descriptions and schemas cost roughly 855 tokens of context every time the server is loaded.

Does the XRPLME Country Intelligence MCP server require authentication?

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

Is the XRPLME Country Intelligence MCP server still maintained?

XRPLME Country Intelligence 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.