
Reverb MCP server
online · 100% uptimeReverb MCP — the musical-instrument marketplace
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Reverb yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Reverb tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Reverb compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 73/100
- higher than 38% of 48,243 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 44 ms
- faster than 93% of 30,027 servers
Release history: 5 versions in the registry since 2026-09-13, latest 2026-11-04, typically one every 12 days.
Install Reverb in Claude Code, Cursor or VS Code
claude mcp add --transport http reverb https://gateway.pipeworx.io/reverb/mcp
What the publisher says
From the Reverb repository's README, as published. We do not edit it. Read it on GitHub
@pipeworx/reverb
Live listings from Reverb.com, the musical-instrument marketplace — guitars, amps, pedals, synths, drums and pro audio, with make/model/year/finish/condition and the seller's asking price.
Part of Pipeworx — an MCP gateway connecting AI agents to 1558+ live data sources.
Tools
model, product_type/category, condition, price band, year range, region, handmade, sort/order). Answers "what is a 1960s Gibson electric going for right now, and who is selling it".
- reverb_search(query, ...) — listing search with the gear filters (make,
asking and buyer price, offer/inventory state, photos, shipping rates by region.
- reverblisting(listingid) — one listing in full: seller description,
preferred-seller status, location, shipping posture.
- reverbshop(shopslug) — seller profile: feedback count, rating,
producttype / category on reverbsearch without guessing slugs.
- reverbcategories(rootslug?) — the category tree, so a caller can fill
Auth
Keyless. Every endpoint this pack calls answers without a token — verified 2026-09-05. Only account-scoped Reverb endpoints (/api/my/, orders, selling) need OAuth, and none of those are exposed here, so there is no PLATFORMREVERB_KEY and no BYOK path.
Asking prices only — there is no sold data here
Reverb's public Price Guide is retired. Both /api/priceguide and /api/priceguide/transactions answer:
HTTP 403 { "Error": "This endpoint is no longer publicly available." }for every query (verified 2026-09-05). Everything this pack returns is a live asking price, not a realized sale, and every response says so in its pricebasis and solddata fields. Do not use it as comps. For realized instrument prices, Reverb is not the source.
Data sources
query, make, model, producttype, category, condition, pricemin, pricemax, currency, yearmin, yearmax, itemregion, shipsto, handmade, sort, order, page, perpage.
- — listing search. Params used:
- — listing detail.
- — seller profile.
- — the full category tree (roots plus sub-categories, 320 entries). Plain /api/categories returns only the 14 roots.
Docs live at (dev.reverb.com redirects there).
Things worth not rediscovering:
select the JSON API. Without them you can get HTML.
- The Accept-Version: 3.0 and Accept: application/hal+json headers are what
query still reports totalpages: 50. Requesting page=51 nevertheless returns results, so treat the cap as a display artifact, not a paging bound. reverbsearch returns a totalpagesnote saying this.
- totalpages is capped at 50** regardless of total — a 77,081-result
the seller's currency, while price.currency follows the currency param.
- price and buyerprice differ when tax is involved; listingcurrency is
which the search payload omits.
- Listing detail carries the shop's feedbackcount and ratingpercentage,
- reverb.com/llms.txt is a 404 as of 2026-09-05, despite reports otherwise.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"reverb": {
"url": "https://gateway.pipeworx.io/reverb/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/reverb/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Reverb: common questions
- Is Reverb MCP server safe?
- Mostly: it is graded B (73/100). Read the Reverb safety report
- How do I install Reverb?
- It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Reverb need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Reverb maintained?
- The last commit was 40 days ago (2026-09-26). The latest release is v0.2.1.
- Is Reverb up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Reverb compare with other MCP servers?
- safety score 73/100 (higher than 38% of 48,243 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 44 ms (faster than 93% of 30,027 servers). Full comparison.