Reverb
NPM · @PIPEWORX/MCP-REVERB · 2 COMPONENTS
Reverb MCP — the musical-instrument marketplace
Available components
Last scanned (10 hours ago)
Scores higher than 76% of npm servers
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-reverb). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 849 tokens (~212/item across 4 items; 4 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 5 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 4 Nov 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-reverb@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-reverb |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-reverb/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3691883897 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:536be7ca4687929f2a855a14a7cd8371933c11ef962a3f37bf7991bcc065135e210471f0c037164509b9b1be1ce3f431b9d7649835a6d16607b47d31f |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
reverb_categories ~95
The Reverb.com category tree — root product types (electric guitars, effects and pedals, amps, keyboards and synths, drums, pro audio, folk instruments) and their sub-categories, with the slugs and UUIDs used by the product_type and category filters on reverb_search.
| Name | Type | Req | Description |
|---|---|---|---|
| root_slug | string | – | Optional: return only this root category and its children, e.g. "electric-guitars" |
No output schema declared.
No examples provided.
reverb_listing ~97
One Reverb.com listing in full, by listing ID: title, make, model, year, finish, condition, seller description, asking and buyer price, offer/inventory state, categories, photos and shipping rates by region. The price is the seller's asking price on a live listing.
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | number | yes | Reverb listing ID, e.g. 98282577 (the `id` from reverb_search) |
No output schema declared.
No examples provided.
reverb_search ~511
Search live Reverb.com listings for musical gear — guitars, amps, pedals, synths, drums, pro audio. Returns asking prices with make, model, year, finish, condition grade and seller, filterable by category, price band, year range, condition, make and region. Prices are what sellers ARE ASKING, not what anything sold for: Reverb retired its public Price Guide, so no realized-sale data is available from this source.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Sub-category slug, e.g. "solid-body" — pairs with product_type |
| condition | string | – | Condition slug: new, b-stock, mint, excellent, very-good, good, fair, poor, non-functioning, used (used = any non-new grade) |
| currency | string | – | ISO currency for the price filters and returned prices (default USD) |
| handmade | boolean | – | Restrict to handmade/boutique listings |
| item_region | string | – | Where the item ships FROM, e.g. "US", "GB", "EUR_EU" |
| make | string | – | Brand filter, e.g. "Fender", "Gibson", "Roland" |
| model | string | – | Model filter, e.g. "Les Paul Standard" |
| order | string | – | asc | desc |
| page | number | – | 1-based page. Paging past `total_pages` still works — see `total_pages_note`. |
| per_page | number | – | 1-50 (default 20) |
| price_max | number | – | Maximum price |
| price_min | number | – | Minimum price, in the currency given by `currency` (default USD) |
| product_type | string | – | Root category slug, e.g. "electric-guitars", "effects-and-pedals", "amps", "keyboards-and-synths", "drums-and-percussion". Call reverb_categories for the full list. |
| query | string | yes | Free-text query, e.g. "stratocaster", "Tube Screamer TS9", "Juno-106" |
| ships_to | string | – | Country code the item must ship to, e.g. "US" |
| sort | string | – | price | published_at (default: Reverb relevance) |
| year_max | string | – | Latest build year, e.g. "1970" |
| year_min | string | – | Earliest build year, e.g. "1960" |
No output schema declared.
No examples provided.
reverb_shop ~94
Reverb.com seller profile by shop slug: shop name, location, feedback count and rating, preferred-seller status, return policy and shipping posture. Answers "who is this seller and what is their track record" for a listing found via reverb_search.
| Name | Type | Req | Description |
|---|---|---|---|
| shop_slug | string | yes | Shop slug, e.g. "guitar-sauce-italy" (the `shop_slug` from reverb_search) |
No output schema declared.
No examples provided.
How do I install the Reverb MCP server?
Reverb runs locally as an npm package, launched with npx -y @pipeworx/mcp-reverb. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-reverb
claude mcp add pipeworx-io-reverb -- npx -y @pipeworx/mcp-reverb
What is the Reverb MCP server?
Reverb is an MCP server listed in the public MCP registry as io.github.pipeworx-io/reverb. Reverb MCP, the musical-instrument marketplace. This page covers its npm package (@pipeworx/mcp-reverb).
Is the Reverb MCP server safe to use?
Reverb scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Reverb MCP server expose?
Reverb exposes 4 tools: reverb_search, reverb_listing, reverb_shop, reverb_categories. Their descriptions and schemas cost roughly 797 tokens of context every time the server is loaded.
Is the Reverb MCP server still maintained?
Reverb is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Reverb MCP server under?
Reverb declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.