
Brük MCP server
Which MCP servers are Brük's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-27
- Registry namecom.brukledger/brukverified in the MCP registry
The registry name sits under brukledger.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-27
- Tools14
- Server calls itselfbruk
- Server version0.12.9
- Protocol version2025-06-18
On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 143 ms.
- Whether its tools do the product's job has not been judged yet.
Once connected
- For "spot the largest single XRP payments as they happen", the likely first call is large_payments.
- Parameters are untyped or undescribed in 8 of 14 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score92 of 100answers 86 · definitions 90 · context 100 · connects 100
- Answered86% of days6 of 7 daily checks
- Median first answer165 ms
- Space in an agent's context≈ 2,758 tokensthe definitions of all its tools (14), which an agent carries on every turn
- Tool definitionsA · 90 of 100
- Typed results0 of 14 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 8 of 14
What an agent can do with it
- not sure · watch live XRP Ledger payments settle in real time
- can do · spot the largest single XRP payments as they happen
- not sure · view real validator locations across a globe
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
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 ledger read. Useful before submitting XRP Ledger transactions…
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 partial-payment tricks. Useful when confirming that a…
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 outstanding, and control flags such as freeze, clawback…
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). Reports the type, issuer domain check, supply, and controls that can freeze, lock…
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 the window is not fully covered. Useful for market and…
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 opt-in and issuer approval), is blackholed, and whether the…
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), or a watch.expired event if none arrives. Payments that…
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 time, result, optional expectation checks, and a QR code to…
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, other), failed transactions hollow, with counts, fees…
list_servicesFree. Lists every Brük service with price, inputs, and its HTTP endpoint.
get_sampleFree. Returns a recent real answer from a Brük service (cached up to 5 minutes) so you can see the format before paying.
free_send_checkFree, 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…
token_typesFree 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.
learn_about_brukFree. Brük's site, its short film about the XRP Ledger (chapters, transcript, captions), and the credit line for quoting it.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"bruk": {
"type": "http",
"url": "https://bruk-agent-api.fly.dev/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http brukledger https://bruk-agent-api.fly.dev/mcpclaude.ai, ChatGPT and other clients: add https://bruk-agent-api.fly.dev/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.