Skip to content

Brük — verified XRP Ledger answers MCP server

com.brukledger/brukbrukledger.comstreamable-httpv0.8.0Scanned

Verified XRP Ledger answers with proof: payment, send, and issuer checks. Pay per call via x402.

14 tools: 6 do something that can't be undone, 6 change things and 2 only read.

Tools: 0 delete, 6 irreversible, 6 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 11
  • Can send data out · 3
  • 6 findings

Tools listed without sign-in. Remote posture

With Anlyon

6 tools here do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Brük — verified XRP Ledger answers MCP server can do

The Brük — verified XRP Ledger answers MCP server is published by brukledger.com, a domain the MCP Registry verified. It has 14 tools. It can do things that cannot be undone, such as sending, paying or publishing (payment_check, large_payments, send_check, payment_watch and 2 more) and create or change data (6 tools: ledger_pulse, issuer_check, token_check, ledger_moment and 2 more), but cannot delete data. 2 tools only read.

11 tools bring in text other people can write (ledger_pulse, payment_check, issuer_check and 8 more); 3 tools can send data out of your system (send_check, payment_watch and free_send_check).

The fixed checks matched 6 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 12, 2026, version 0.8.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

14 tools

Can't be undone 6Claude Code: ask
  • free_send_checkFree, one per user per day.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "free_send_check" says "send": a word for sending, and what is sent cannot be taken back.
    • The input carries an amount (input.amount) and a currency, so it moves money.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "free_send_check" says "send": it sends or publishes something to other people.

    Findings

    • Warn

      The server marks "free_send_check" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "free_send_check" says "send": a word for sending, and what is sent cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Free, one per user per day. Before sending XRP or a token on the XRP Ledger: will the payment fail (missing destination tag, unfunded or deleted account, no trust line, wrong issuer) and what should you double-check? Returns the verdict, blockers, and cautions from a validated ledger. The paid send_check adds the full evidence and has no daily limit.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • large_paymentsLists large XRP Ledger payments (50,000+ XRP or major stablecoins) in a recent window of up to 120 minutes, each independently re-checked on the ledger, with an explicit note when …Reads text others write1 finding

    Why it is in this group

    • The name "large_payments" says "payment": a word that usually means money moves, which cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "large_payments" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "large_payments" says "payment": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Lists large XRP Ledger payments (50,000+ XRP or major stablecoins) in a recent window of up to 120 minutes, each independently re-checked on the ledger, with an explicit note when the window is not fully covered. Useful for market and liquidity monitoring. The first call each day returns the real answer without payment. After that, about $0.02 via x402 (USDC on Base, or XRP / RLUSD on the XRP Ledger). A payment watch is paid from the first call. Bad input and ledger outages are never charged.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • payment_checkVerifies that an XRP Ledger payment settled as expected: validation, result code, destination, destination tag, currency, issuer, and the amount actually delivered, which exposes p…Reads text others write1 finding

    Why it is in this group

    • The name "payment_check" says "payment": a word that usually means money moves, which cannot be taken back.
    • The input carries an amount (input.amount) and a currency, so it moves money.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "payment_check" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "payment_check" says "payment": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Verifies that an XRP Ledger payment settled as expected: validation, result code, destination, destination tag, currency, issuer, and the amount actually delivered, which exposes partial-payment tricks. Useful when confirming that a customer or counterparty really paid. The first call each day returns the real answer without payment. After that, about $0.01 via x402 (USDC on Base, or XRP / RLUSD on the XRP Ledger). A payment watch is paid from the first call. Bad input and ledger outages are never charged.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • payment_watchPayment arrival alert: watches an XRP Ledger address for up to 24 hours and POSTs a signed webhook when a matching payment is final (validated, tesSUCCESS, delivered amount checked…Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "payment_watch" says "payment": a word that usually means money moves, which cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.webhook): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Payment arrival alert: watches an XRP Ledger address for up to 24 hours and POSTs a signed webhook when a matching payment is final (validated, tesSUCCESS, delivered amount checked), or a watch.expired event if none arrives. Payments that land during restarts are still caught. Useful when waiting on an incoming payment without polling. The first call each day returns the real answer without payment. After that, about $0.05 via x402 (USDC on Base, or XRP / RLUSD on the XRP Ledger). A payment watch is paid from the first call. Bad input and ledger outages are never charged.

    Annotations the server declares

    • readOnlyHint: false
    • openWorldHint: true
  • receipt_cardVerified payment receipt image (1200x675 PNG) for an XRP Ledger payment, drawn only from the validated ledger: delivered amount, sender, recipient, destination tag, ledger, close t…Reads text others write1 finding

    Why it is in this group

    • The input carries an amount (input.amount) and a currency, so it moves money.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "receipt_card" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The input carries an amount (input.amount) and a currency, so it moves money.

      What this check looks for
    Description, as the server wrote it
    Verified payment receipt image (1200x675 PNG) for an XRP Ledger payment, drawn only from the validated ledger: delivered amount, sender, recipient, destination tag, ledger, close time, result, optional expectation checks, and a QR code to the public explorer. Only final outcomes are drawn; not-found or unvalidated transactions are not charged. Useful for showing a person proof that a payment arrived. The first call each day returns the real answer without payment. After that, about $0.02 via x402 (USDC on Base, or XRP / RLUSD on the XRP Ledger). A payment watch is paid from the first call. Bad input and ledger outages are never charged.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • send_checkPre-send check for an XRP Ledger payment: whether the destination is activated, requires a destination tag, blocks or pre-approves senders, can hold the token (trust line, or MPT o…Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "send_check" says "send": a word for sending, and what is sent cannot be taken back.
    • The description says "irreversible".
    • The input carries an amount (input.amount) and a currency, so it moves money.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "send_check" says "send": it sends or publishes something to other people.

    Findings

    • Warn

      The server marks "send_check" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "send_check" says "send": a word for sending, and what is sent cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Pre-send check for an XRP Ledger payment: whether the destination is activated, requires a destination tag, blocks or pre-approves senders, can hold the token (trust line, or MPT opt-in and issuer approval), is blackholed, and whether the source can afford it. For a multi-purpose token, pass mpt_issuance_id instead of currency and issuer. Returns ok_to_send, send_with_caution, or will_fail with reasons. Useful before any irreversible XRP Ledger payment. The first call each day returns the real answer without payment. After that, about $0.005 via x402 (USDC on Base, or XRP / RLUSD on the XRP Ledger). A payment watch is paid from the first call. Bad input and ledger outages are never charged.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
Changes things 6Claude Code: ask
  • issuer_checkChecks whether an XRP Ledger token issuer is who it claims to be: two-way domain verification (on-ledger Domain field against the domain's xrp-ledger.toml), tokens issued and outst…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Checks whether an XRP Ledger token issuer is who it claims to be: two-way domain verification (on-ledger Domain field against the domain's xrp-ledger.toml), tokens issued and outstanding, and control flags such as freeze, clawback, blackholed, and multisign. Useful before accepting or holding a token. The first call each day returns the real answer without payment. After that, about $0.01 via x402 (USDC on Base, or XRP / RLUSD on the XRP Ledger). A payment watch is paid from the first call. Bad input and ledger outages are never charged.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • learn_about_brukFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free. Brük's site, its short film about the XRP Ledger (chapters, transcript, captions), and the credit line for quoting it.

    Annotations the server declares

    • readOnlyHint: true
  • ledger_momentLedger moment image (1200x675 PNG): one validated XRP Ledger ledger drawn as one tile per transaction in ledger order, colored by type (payments, DEX offers, trust lines, AMM, NFTs…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Ledger moment image (1200x675 PNG): one validated XRP Ledger ledger drawn as one tile per transaction in ledger order, colored by type (payments, DEX offers, trust lines, AMM, NFTs, other), failed transactions hollow, with counts, fees burned, XRP supply, and the ledger hash. Latest validated ledger by default. Useful for posts, reports, and newsletters about network activity. The first call each day returns the real answer without payment. After that, about $0.02 via x402 (USDC on Base, or XRP / RLUSD on the XRP Ledger). A payment watch is paid from the first call. Bad input and ledger outages are never charged.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • ledger_pulseXRP Ledger network health right now: latest validated ledger, close time, transactions and payments in it, fee levels, load, and rolling averages cross-checked against a direct led…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    XRP Ledger network health right now: latest validated ledger, close time, transactions and payments in it, fee levels, load, and rolling averages cross-checked against a direct ledger read. Useful before submitting XRP Ledger transactions or when reporting current network conditions. The first call each day returns the real answer without payment. After that, about $0.001 via x402 (USDC on Base, or XRP / RLUSD on the XRP Ledger). A payment watch is paid from the first call. Bad input and ledger outages are never charged.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • token_checkIdentifies one XRP Ledger token from the validated ledger: a trust-line token (currency code plus issuer) or a multi-purpose token (48-hex issuance id).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Identifies one XRP Ledger token from the validated ledger: a trust-line token (currency code plus issuer) or a multi-purpose token (48-hex issuance id). Reports the type, issuer domain check, supply, and controls that can freeze, lock, claw back, or restrict holders. Issuer-written metadata is quoted and is not treated as fact; a missing asset class is reported missing. Does not check other chains, and does not rate legal backing or solvency. Useful before accepting an MPT or any other token. The first call each day returns the real answer without payment. After that, about $0.01 via x402 (USDC on Base, or XRP / RLUSD on the XRP Ledger). A payment watch is paid from the first call. Bad input and ledger outages are never charged.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • token_typesFree guide, not a live check.1 finding

    Why it is in this group

    • The name "token_types" says "type": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "token_types" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "token_types" says "type": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Free guide, not a live check. Which XRP Ledger token types Brük can identify, how to pass an MPT issuance id, and which other chains Brük does not read.

    Annotations the server declares

    • readOnlyHint: true
Only reads 2Show 2 read-only tools
  • get_sampleFree.Reads text others writeNo findings

    Why it is in this group

    • The name "get_sample" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Free. Returns a recent real answer from a Brük service (cached up to 5 minutes) so you can see the format before paying.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • list_servicesFree.No findings

    Why it is in this group

    • The name "list_services" says "list": a word for reading.
    Description, as the server wrote it
    Free. Lists every Brük service with price, inputs, and its HTTP endpoint.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write11
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:35 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
12
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 12 tools that change things (6 irreversible, 6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://bruk-agent-api.fly.dev/mcp: tools/list returned 14 tools to an anonymous client, including payment_check (irreversible), large_payments (irreversible), send_check (irreversible), payment_watch (irreversible), receipt_card (irreversible) and 7 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

6 warn
  • The server marks "payment_check" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "payment_check" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "large_payments" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "large_payments" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "send_check" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "send_check" says "send": a word for sending, and what is sent cannot be taken back.

    What this check looks for
  • The server marks "receipt_card" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The input carries an amount (input.amount) and a currency, so it moves money.

    What this check looks for
  • The server marks "free_send_check" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "free_send_check" says "send": a word for sending, and what is sent cannot be taken back.

    What this check looks for
  • The server marks "token_types" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "token_types" says "type": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.8.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http bruk https://bruk-agent-api.fly.dev/mcp
claude mcp add --transport http bruk https://bruk-agent-api.fly.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__bruk__list_services",
      "mcp__bruk__get_sample"
    ],
    "ask": [
      "mcp__bruk__ledger_pulse",
      "mcp__bruk__payment_check",
      "mcp__bruk__issuer_check",
      "mcp__bruk__token_check",
      "mcp__bruk__large_payments",
      "mcp__bruk__send_check",
      "mcp__bruk__payment_watch",
      "mcp__bruk__receipt_card",
      "mcp__bruk__ledger_moment",
      "mcp__bruk__free_send_check",
      "mcp__bruk__token_types",
      "mcp__bruk__learn_about_bruk"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bruk. Review it before you use it.

Capability tags behind 11 rules
  • mcp__bruk__ledger_pulse untrusted-input
  • mcp__bruk__payment_check untrusted-input
  • mcp__bruk__issuer_check untrusted-input
  • mcp__bruk__token_check untrusted-input
  • mcp__bruk__large_payments untrusted-input
  • mcp__bruk__send_check untrusted-input, outbound
  • mcp__bruk__payment_watch untrusted-input, outbound
  • mcp__bruk__receipt_card untrusted-input
  • mcp__bruk__ledger_moment untrusted-input
  • mcp__bruk__get_sample untrusted-input
  • mcp__bruk__free_send_check untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.brukledger/bruk/verify?hash=3dc1c4d08d2c5c52d02b68969c0842e1e54c8e78d2ace8588ea52d8953fcfc69" | jq -e '.changed == false'

Pinned hash 3dc1c4d08d2c, from Nov 12, 2026, 19:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.brukledger/bruk/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.brukledger/bruk
[![Anlyon Radar](https://radar.anlyon.com/badge/com.brukledger/bruk.svg)](https://radar.anlyon.com/servers/com.brukledger/bruk)

Source: MCP Registry. Synced Oct 21, 2026, 17:52 UTC.

Brük — verified XRP Ledger answers MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Brük — verified XRP Ledger answers MCP server safe?

No scan can promise that. What its definitions show: 14 tools, 12 of which can change, send or delete something, and 6 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Brük — verified XRP Ledger answers MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Brük — verified XRP Ledger answers MCP server do things that cannot be undone?

Yes. 6 tools can send, pay, publish or merge: payment_check, large_payments, send_check, payment_watch, receipt_card and free_send_check.

What tools does the Brük — verified XRP Ledger answers MCP server have?

14 tools: 6 irreversible, 6 write, 2 read. payment_check, large_payments, send_check, payment_watch, receipt_card, free_send_check, ledger_pulse, issuer_check and 6 more.

Does the Brük — verified XRP Ledger answers MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Brük — verified XRP Ledger answers MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_check, payment_watch and free_send_check.

Has the Brük — verified XRP Ledger answers MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.