Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
btw 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
Agentic group buying. Agents pool demand into chains that clear at a group price. Waitlist is open.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http btw-mcp 'https://btw.space/mcp?utm_source=mcp-registry'
# 2 — ask your agent for something these tools do
# my_agent, waitlist, list_chains and 16 more
btw 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 btw-mcp 'https://btw.space/mcp?utm_source=mcp-registry'Reconnect, 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.
19 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.
What your human's btw agent is watching, with a status on each thing: watching (counting the other agents), group forming (enough want it that btw is talking to the brand), or live (there's a price and a deadline, hold a spot). Takes their email. The list opens once they've clicked the confirm link btw emailed them the first time you called.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | your human's email |
Old style: put your human on the list to hear when the next product goes live. Prefer want with a link, or hold on what's live. Needs their email. Optionally say what they want to buy and which agent platform you are.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | no | your human's email | |
| want | string | no | what your human wants to buy, plainly |
| platform | string | no | your agent platform, like claude, grok, chatgpt, other |
| referral | string | no | a friend's referral code or link, if you came through one |
Every product btw has run or queued: the live one, what's up next by wants, and what filled or closed. Use status for the live one.
No parameter schema on file.
Hold your human a spot on the live product. Needs their email. Returns the price this spot locks and a link where they save a card; the spot is held once they do. The first spots lock at the early price; every spot after locks at the group price. The result says which one this spot got. Nothing is charged now. If the product fills, the deposit is charged and applied to their purchase; they pay the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | your human's email | |
| chain | string | no | a product slug; leave it out for what's live |
| max_price_usd | number | no | optional cap on the deposit in dollars |
| name | string | no | first name and last initial, shown on the product page |
| ref | string | no | a referral code from another buyer's link, the r= part |
| invite_code | string | no | not needed any more |
The old name for hold. Hold your human a spot on the live product. Needs their email. Returns the price this spot locks and a link where they save a card; the spot is held once they do. The first spots lock at the early price; every spot after locks at the group price. The result says which one this spot got. Nothing is charged now. If the product fills, the deposit is charged and applied to their
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | your human's email | |
| chain | string | no | a product slug; leave it out for what's live |
| max_price_usd | number | no | optional cap on the deposit in dollars |
| name | string | no | first name and last initial, shown on the product page |
| ref | string | no | a referral code from another buyer's link, the r= part |
| invite_code | string | no | not needed any more |
What's live: the product, its list and group price, how many buyers unlock the price, how many are committed, how many want it, spots left, and the deadline if one is set. Give a slug to ask about another product, and an email to also see that person's spot.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | no | a product slug; leave it out for what's live |
| string | no | check this person's spot |
Release a held spot. Needs the product slug, the email that holds it, and the commitment id from hold or status. Nothing is charged for a released spot.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | yes | product slug |
| string | yes | — | |
| commitment_id | string | yes | — |
The old name for release. Release a held spot. Needs the product slug, the email that holds it, and the commitment id from hold or status. Nothing is charged for a released spot.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | yes | product slug |
| string | yes | — | |
| commitment_id | string | yes | — |
Old style: park what your human wants in plain words with the most they'd pay. Prefer want with a link.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| description | string | yes | what your human wants, plainly |
| max_price_usd | number | yes | the most they'd pay, in dollars |
| string | no | optional, so we can say when a chain opens |
Add something to your human's btw agent. Takes a link or an ASIN plus their email; a new email gets an agent. A hotel link becomes a stay (give month, and nights if known), a subscription link becomes software (give plan), anything else is gear. Or set type and the fields outright: stay needs hotel and month, home needs job and zip, software needs product and plan. Their agent starts watching it a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | no | a product, hotel, or subscription link |
| asin | string | no | an Amazon ASIN, 10 letters and digits |
| asins | array | no | ASINs you read off a page yourself, up to 100 |
| type | string | no | skip auto-detection and say the type |
| name | string | no | gym: the gym or studio name |
| hotel | string | no | stay: hotel name or link |
| month | string | no | stay: month as YYYY-MM |
| nights | integer | no | stay: nights, if known |
| job | string | no | home: solar, home-battery, ev-charger, heat-pump, roof, windows, sauna-install, other |
| zip | string | no | home: five digit US zip |
| note | string | no | home or stay: a short note |
| product | string | no | software: product name or link |
| plan | string | no | software: individual, family, team, other |
| string | yes | your human's email, same as the waitlist |
Read a public wishlist and add every item to your human's btw agent. Amazon wishlists and Steam wishlists. Takes the list link plus their email; a new email gets an agent. Returns the items found and how many other agents want each one. If the server can't read the list, the reply says so; then open the list yourself and pass the ASINs, or call want once per product link. btw doesn't buy from Amaz
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | no | the list link. Amazon: open the list, tap Share, copy the link. Steam: the profile's wishlist page |
| asins | array | no | ASINs you read off the list yourself, up to 100 |
| string | yes | your human's email, same as the waitlist |
Your human wants a hotel in a given month. Takes the hotel (name or link), the month as YYYY-MM, nights if known, and their email. People wanting the same hotel in the same month count together; when enough do, btw asks the hotel for a group rate. Returns how many others want it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hotel | string | yes | hotel name or a link to it |
| month | string | yes | month as YYYY-MM |
| nights | integer | no | nights, if known |
| note | string | no | — |
| string | yes | your human's email, same as the waitlist |
Your human wants a home job done: solar, home-battery, ev-charger, heat-pump, roof, windows, sauna-install, other. Takes the job, their five digit zip, an optional note, and their email. Homes near each other wanting the same job count together; when enough do, btw gets a group quote from local installers. Returns how many others nearby want it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job | string | yes | the job |
| zip | string | yes | five digit US zip |
| note | string | no | anything the installer should know |
| string | yes | your human's email, same as the waitlist |
Your human wants a software subscription at group pricing. Takes the product (name or link), the plan (individual, family, team, other), and their email. Annual plans; vendors already have volume tiers and btw brings the volume. Returns how many others want the same product on the same plan.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | yes | product name or a link to it |
| plan | string | yes | the plan |
| string | yes | your human's email, same as the waitlist |
Your human wants a membership at a gym or studio near them. Takes the name, their five digit zip, the plan (monthly, annual, class-pack, other), and their email. People near the same gym on the same plan count together; when enough do, btw asks for a group rate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | gym or studio name |
| zip | string | yes | five digit US zip |
| plan | string | yes | the plan |
| string | yes | your human's email, same as the waitlist |
Counts at a glance: live, queued, filled. Use status for the live product.
No parameter schema on file.
One product by slug. Prefer status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | chain slug |
The old v1 join. Use hold instead.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | no | — |
| monthly_commit_usd | number | no | — |
| team_name | string | no | — |
The old v1 park. Use want with a link instead.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider | string | no | — |
| category | string | no | — |
| min_discount_pct | number | no | — |
| monthly_cap_usd | number | no | — |
| note | string | no | — |
- 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 btw 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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
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 2.1.0.
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 btw 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.