XRPLME Country Intelligence — MCP Server
Source-backed economic and policy data for 30 countries, served over MCP and paid per call with x402 — settled in XRP or USDC.
No accounts, no API keys. The payment is the authentication.
Live endpoint: https://api.xrplme.online/mcp — Streamable HTTP transport.
What this repository is. It documents the hosted server: the endpoint, the tools, the prices, and how to connect. The server implementation itself is not open source and is not published here. Nothing in this repo is required to use the endpoint — you only need the URL.
Connect
Add the server to any MCP client that supports Streamable HTTP:
{
"mcpServers": {
"xrplme": {
"type": "http",
"url": "https://api.xrplme.online/mcp"
}
}
}
Then call xrplme_list_countries to see the coverage. It is free.
Tools
Eight tools are exposed. Six are free; two require payment.
| Tool | What it does | Cost |
|---|---|---|
xrplme_list_countries | List the 30 countries | Free |
xrplme_get_country_status | Live health probe for one country | Free |
xrplme_get_pricing | Current prices for both rails | Free |
xrplme_get_country_data | Latest data + freshness for one country | Paid |
xrplme_get_country_schema | Field schema for one country | Paid |
xrplme_get_survey_questions | Survey questions for AI agents | Free |
xrplme_submit_survey | Submit feedback | Free |
xrplme_get_survey_stats | Aggregated survey statistics | Free |
Prices
| Tier | XRP Ledger | Solana |
|---|---|---|
Standard (xrplme_get_country_schema) | 0.1 XRP | 1.0 USDC |
AI-enhanced (xrplme_get_country_data) | 0.5 XRP | 7.0 USDC |
xrplme_get_pricing always returns the live values — query it rather than
hard-coding these.
How payment works
- Call a paid tool with no payment. The server replies HTTP 402 with the exact amount, asset, recipient, and accepted networks. Nothing is charged and no data is returned.
- Pay on either rail:
- XRP Ledger — pass
X-PAYMENT-SIGNATURE+X-INV-IDheaders - Solana — pass
X-PAYMENT-SIGNATUREheader with a base64-encoded V2 payment payload containing the signed Solana transaction
- XRP Ledger — pass
- Call the tool again with the payment attached. On successful settlement the data is returned.
Payments are verified on-chain and are single-use — a replayed signature is rejected. Data is released only after settlement is confirmed, never before.
Networks
| Rail | Network |
|---|---|
| XRP Ledger | xrpl:0 (mainnet) |
| Solana | solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp (mainnet) |
Solana payments use native USDC
(EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v).
Solana payment details
Solana pays use the x402 exact payment scheme via a local facilitator
(http://127.0.0.1:8402). The 402 response includes a feePayer in the
extra field — this is the wallet that pays Solana transaction fees. Your
client must:
- Build a transaction with 3 instructions:
SetComputeUnitLimit,SetComputeUnitPrice, andTransferChecked(USDC, 6 decimals) - Set the
feePayerfrom the 402 response as the transaction fee payer - Partially sign the transaction with your wallet (which holds the USDC) — do not sign with the fee payer; the facilitator adds its signature
- Encode the partially-signed transaction as base64 and include it in a V2 payment payload:
{
"x402Version": 2,
"payload": {"transaction": "<base64-encoded signed tx>"},
"accepted": { /* from the 402 response's accepts[0] */ }
}
- Base64-encode the entire payload JSON and send it as the
X-PAYMENT-SIGNATUREheader on the retry request.
See xrplme-mcp-client/examples/x402_payment_solana.py
for a complete end-to-end example.
Registry
Listed in the official MCP Registry as
io.github.DaimyoVegan/xrplme-paid.
Related
- xrplme-mcp-client — client examples and working payment flows.
- Website / API docs: https://xrplme.online/api-docs.html
Notes
- Data is sourced from national statistics offices, central banks, and regulators. Each response carries its own freshness metadata; check it before relying on a figure.
- Coverage is 30 countries.
xrplme_list_countriesis the authoritative list.