Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Tools
steward_catalog
List everything buyable from Brian Booms — ambient music, ringtones, wallpapers, track leases, game licenses, commissions. Returns sku, name, and USD price per product. Start any purchase flow here, then use steward_product for details on one item or steward_purchase_instructions for its live payment requirements. This lists WHAT Brian Booms sells; for the merchant directory (who sells) see stewar
ArgumentsA call is made on an account: it counts against an allowance and the publisher sees it, which is why this one asks who you are first.
99/100
trust score
30
downloads a day
remote
via our gateway
2k
downloads in 30d
What it does
Brian Booms x402 product catalog as agent tools. Read-only.
Quickstart
# 1 — sign in once: npx mcprush@latest login
# it asks for a key from mcprush.com/dashboard#access
# 2 — install
npx mcprush@latest add brianbooms/brian-booms-mcp
# 3 — the plan is chosen at checkout, in the browser
# 4 — ask your agent for something these tools do
# steward_catalog, steward_product, steward_purchase_instructions and 8 more
Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither.
You are on the Taste tier: 500 calls a month, and call 501 returns a normal MCP error rather than an invoice.
PublisherVerified · since 2026
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 — this server runs on the publisher’s own infrastructure behind our gateway, and what you install is the connection to it.
Claude Codedeclared by this listing
Claude Code has its own MCP command, and the key rides on it as a header — the gateway refuses a call that carries none. Claude Code reads MCPRUSH_KEY each time it connects, so the key stays out of its config: export your key from Access in your shell profile (macOS, Linux), or run setx MCPRUSH_KEY <your key> and open a new terminal (Windows). Or let npx mcprush@latest add brianbooms/brian-booms-mcp write the entry with the key for you; --scope user makes it available in every project.
claude mcp add --transport http --scope user brian-booms-mcp https://mcprush.com/gw/brian-booms-mcp/mcp --header 'Authorization: Bearer ${MCPRUSH_KEY}'Reconnect, or start a new session, and the tools appear in the model’s tool list.
This is a paid listing: the gateway answers only a key of an account whose subscription to it is active — how the login works. Until then add writes nothing: signed out, it names the price and the checkout link; signed in, it prints the checkout link, or why the subscription is held (ended, paused, an unpaid invoice) and the link that lifts it. The gateway refuses every call the same way, and most clients only show the server as failed.
What it writes
One config entry pointing at the gateway. The server itself runs on the publisher’s own infrastructure, so nothing from this listing executes on your machine.
What you approve
11 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.
List everything buyable from Brian Booms — ambient music, ringtones, wallpapers, track leases, game licenses, commissions. Returns sku, name, and USD price per product. Start any purchase flow here, then use steward_product for details on one item or steward_purchase_instructions for its live payment requirements. This lists WHAT Brian Booms sells; for the merchant directory (who sells) see stewar
No parameter schema on file.
Full details for one catalog product: description, USD price, delivery method, and buy URL. Use after steward_catalog to zoom in on a single sku; when ready to pay, call steward_purchase_instructions for the live x402 quote. Free, read-only — never signs or spends.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sku | string | yes | Product sku exactly as returned by steward_catalog (e.g. 'data-affirmation'). |
Exact x402 payment requirements for buying a product: pay-to address, amount, asset, network, and facilitator — parsed live from the product's 402 response. Find the sku with steward_catalog first. Your agent pays with its own x402/EVM wallet, then downloads instantly. Free, read-only (reads the 402, never pays it).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sku | string | yes | Product sku exactly as returned by steward_catalog (e.g. 'data-affirmation'). |
How Booms Rewards works: earn rates for buyers, referral rates, and how a store joins free. Read this before buying through steward_purchase_instructions so you know the credit you'll earn, or before enrolling a store as a merchant. Free, read-only — never signs or spends.
No parameter schema on file.
Byte-exact guide to constructing a valid X-PAYMENT header for x402 v1 (EVM, USDC on Base). Call this BEFORE an agent's first self-paid purchase via steward_purchase_instructions — most failed payments are header-format errors this guide prevents. Free, read-only — never signs or spends.
No parameter schema on file.
Cheapest of 6 crypto transfer routes for a USD amount — USDC on Base, Solana, Polygon, Arbitrum, Avalanche C-chain, and BTC — ranked with live fee data. Returns the ranked list plus the single cheapest route. Use this for a quick answer; use steward_route_fees for the full fee table. Advisory only: neutral ranking, no wallet, no custody, moves nothing. Free, read-only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| amount_usd | number | yes | Transfer amount in USD, 1-100000 (e.g. 250). |
| token | string | no | Optional: restrict to one token — 'USDC' or 'BTC'. Omit to compare all routes. |
Full ranked fee table for all 6 crypto transfer routes (USDC on Base, Solana, Polygon, Arbitrum, Avalanche C-chain, and BTC) for a USD amount. Each route carries fee_usd, total_usd, and fee_source (live or typical) verbatim from the API. Use this for the complete comparison; use steward_cheapest_route when you only need the winner. Advisory only: neutral ranking, no wallet, no custody, moves nothi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| amount_usd | number | yes | Transfer amount in USD, 1-100000 (e.g. 250). |
| token | string | no | Optional: restrict to one token — 'USDC' or 'BTC'. Omit to compare all routes. |
Public per-wallet receipts for settled Steward calls — look up any EVM wallet and see every cent it paid, in the open. Use this to verify a payment actually settled. This is on-rail history and the source of truth for settled spend. Free, read-only — never signs or spends.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet | string | yes | EVM wallet address to look up, 0x-prefixed 40-hex chars (e.g. 0xa98e8c6cbc64b7bb30fd0d2015ab24814c661839). |
Steward Verified issuer's Ed25519 public key (hex) — independently verify any Steward Verified record's signature offline: the signature covers the canonical record (sorted keys, no whitespace, UTF-8) with signing_pubkey blanked. Free, read-only — never signs or spends.
No parameter schema on file.
The Steward Standard merchant directory: x402 merchants ranked by public merit score — liveness, volume, docs, endpoints, breadth, trust. Ranking is never for sale: no pay-to-rank, no sponsored slots, no partner override. This lists WHO sells (merchants); for WHAT Brian Booms sells use steward_catalog. Returns the full machine-readable directory. Free, read-only — never signs or spends.
No parameter schema on file.
This endpoint's spend meter. The hosted McPrush endpoint exposes free read-only tools only and holds no payer key, so it never spends: the meter is always 0 here. For settled-spend history use steward_receipts (the source of truth). Free, no rail call.
No parameter schema on file.
Free trialfree to start
$0 for 14 days
- The full Builder plan for 14 days
- 5,000 calls a month, included
- Nothing is charged inside the trial
- A card goes on file, and is only charged when it ends
- Becomes Builder on day 15 unless cancelled
Taste
$0 / month · free tier
- 500 calls a month, included
- 10 calls a minute at peak
- Every tool the listing has
- No card needed — call 501 returns a limit error rather than a bill
- Upgrade at any point, prorated to the day
Builder
$9 / month
- 5,000 calls a month, included
- No rate limit
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Pro
$29 / month
- 25,000 calls a month, included
- No rate limit
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against the 500 calls a month on Taste
| Tool | Unit | Calls used | Out of the monthly allowance |
|---|---|---|---|
| steward_catalog | call | 1 | 0.2000% |
| steward_product | call | 1 | 0.2000% |
| steward_purchase_instructions | call | 1 | 0.2000% |
| steward_rewards | call | 1 | 0.2000% |
| steward_payment_format | call | 1 | 0.2000% |
| steward_cheapest_route | call | 1 | 0.2000% |
| steward_route_fees | call | 1 | 0.2000% |
| steward_receipts | call | 1 | 0.2000% |
Failed calls, timeouts and anything the gateway rejects never count. When the allowance runs out the gateway returns an error naming the plan limit — nothing is billed beyond the subscription, ever.
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: —
ATrust score 99 / 100
Release 1.1.1 · scanned 14 Oct 2026
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 score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digestf29bb6a920c81c1ec71a1bc67157ecdde663b1b2a9371d1f394c125129e46ea4
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (5 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| catalog | no tags | |
| product | no tags | |
| purchase_instructions | no tags | |
| rewards | no tags | |
| payment_format | 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.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestf29bb6a920c81c1e
Scanned2026-10-14
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
The gateway serves every install the publisher’s current release, so a release cannot be pinned or rolled back to here yet. The history below is for reading; the current release on file is 1.1.1.
1.1.1
4 Oct 2026
latestNo release note was published with this version.
1.0.7
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
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 Brian Booms 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.