PCBBrew
REMOTE · PCBBREW.DEV
Boards and modules for real PCBs: catalogue, KiCad parts, wiring and power checks, published boards.
Available components
Last scanned (21 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category IoT and Hardware
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 Security80
- 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. 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 658 tokens (~109/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_part” rewrote its description, which is the text the model reads security
- Tool “search_parts” rewrote its description, which is the text the model reads security
- Schema quality: fail → pass ▲ functional
- “search_parts” reworded the description of “kind” cosmetic
- 14 Nov 26 +1
- Tool “search_parts” rewrote its description, which is the text the model reads security
- “search_parts” reworded the description of “kind” cosmetic
- 12 Nov 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.
- 10 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_part” rewrote its description, which is the text the model reads security
- Tool coverage: 100% → 91% ▼ functional
- Schema quality: pass → fail ▼ functional
- Server version: 1.0.1 → 1.1.0 functional
- New tool “check_wiring” functional
- New tool “power_budget” functional
- 9 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 8 Nov 26 71
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 21 Nov 2026 · Probed https://pcbbrew.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pcbbrew.dev | CN=YE1,O=Let's Encrypt,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 61eff3871cdafbcb923cfd8add560cc388b |
| SANs: *.pcbbrew.dev, pcbbrew.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 pcbbrew.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| pcbbrew.dev. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), usb=(self), serial=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pcbbrew.dev/mcp | Verified | 200 | |
| http (plaintext) | http://pcbbrew.dev/mcp | HTTPS enforced | 301 | https://pcbbrew.dev/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_wiring Check module wiring ~198
Checks how modules are wired to a microcontroller board, pin by pin, with PCBBrew's catalogue data (no AI): missing or unknown pins, pins not on the headers, wrong supply (3.3 V module on 5 V), 5 V signals into non 5 V tolerant GPIOs, analog outputs on non-ADC pins, boot/strapping pins, pins used twice, invalid I2C pins (Arduino A4/A5, RP2040 pairs) and I2C address conflicts. Board and module ids come from search_parts; board pins by their header name (GPIO4, D7, A0, GP15, 3V3, 5V, GND).
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | yes | board id, e.g. ESP32-S3-DevKitC-1, Arduino-Nano, Raspberry-Pi-Pico |
| modules | array | yes | modules and their wiring |
No output schema declared.
No examples provided.
get_part Get a board or module ~62
One board or module from the catalogue by id: description, pins with their role, interfaces, I2C addresses, Arduino libraries, whether PCBBrew simulates it, where to buy it and a picture.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | id from search_parts |
No output schema declared.
No examples provided.
list_showcase List published boards ~41
Boards that PCBBrew users designed and chose to publish: title, cover image, author and likes.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | maximum number of boards |
No output schema declared.
No examples provided.
power_budget Estimate supply current ~72
Typical and peak supply current of a board plus its modules (servos, LED strips, displays, radios...), compared with what USB and the board's 3.3 V regulator can give, with advice (no AI).
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | yes | board id from search_parts |
| modules | array | yes | – |
No output schema declared.
No examples provided.
search_kicad_parts Search KiCad components ~86
Search the KiCad symbol libraries PCBBrew designs with (resistors, regulators, op-amps, timers, MOSFETs, connectors...): symbol id, description and datasheet link.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | maximum number of results |
| query | string | yes | e.g. 'AMS1117', 'NE555', 'USB-C receptacle' |
No output schema declared.
No examples provided.
search_parts Search boards and modules ~125
Search PCBBrew's catalogue of microcontroller boards (ESP32, Arduino, Raspberry Pi Pico, display boards) and plug-in modules (sensors, displays, motor drivers, radio, storage) by name, chip, use or interface. Every entry can be placed on a PCB designed by PCBBrew; most are simulated.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | only boards, only modules, or both |
| limit | integer | – | maximum number of results |
| query | string | yes | e.g. 'CO2 sensor', 'e-paper', 'ESP32-S3' |
No output schema declared.
No examples provided.
How do I install the PCBBrew MCP server?
PCBBrew is a hosted endpoint at https://pcbbrew.dev/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 · pcbbrew.dev
claude mcp add --transport http dev-pcbbrew-pcbbrew 'https://pcbbrew.dev/mcp'
What is the PCBBrew MCP server?
PCBBrew is an MCP server listed in the public MCP registry as dev.pcbbrew/pcbbrew. Boards and modules for real PCBs: catalogue, KiCad parts, wiring and power checks, published boards. This page covers its hosted endpoint (https://pcbbrew.dev/mcp).
Is the PCBBrew MCP server safe to use?
PCBBrew scores 77 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 PCBBrew MCP server expose?
PCBBrew exposes 6 tools: search_parts, get_part, search_kicad_parts, check_wiring, power_budget, list_showcase. Their descriptions and schemas cost roughly 584 tokens of context every time the server is loaded.
Does the PCBBrew MCP server require authentication?
No. We connected to PCBBrew without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PCBBrew MCP server still maintained?
PCBBrew is still listed as active in the MCP registry. We last reached this channel on 21 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 PCBBrew MCP server?
VerifyMCP ran 13 checks on PCBBrew, 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.