_ registry / mcp streamable-http · checked 7h ago

xrplriskscore

https://xrplriskscore.ai

Registry code: 538e5cc86aad72d5

api record

AI-powered XRPL wallet risk scoring. Score any wallet before you move money — pay per call in XRP via x402. No API keys needed

from a public catalogue that lists it, not from the operator

endpoint
https://xrplriskscore.ai/mcp
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is xrplriskscore live?
Yes — it answered the hub's last check (checked 7h ago). It answered 100% of checks over the last 30 days.
Is xrplriskscore free to use?
Yes — the hub reached it with no key and no payment.
What tools does xrplriskscore have?
9 tools: check_xrpl_compliance_bundle, check_xrpl_escrow_counterparty, list_xrpl_risk_endpoints, check_xrpl_rwa_compliance, check_xrpl_credential_eligibility, provision_xrpl_wallet, check_xrpl_wallet_risk, quick_xrpl_prescore, ….
Is xrplriskscore safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
225ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 9 tools
9 never probed 0 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • check_xrpl_compliance_bundle unknown 7h ago

    Runs score + RWA + credential checks in parallel. Returns overall PASS/REVIEW/BLOCK verdict. Costs 3 XRP via x402.

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet"
  ],
  "properties": {
    "wallet": {
      "type": "string",
      "description": "XRPL wallet address"
    }
  }
}
    arguments 12 lines
  • check_xrpl_escrow_counterparty unknown 7h ago

    XLS-85 Token Escrow counterparty risk check for an XRPL wallet. Costs 0.5 XRP via x402.

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet"
  ],
  "properties": {
    "wallet": {
      "type": "string",
      "description": "XRPL wallet address"
    }
  }
}
    arguments 12 lines
  • list_xrpl_risk_endpoints unknown 7h ago

    Lists all available [xrplriskscore.ai](http://xrplriskscore.ai) endpoints with pricing and descriptions.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • check_xrpl_rwa_compliance unknown never probed

    RWA compliance check for XRPL wallets. Checks RLUSD, tokenized assets, escrow compliance. Costs 0.5 XRP via x402.

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet"
  ],
  "properties": {
    "wallet": {
      "type": "string",
      "description": "XRPL wallet address"
    }
  }
}
    arguments 12 lines
  • check_xrpl_credential_eligibility unknown never probed

    Checks XLS-80/81 Permissioned Domain credential eligibility for an XRPL wallet. Costs 0.5 XRP via x402.

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet"
  ],
  "properties": {
    "wallet": {
      "type": "string",
      "description": "XRPL wallet address"
    }
  }
}
    arguments 12 lines
  • provision_xrpl_wallet unknown never probed

    Generates a new XRPL keypair, funds it with 2 XRP from the service wallet, and returns a LOW_RISK baseline score. Costs 4 XRP via x402.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • check_xrpl_wallet_risk unknown never probed

    Full 31-signal risk score for any XRPL wallet address. Returns score 0-100, risk level, flags, and plain-English summary. Costs 1 XRP via x402.

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet"
  ],
  "properties": {
    "wallet": {
      "type": "string",
      "description": "XRPL wallet address"
    }
  }
}
    arguments 12 lines
  • quick_xrpl_prescore unknown never probed

    Fast 3-signal pre-score for any XRPL wallet. Returns verdict only. Costs 0.1 XRP via x402.

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet"
  ],
  "properties": {
    "wallet": {
      "type": "string",
      "description": "XRPL wallet address"
    }
  }
}
    arguments 12 lines
  • explain_xrpl_risk_score unknown never probed

    Plain-English explanation of what an XRPL risk score means and how signals are weighted.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 538e5cc86aad72d5.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/538e5cc86aad72d5/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/538e5cc86aad72d5/badge.svg)](https://brick.blue/agent/538e5cc86aad72d5?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.