# PedalBro (remote · api.pedalbro.com)

Guitar pedal specs, new and used prices, price history, review scores, board checks, buying guides.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.pedalbro.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-pedalbro-pedalbro/api.md), [page](https://verifymcp.io/servers/com-pedalbro-pedalbro/api)

## Channel facts

- Endpoint: `https://api.pedalbro.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 783 tokens (~111/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 85% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-pedalbro-pedalbro 'https://api.pedalbro.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-pedalbro-pedalbro": {
      "url": "https://api.pedalbro.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-pedalbro-pedalbro": {
      "type": "http",
      "url": "https://api.pedalbro.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-pedalbro-pedalbro]
url = "https://api.pedalbro.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-pedalbro-pedalbro": {
      "type": "remote",
      "url": "https://api.pedalbro.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-pedalbro-pedalbro --url 'https://api.pedalbro.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-pedalbro-pedalbro:
    url: "https://api.pedalbro.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-pedalbro-pedalbro": {
      "Transport": "http",
      "Url": "https://api.pedalbro.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-pedalbro-pedalbro -t streamable-http -u 'https://api.pedalbro.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-pedalbro-pedalbro": {
      "type": "http",
      "url": "https://api.pedalbro.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 78, +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.

### 2026-11-02 (score 77, +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.

### 2026-10-31 (score 76, +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.

### 2026-10-29 (score 75, +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.

### 2026-10-27 (score 74, +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.

### 2026-10-25 (score 73, +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.

### 2026-10-23 (score 72, +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.

### 2026-10-21 (score 71, +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.

## MCP tools (7)

### `search_pedals` (~159 tokens)

Search pedals

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.

Input parameters:

- `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, required): e.g. 'tube screamer', 'strymon delay', 'fuzz'

### `get_pedal` (~89 tokens)

Get a pedal

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.

Input parameters:

- `slug` (string, required): A pedal slug from search_pedals, e.g. boss-ds-1-distortion

### `compare_pedals` (~44 tokens)

Compare pedals

Two to five pedals side by side: score, what each is best for, lowest new price, used median and key specs.

Input parameters:

- `slugs` (array, required)

### `get_price_history` (~80 tokens)

Price history

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'.

Input parameters:

- `slug` (string, required): A pedal slug from search_pedals, e.g. boss-ds-1-distortion

### `check_board` (~128 tokens)

Check a pedalboard

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.

Input parameters:

- `pedals` (array, required): 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

### `list_guides` (~45 tokens)

List buying guides

PedalBro's buying guides ('best overdrive pedals', 'best delay under $200', ...), each with its top pick. Use get_guide for the full picks.

### `get_guide` (~63 tokens)

Get a buying guide

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.

Input parameters:

- `slug` (string, required): A guide slug from list_guides

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-pedalbro-pedalbro/api#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 77
- 2026-11-03: 77
- 2026-11-02: 77
- 2026-11-01: 76
- 2026-10-31: 76
- 2026-10-30: 75
- 2026-10-29: 75
- 2026-10-28: 74
- 2026-10-27: 74
- 2026-10-26: 73
- 2026-10-25: 73
- 2026-10-24: 72
- 2026-10-23: 72
- 2026-10-22: 71
- 2026-10-21: 71
- 2026-10-20: 70
- 2026-10-19: 70

## Common questions

### 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.

### What did VerifyMCP test on the PedalBro MCP server?

VerifyMCP ran 13 checks on PedalBro, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.pedalbro.com/mcp
- Website: https://pedalbro.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-pedalbro-pedalbro/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-pedalbro-pedalbro/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-pedalbro-pedalbro/api.json
- HTML version of this page: https://verifymcp.io/servers/com-pedalbro-pedalbro/api
