btw
REMOTE · BTW.SPACE
Agentic group buying. Agents pool demand into chains that clear at a group price. Waitlist is open.
Available components
Last scanned (23 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 4 Nov 2026.
Category E-commerce
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (release). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2436 tokens (~128/item across 19 items; 19 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 81% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 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.
- 2 Oct 26 0
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 19 Sept 26 0
- Tool “hold” rewrote its description, which is the text the model reads security
- Tool “join” rewrote its description, which is the text the model reads security
- “hold” added an optional parameter “ref” cosmetic
- “join” added an optional parameter “ref” cosmetic
- 18 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- New tool “release”, which the server declares destructive security
- Tool “book_stats” rewrote its description, which is the text the model reads security
- Tool “get_chain” rewrote its description, which is the text the model reads security
- Tool “join” rewrote its description, which is the text the model reads security
- Tool “join_chain” rewrote its description, which is the text the model reads security
- Tool “leave” rewrote its description, which is the text the model reads security
- Tool “list_chains” rewrote its description, which is the text the model reads security
- Tool “park” rewrote its description, which is the text the model reads security
- Tool “park_intent” rewrote its description, which is the text the model reads security
- Tool “status” rewrote its description, which is the text the model reads security
- Tool “waitlist” rewrote its description, which is the text the model reads security
- Schema quality: 1966 → 2233 ▼ functional
- New tool “hold” functional
- “join” reworded the description of “chain” cosmetic
- “join” reworded the description of “invite_code” cosmetic
- “join” reworded the description of “max_price_usd” cosmetic
- “join” reworded the description of “name” cosmetic
- “leave” reworded the description of “chain” cosmetic
- “status” reworded the description of “chain” cosmetic
- “status” reworded the description of “email” cosmetic
- “waitlist” reworded the description of “email” cosmetic
- “join” made “chain” optional cosmetic
- “join” made “invite_code” optional cosmetic
- “join” made “max_price_usd” optional cosmetic
- “status” made “chain” optional cosmetic
- Tool “join” changed its title: Join a chain → Hold a spot (old name) cosmetic
- Tool “leave” changed its title: Leave a chain → Release a spot (old name) cosmetic
- 16 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “list_chains” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 58% → 80% ▲ functional
- Server version: 2.1.0 → 2.3.0 functional
- New tool “sync_wishlist” functional
- New tool “want” functional
- New tool “want_gym” functional
- New tool “want_home” functional
- New tool “want_software” functional
- New tool “want_stay” functional
- 3 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Sept 26 0
First indexed and scored.
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 4 Nov 2026 · Probed https://btw.space/mcp?utm_source=mcp-registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=btw.space | CN=WE1,O=Google Trust Services,C=US | 29 Oct 2026 | 27 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | e584c51ad2b8675313905d7c40e1ac21 |
| SANs: btw.space, www.btw.space, *.www.btw.space | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of btw.space. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| space. | present | 51168 | 13 | Verified |
| btw.space. | 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://btw.space/mcp?utm_source=mcp-registry | Verified | 200 | |
| http (plaintext) | http://btw.space/mcp?utm_source=mcp-registry | Inconclusive | 406 |
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 →
book_stats Book stats ~26
Counts at a glance: live, queued, filled. Use status for the live product.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_chain Get one chain ~25
One product by slug. Prefer status.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | chain slug |
No output schema declared.
No examples provided.
hold Hold a spot ~215
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 balance to the brand. If it doesn't fill, nobody pays. Stripe test mode. Test cards only, no real money moves.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | a product slug; leave it out for what's live |
| string | yes | your human's email | |
| invite_code | string | – | not needed any more |
| max_price_usd | number | – | optional cap on the deposit in dollars |
| name | string | – | first name and last initial, shown on the product page |
| ref | string | – | a referral code from another buyer's link, the r= part |
No output schema declared.
No examples provided.
join Hold a spot (old name) ~221
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 purchase; they pay the balance to the brand. If it doesn't fill, nobody pays. Stripe test mode. Test cards only, no real money moves.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | a product slug; leave it out for what's live |
| string | yes | your human's email | |
| invite_code | string | – | not needed any more |
| max_price_usd | number | – | optional cap on the deposit in dollars |
| name | string | – | first name and last initial, shown on the product page |
| ref | string | – | a referral code from another buyer's link, the r= part |
No output schema declared.
No examples provided.
join_chain Join a chain (old name) ~43
The old v1 join. Use hold instead.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | – |
| monthly_commit_usd | number | – | – |
| team_name | string | – | – |
No output schema declared.
No examples provided.
leave Release a spot (old name) ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | product slug |
| commitment_id | string | yes | – |
| string | yes | – |
No output schema declared.
No examples provided.
list_chains List chains ~40
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
my_agent My agent ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | your human's email |
No output schema declared.
No examples provided.
park Park a want ~77
Old style: park what your human wants in plain words with the most they'd pay. Prefer want with a link.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | what your human wants, plainly |
| string | – | optional, so we can say when a chain opens | |
| max_price_usd | number | yes | the most they'd pay, in dollars |
No output schema declared.
No examples provided.
park_intent Park a standing order (old name) ~62
The old v1 park. Use want with a link instead.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| min_discount_pct | number | – | – |
| monthly_cap_usd | number | – | – |
| note | string | – | – |
| provider | string | – | – |
No output schema declared.
No examples provided.
release Release a spot ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | product slug |
| commitment_id | string | yes | – |
| string | yes | – |
No output schema declared.
No examples provided.
status Chain status ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | a product slug; leave it out for what's live |
| string | – | check this person's spot |
No output schema declared.
No examples provided.
sync_wishlist Import a wishlist ~187
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 Amazon. The link is how we know what you want; the group price comes from the brand.
| Name | Type | Req | Description |
|---|---|---|---|
| asins | array | – | ASINs you read off the list yourself, up to 100 |
| string | yes | your human's email, same as the waitlist | |
| url | string | – | the list link. Amazon: open the list, tap Share, copy the link. Steam: the profile's wishlist page |
No output schema declared.
No examples provided.
waitlist Join the waitlist ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | your human's email | |
| platform | string | – | your agent platform, like claude, grok, chatgpt, other |
| referral | string | – | a friend's referral code or link, if you came through one |
| want | string | – | what your human wants to buy, plainly |
No output schema declared.
No examples provided.
want Add to my agent ~372
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 and the reply says how many other agents already want it. If you already read a page yourself, pass asins instead of a link. btw doesn't buy from Amazon. The link is how we know what you want; the group price comes from the brand.
| Name | Type | Req | Description |
|---|---|---|---|
| asin | string | – | an Amazon ASIN, 10 letters and digits |
| asins | array | – | ASINs you read off a page yourself, up to 100 |
| string | yes | your human's email, same as the waitlist | |
| hotel | string | – | stay: hotel name or link |
| job | string | – | home: solar, home-battery, ev-charger, heat-pump, roof, windows, sauna-install, other |
| month | string | – | stay: month as YYYY-MM |
| name | string | – | gym: the gym or studio name |
| nights | integer | – | stay: nights, if known |
| note | string | – | home or stay: a short note |
| plan | string | – | software: individual, family, team, other |
| product | string | – | software: product name or link |
| type | string | – | skip auto-detection and say the type |
| url | string | – | a product, hotel, or subscription link |
| zip | string | – | home: five digit US zip |
No output schema declared.
No examples provided.
want_gym Want a gym or studio membership ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | your human's email, same as the waitlist | |
| name | string | yes | gym or studio name |
| plan | string | yes | the plan |
| zip | string | yes | five digit US zip |
No output schema declared.
No examples provided.
want_home Want a home job ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | your human's email, same as the waitlist | |
| job | string | yes | the job |
| note | string | – | anything the installer should know |
| zip | string | yes | five digit US zip |
No output schema declared.
No examples provided.
want_software Want a subscription ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | your human's email, same as the waitlist | |
| plan | string | yes | the plan |
| product | string | yes | product name or a link to it |
No output schema declared.
No examples provided.
want_stay Want a stay ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | your human's email, same as the waitlist | |
| hotel | string | yes | hotel name or a link to it |
| month | string | yes | month as YYYY-MM |
| nights | integer | – | nights, if known |
| note | string | – | – |
No output schema declared.
No examples provided.
How do I install the btw MCP server?
btw is a hosted endpoint at https://btw.space/mcp?utm_source=mcp-registry, 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 · btw.space
claude mcp add --transport http space-btw-btw 'https://btw.space/mcp?utm_source=mcp-registry'
What is the btw MCP server?
btw is an MCP server listed in the public MCP registry as space.btw/btw. Agentic group buying. Agents pool demand into chains that clear at a group price. Waitlist is open. This page covers its hosted endpoint (https://btw.space/mcp?utm_source=mcp-registry).
Is the btw MCP server safe to use?
btw scores 72 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 btw MCP server expose?
btw exposes 19 tools: my_agent, waitlist, list_chains, hold, join, and 14 more. Their descriptions and schemas cost roughly 2,213 tokens of context every time the server is loaded.
Does the btw MCP server require authentication?
No. We connected to btw without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the btw MCP server still maintained?
btw is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.