PedalBro
REMOTE · API.PEDALBRO.COM
Guitar pedal specs, new and used prices, price history, review scores, board checks, buying guides.
Available components
Last scanned (2 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Entertainment and Games
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 783 tokens (~111/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 85% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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 · Probed https://api.pedalbro.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pedalbro.com | CN=YE2,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 65969ba4712818c15e44b4baa83861633c3 |
| SANs: *.pedalbro.com, pedalbro.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.pedalbro.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| pedalbro.com. | 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://api.pedalbro.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.pedalbro.com/mcp | HTTPS enforced | 301 | https://api.pedalbro.com/mcp |
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 →
check_board Check a pedalboard ~128
Check a set of pedals as a pedalboard: a suggested signal-chain order with reasons, total current draw against a power supply, and a count of power and compatibility issues.
| Name | Type | Req | Description |
|---|---|---|---|
| pedals | array | yes | Pedal slugs from search_pedals, in any order |
| supplyOutlets | integer | – | How many outputs the power supply has |
| supplyTotalMa | integer | – | The power supply's total current in mA, if known |
| usesFxLoop | boolean | – | True if the amp's effects loop is used, so time-based effects can go in the loop |
No output schema declared.
No examples provided.
compare_pedals Compare pedals ~44
Two to five pedals side by side: score, what each is best for, lowest new price, used median and key specs.
| Name | Type | Req | Description |
|---|---|---|---|
| slugs | array | yes | – |
No output schema declared.
No examples provided.
get_guide Get a buying guide ~63
One buying guide: who it is for, what matters when choosing, the three picks (best overall, budget, step up) with strengths, flaws and current prices, and the other pedals considered.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | A guide slug from list_guides |
No output schema declared.
No examples provided.
get_pedal Get a pedal ~89
Everything PedalBro knows about one pedal: specs (power, size, bypass, controls), a plain-language summary, the PedalBro review score, what players say, professional review ratings with links, current new and used prices with buy links, and similar pedals.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | A pedal slug from search_pedals, e.g. boss-ds-1-distortion |
No output schema declared.
No examples provided.
get_price_history Price history ~80
How a pedal's new and used prices have moved over the last 90 days (weekly points), recent sold used listings, and current prices. Useful for 'is this a good price' and 'should I buy used'.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | A pedal slug from search_pedals, e.g. boss-ds-1-distortion |
No output schema declared.
No examples provided.
list_guides List buying guides ~45
PedalBro's buying guides ('best overdrive pedals', 'best delay under $200', ...), each with its top pick. Use get_guide for the full picks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_pedals Search pedals ~159
Search guitar and bass pedals by brand, model, nickname or type (typos are fine), optionally only those buyable new under a price. Returns names, slugs and lowest new prices.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | Brand slug, e.g. boss, strymon, electro-harmonix |
| category | string | – | Category slug to narrow to, e.g. overdrive, fuzz, distortion, delay, reverb, chorus, compressor, looper |
| limit | integer | – | – |
| maxPriceUsd | number | – | Only pedals buyable new and in stock at or under this price |
| query | string | yes | e.g. 'tube screamer', 'strymon delay', 'fuzz' |
No output schema declared.
No examples provided.
How do I install the PedalBro MCP server?
PedalBro is a hosted endpoint at https://api.pedalbro.com/mcp, 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 · api.pedalbro.com
claude mcp add --transport http com-pedalbro-pedalbro 'https://api.pedalbro.com/mcp'
What is the PedalBro MCP server?
PedalBro is an MCP server listed in the public MCP registry as com.pedalbro/pedalbro. Guitar pedal specs, new and used prices, price history, review scores, board checks, buying guides. This page covers its hosted endpoint (https://api.pedalbro.com/mcp).
Is the PedalBro MCP server safe to use?
PedalBro scores 78 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 PedalBro MCP server expose?
PedalBro exposes 7 tools: search_pedals, get_pedal, compare_pedals, get_price_history, check_board, and 2 more. Their descriptions and schemas cost roughly 608 tokens of context every time the server is loaded.
Does the PedalBro MCP server require authentication?
No. We connected to PedalBro without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PedalBro MCP server still maintained?
PedalBro 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.