Blackwall X402 Guardrail vs Xrpldashboard
A side-by-side look at the Blackwall X402 Guardrail and Xrpldashboard MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Blackwall X402 Guardrail for finance & fintech work over a hosted endpoint; choose Xrpldashboard for finance & fintech over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Blackwall X402 Guardrail when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
forecast_payment.
Choose Xrpldashboard when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
get_ledger_stats, get_amendment_status, get_unl_status.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 47/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 1 | 19 |
| Full listing | View Blackwall X402 Guardrail | View Xrpldashboard |
Tools & capabilities
Blackwall X402 Guardrail tools 1
forecast_paymentPre-signature x402 payment verdict: GO / HOLD / STOP for paying a counterparty, from settlement reputation, price-anomaly (quoted vs the payee's own median), and OFAC sanctions — with a third-party-verifiable Ed25519 signed receipt. Verdict only; never takes custody. Free under $10 at risk; over that, returns an x402 payment challenge.
Xrpldashboard tools 19
get_ledger_statsReturn the last-validated ledger stats (index, close time, server state, load factor, complete range, build). Wrapped in the xrpldashboard proof envelope; envelope source is derived from the actual URL host (`local_rippled` for loopback / private LAN, `remote_rippled:<host>` otherwise) — never hardcoded.get_amendment_statusReturn the current amendments state (enabled / in-flight / superseded / unrecognized-enabled) with `cross_check_status` derived from the responding node's feature-RPC vs Amendments ledger-object concurrence. Wrapped in the proof envelope.get_unl_statusReturn the current UNL composition (both published lists, overlap, expiry-days). Honest-partial when a list fetch fails. Wrapped in the proof envelope.get_whale_eventsReturn the last N XRP-denominated whale events + tagged-watchlist events (trustset excluded). Same feed the homepage globe pulse reads. Wrapped in the proof envelope.get_whale_watchlistReturn the last N tagged-watchlist events (type='tagged'), floored at TAGGED_XRP_FLOOR_DROPS for XRP-denominated rows. Wrapped in the proof envelope.get_rlusd_supplyReturn the current cross-chain RLUSD supply (Ethereum + XRPL) from the same PG mirror /rlusd reads. Honest-partial when either chain errored. Wrapped in the proof envelope.get_rlusd_flow_24hReturn the last finalized 24h XRPL net-change from rlusd_supply_history. freshness_contract='finalized_only' is the machine-readable form of the R1/R2 finalized-window rule. cross_check_status derived from stored vs supply-diff pair. Wrapped in the proof envelope.get_amm_poolReturn the single ranked-pool row for one AMM account from the amm_ranked_pools snapshot. Raises when the account is absent (unranked, below thresholds, or newer than the last snapshot). Wrapped in the proof envelope.get_amm_top_by_tvlReturn the top-N ranked AMM pools by tvl_usd from the same snapshot /pools reads. NULL-tvl rows sort last. Wrapped in the proof envelope.get_token_attestationReturn the attestation tier (verified / self-described / null) for one (currency, issuer) pair. Data payload includes `dispute_contact_url` — first tool to name a third party. Wrapped in the proof envelope.get_rwa_familiesReturn every rwa_family row with attributed pool count. Data payload includes `dispute_contact_url`. Wrapped in the proof envelope.get_rwa_poolsReturn every attributed RWA pool with provenance + TVL. Data payload includes `dispute_contact_url`. Wrapped in the proof envelope.- +7 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Blackwall X402 Guardrail
{
"mcpServers": {
"blackwall-x402-guardrail-2": {
"url": "https://mcp.blackwalltier.com"
}
}
}
Xrpldashboard
{
"mcpServers": {
"xrpldashboard": {
"url": "https://mcp.xrpldashboard.com/mcp?ref=readme"
}
}
}
Frequently asked questions
Blackwall X402 Guardrail is categorized under Finance & Fintech and uses a remote HTTP/SSE transport. Xrpldashboard belongs to Finance & Fintech and uses a remote HTTP/SSE transport. Pick Blackwall X402 Guardrail for finance & fintech work and Xrpldashboard for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Blackwall X402 Guardrail has no declared pricing — check the project's own site. Xrpldashboard has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add blackwall-x402-guardrail-2 and xrpldashboard as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Blackwall X402 Guardrail has a quality signal of 47/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Xrpldashboard has 57/100 (Good) with 3 views, 0 installs and 0 GitHub stars.