Brük — verified XRP Ledger answers
REMOTE · BRUK-AGENT-API.FLY.DEV
Verified XRP Ledger answers with proof: payment, send, and issuer checks. Pay per call via x402.
Available components
Last scanned (1 hour ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2052 tokens (~146/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_check" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
- Server version: 0.12.9 → 0.12.10 functional
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
- Injection markers: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.27 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Server version: 0.12.8 → 0.12.9 functional
- 25 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.20 → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://bruk-agent-api.fly.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.fly.dev | CN=YE1,O=Let's Encrypt,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5e6e25e6df778e81cd07b85fc9f12d4df7d |
| SANs: *.fly.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bruk-agent-api.fly.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| fly.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bruk-agent-api.fly.dev/mcp | Verified | 200 | |
| http (plaintext) | http://bruk-agent-api.fly.dev/mcp | HTTPS enforced | 301 | https://bruk-agent-api.fly.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
free_send_check Free daily send check ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | – |
| currency | string | – | – |
| destination | string | yes | XRP Ledger r-address |
| destination_tag | integer | – | – |
| issuer | string | – | XRP Ledger r-address |
| network | string | – | Default mainnet |
| source | string | – | XRP Ledger r-address |
No output schema declared.
No examples provided.
get_sample Free sample ~44
Free. Returns a recent real answer from a Brük service (cached up to 5 minutes) so you can see the format before paying.
| Name | Type | Req | Description |
|---|---|---|---|
| service | string | yes | – |
No output schema declared.
No examples provided.
issuer_check Issuer Check ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | XRP Ledger r-address |
No output schema declared.
No examples provided.
large_payments Large Payments ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| min_value | string | – | At least 50000 |
| minutes | integer | – | – |
No output schema declared.
No examples provided.
learn_about_bruk About Brük ~40
Free. Brük's site, its short film about the XRP Ledger (chapters, transcript, captions), and the credit line for quoting it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ledger_moment Ledger Moment ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ledger_index | integer | – | – |
| network | string | – | Default mainnet |
No output schema declared.
No examples provided.
ledger_pulse Ledger Pulse ~117
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_services List Brük services ~25
Free. Lists every Brük service with price, inputs, and its HTTP endpoint.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
payment_check Payment Check ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | – |
| currency | string | – | – |
| destination | string | – | XRP Ledger r-address |
| destination_tag | integer | – | – |
| issuer | string | – | XRP Ledger r-address |
| network | string | – | Default mainnet |
| tx | string | yes | 64-character transaction hash |
No output schema declared.
No examples provided.
payment_watch Payment Watch ~208
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | XRP Ledger r-address |
| currency | string | – | – |
| destination_tag | integer | – | – |
| hours | integer | – | – |
| issuer | string | – | XRP Ledger r-address |
| min_amount | string | – | – |
| network | string | – | Default mainnet |
| webhook | string | yes | Public https URL for signed events |
No output schema declared.
No examples provided.
receipt_card Receipt Card ~213
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | – |
| currency | string | – | – |
| destination | string | – | XRP Ledger r-address |
| destination_tag | integer | – | – |
| issuer | string | – | XRP Ledger r-address |
| network | string | – | Default mainnet |
| tx | string | yes | 64-character transaction hash |
No output schema declared.
No examples provided.
send_check Send Check ~260
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | – |
| currency | string | – | – |
| destination | string | yes | XRP Ledger r-address |
| destination_tag | integer | – | – |
| issuer | string | – | XRP Ledger r-address |
| mpt_issuance_id | string | – | 48-hex MPT issuance id. Use instead of currency and issuer. |
| network | string | – | Default mainnet |
| source | string | – | XRP Ledger r-address |
No output schema declared.
No examples provided.
token_check Token Check ~231
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Trust-line token code, with issuer. Not XRP. |
| issuer | string | – | XRP Ledger r-address |
| mpt_issuance_id | string | – | 48-hex multi-purpose token issuance id. Use this or currency plus issuer, not both. |
No output schema declared.
No examples provided.
token_types Token types ~45
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Brük — verified XRP Ledger answers MCP server?
Brük — verified XRP Ledger answers is a hosted endpoint at https://bruk-agent-api.fly.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · bruk-agent-api.fly.dev
claude mcp add --transport http com-brukledger-bruk 'https://bruk-agent-api.fly.dev/mcp'
What is the Brük — verified XRP Ledger answers MCP server?
Brük — verified XRP Ledger answers is an MCP server listed in the public MCP registry as com.brukledger/bruk. Verified XRP Ledger answers with proof: payment, send, and issuer checks. Pay per call via x402. This page covers its hosted endpoint (https://bruk-agent-api.fly.dev/mcp).
Is the Brük — verified XRP Ledger answers MCP server safe to use?
Brük — verified XRP Ledger answers scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Brük — verified XRP Ledger answers MCP server expose?
Brük — verified XRP Ledger answers exposes 14 tools: ledger_pulse, payment_check, issuer_check, token_check, large_payments, and 9 more. Their descriptions and schemas cost roughly 1,972 tokens of context every time the server is loaded.
Does the Brük — verified XRP Ledger answers MCP server require authentication?
No. We connected to Brük — verified XRP Ledger answers without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Brük — verified XRP Ledger answers MCP server still maintained?
Brük — verified XRP Ledger answers is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.