API Tools
brukledger.com
Provides XRP Ledger API tools for checking network health, verifying payments and issuers, listing large payments, and validating payment destinations before sending.
ENDPOINT 1
https://bruk-agent-api.fly.dev/mcp
MCP server metadata
- Name
- bruk
- Version
- 0.9.0
Verified XRP Ledger answers with proof. Free tools: list_services, get_sample, learn_about_bruk. Paid tools use x402: call once without payment to receive the payment requirements, then retry with params._meta['x402/payment'].
Known tools 9
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.
Inferred read-onlypayment_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.
Potential side effectsissuer_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.
Inferred read-onlylarge_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.
Inferred read-onlysend_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, limit, freeze, issuer approval), is blackholed, and whether the source can afford it.
Potential side effectspayment_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.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.bruk]
url = "https://bruk-agent-api.fly.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"bruk": {
"type": "http",
"url": "https://bruk-agent-api.fly.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: bruk
Remote MCP URL: https://bruk-agent-api.fly.dev/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"bruk": {
"url": "https://bruk-agent-api.fly.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"bruk": {
"type": "http",
"url": "https://bruk-agent-api.fly.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "bruk",
"transport": "streamable-http",
"url": "https://bruk-agent-api.fly.dev/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for fly.dev was fetched 2026-09-26T18:35:49.496Z.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.