Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
BrewMan MCP by usefulapi 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.
What it does
Read orders, outlets, stock and purchase orders, and create or cancel orders in BrewMan.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http brewman-mcp-by-usefulapi https://brewman.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# brewman_get_current_user, brewman_list_outlets, brewman_get_outlet and 11 more
BrewMan MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 brewman-mcp-by-usefulapi https://brewman.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
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.
Return the BrewMan user that the Api-Token belongs to, with its tenant group id. Use it to confirm the connection. BrewMan API: POST /webapi/User/v1/GetCurrentUserContext.
No parameter schema on file.
List all outlets (customers: pubs, shops, accounts) in the tenant. Use the outlet ids with the order tools. BrewMan API: POST /webapi/Outlet/v1/GetAllOutlets.
No parameter schema on file.
Get one outlet by id, with its contact, address, price list and credit terms. BrewMan API: POST /webapi/Outlet/v1/GetOutlet.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| outlet_id | string | yes | The outlet id (from brewman_list_outlets). |
List full orders (header and lines) that match a filter. Dates are inclusive yyyy-mm-dd. Results can be large: set filter.maximumResults. BrewMan API: POST /webapi/Order/v2/GetOrdersByFilter.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filter | object | no | Order filter. All fields are optional. |
Get one order by id, with its header and lines. BrewMan API: POST /webapi/Order/v2/GetOrder.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | The order id (from brewman_list_orders). |
List items (products, materials, services) that match a filter. Use the item ids with stock and order tools. BrewMan API: POST /webapi/Item/v1/GetItemsByFilter.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filter | object | no | Item filter. All fields are optional. |
Get the current stock level (all batches summed) per stock item and stock location. Narrow it with the id lists. BrewMan API: POST /webapi/Stock/v1/GetStockItemsQuantityCurrentlyInStock.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stock_location_ids | array | no | Only these stock locations (from the stock location list). |
| stock_item_ids | array | no | Only these stock items (item ids). |
Get the known incoming and outgoing stock totals (on purchase orders, allocated to orders, in transfers) for items and locations. BrewMan API: POST /webapi/Stock/v1/GetStockIncomingOutgoing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stock_location_ids | array | no | Stock location ids to report on. |
| item_ids | array | no | Item ids to report on. |
List all price lists with their currency and whether they use gross pricing. Use the ids when you create an order. BrewMan API: POST /webapi/PriceList/v1/GetAllPriceLists.
No parameter schema on file.
List purchase orders that match a filter (status, supplier, dates). Dates are inclusive yyyy-mm-dd. BrewMan API: POST /webapi/PurchaseOrder/v1/GetPurchaseOrdersByFilter.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filter | object | no | Purchase order filter. All fields are optional. |
Create a new order for an outlet, in Open status. Then add lines with brewman_add_order_line. Writes to the BrewMan tenant. BrewMan API: POST /webapi/Order/v1/CreateOrder.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| outlet_id | string | yes | The outlet the order is for. Required; it cannot be changed later. |
| customer_reference | string | no | Customer reference shown on documents. |
| delivery_date | string | no | Delivery date (yyyy-mm-dd). |
| despatch_date | string | no | Despatch date (yyyy-mm-dd). |
| duty_return_date_override | string | no | Special duty return date, only when needed. |
| standard_order_type | string | no | Duty and price type of the order. |
| price_list_id | string | no | Price list id (from brewman_list_price_lists). |
| order_source | string | no | Source system of the order. |
| external_reference | string | no | Reference of the order in the source system. Cannot be changed later. |
Add a stock item line to an open order. Pass a new GUID as order_line_id for each line. Writes to the BrewMan tenant. BrewMan API: POST /webapi/Order/v1/AddLineToOrder.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | The order to add the line to (from brewman_create_order or brewman_list_orders). |
| order_line_id | string | yes | A new GUID for the line. Generate one for each new line. |
| stock_location_id | string | yes | The stock location the line is taken from. |
| stock_item_id | string | yes | The stock item (item id) to add. |
| quantity | number | yes | Quantity to add, in the unit of measure. |
| unit_of_measure_id | string | no | Unit of measure id of the quantity. |
| urn | string | no | Optional URN text of the line, sent as given. |
Delete one or more lines from an order. This cannot be undone through the API. BrewMan API: POST /webapi/Order/v1/DeleteLinesFromOrder.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_header_id | string | yes | The order id the lines belong to. |
| line_ids | array | yes | The ids of the lines to delete. |
Cancel an order and give the reason. A cancelled order cannot be reopened through the API. BrewMan API: POST /webapi/Order/v1/CancelOrder.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | The order to cancel. |
| cancellation_reason | string | yes | Why the order is cancelled. BrewMan records it. |
- 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 BrewMan MCP by usefulapi or to call it, at any volume.
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.
| 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 |
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.
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 |
|---|---|---|
| brewman_get_current_user | no tags | |
| brewman_list_outlets | no tags | |
| brewman_get_outlet | no tags | |
| brewman_list_orders | no tags | |
| brewman_get_order | no tags | |
| brewman_list_items | no tags | |
| brewman_get_stock_levels | no tags | |
| brewman_get_stock_incoming_outgoing | no tags | |
| brewman_list_price_lists | no tags | |
| brewman_list_purchase_orders | no tags | |
| brewman_create_order | state-write | state-write: declares destructiveHint: true |
| brewman_add_order_line | state-write | state-write: declares destructiveHint: true |
| brewman_delete_order_lines | state-write | state-write: declares destructiveHint: true |
| brewman_cancel_order | state-write | state-write: declares destructiveHint: true |
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
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 1.0.1.
No release note was published with this version.
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.
Any signed-in account that does not publish BrewMan MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.