Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Brük — verified XRP Ledger answers is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
14
tools declared
remote
at its publisher
—
calls last 7d
What it does
Verified XRP Ledger answers with proof: payment, send, and issuer checks. Pay per call via x402.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http bruk-verified-xrp-ledger-answers-mcp https://bruk-agent-api.fly.dev/mcp
# 2 — ask your agent for something these tools do
# ledger_pulse, payment_check, issuer_check and 11 more
Brük — verified XRP Ledger answers costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BRAll 1 server
brukledger1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http bruk-verified-xrp-ledger-answers-mcp https://bruk-agent-api.fly.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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. Price about $0.001 per call via x402 (USDC on Base, or XRP / RLUSD on the XRP Ledger). Without a payment the tool r
No parameter schema on file.
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. Price about $0.01 per call via x402 (USDC on Base, or XRP / RLUSD on the XRP Ledger). Without a payment the tool returns the x402
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tx | string | yes | 64-character transaction hash |
| network | string | no | Default mainnet |
| destination | string | no | XRP Ledger r-address |
| amount | string | no | — |
| currency | string | no | — |
| issuer | string | no | XRP Ledger r-address |
| destination_tag | integer | no | — |
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. Price about $0.01 per call via x402 (USDC on Base, or XRP / RLUSD on the XRP Ledger). Without a p
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account | string | yes | XRP Ledger r-address |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mpt_issuance_id | string | no | 48-hex multi-purpose token issuance id. Use this or currency plus issuer, not both. |
| currency | string | no | Trust-line token code, with issuer. Not XRP. |
| issuer | string | no | XRP Ledger r-address |
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. Price about $0.02 per call via x402 (USDC on Base, or XRP / RLUSD on the XRP Ledger). Without a payment the tool returns the x402 payment requi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| minutes | integer | no | — |
| min_value | string | no | At least 50000 |
| limit | integer | no | — |
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 re
| Parameter | Type | Required | Notes |
|---|---|---|---|
| destination | string | yes | XRP Ledger r-address |
| amount | string | no | — |
| currency | string | no | — |
| issuer | string | no | XRP Ledger r-address |
| destination_tag | integer | no | — |
| source | string | no | XRP Ledger r-address |
| network | string | no | Default mainnet |
| mpt_issuance_id | string | no | 48-hex MPT issuance id. Use instead of currency and issuer. |
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. Price about $0.05 per call via x402 (USDC on Base, or XRP / RL
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | XRP Ledger r-address |
| webhook | string | yes | Public https URL for signed events |
| destination_tag | integer | no | — |
| min_amount | string | no | — |
| currency | string | no | — |
| issuer | string | no | XRP Ledger r-address |
| hours | integer | no | — |
| network | string | no | Default mainnet |
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 arriv
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tx | string | yes | 64-character transaction hash |
| network | string | no | Default mainnet |
| destination | string | no | XRP Ledger r-address |
| amount | string | no | — |
| currency | string | no | — |
| issuer | string | no | XRP Ledger r-address |
| destination_tag | integer | no | — |
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. Price about $0.02 pe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ledger_index | integer | no | — |
| network | string | no | Default mainnet |
Free. Lists every Brük service with price, inputs, and its HTTP endpoint.
No parameter schema on file.
Free. Returns a recent real answer from a Brük service (cached up to 5 minutes) so you can see the format before paying.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| destination | string | yes | XRP Ledger r-address |
| amount | string | no | — |
| currency | string | no | — |
| issuer | string | no | XRP Ledger r-address |
| destination_tag | integer | no | — |
| source | string | no | XRP Ledger r-address |
| network | string | no | Default mainnet |
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.
No parameter schema on file.
Free. Brük's site, its short film about the XRP Ledger (chapters, transcript, captions), and the credit line for quoting it.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Brük — verified XRP Ledger answers or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 0.8.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestc6436bb8155228562609e713c65b54fb86d63a2322f10933d5eb34ab15d1b79e
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| ledger_pulse | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| payment_check | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| issuer_check | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| token_check | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| large_payments | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| send_check | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| payment_watch | external-sink | external-sink: keyword "webhook", parameter "webhook", declares readOnlyHint: false, openWorldHint: true |
| receipt_card | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ledger_moment | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_services | no tags | |
| get_sample | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| free_send_check | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| token_types | no tags | |
| learn_about_bruk | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digestc6436bb815522856
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.8.0.
0.8.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Brük — verified XRP Ledger answers can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.