Protoship
REMOTE · MCP.PROTOSHIP.DEV
Checks an ESP32 project (board, pins, power, JLCPCB parts, costs) and gets the build finished.
Available components
Last scanned (13 minutes ago)
Scores higher than 45% of remote servers
Reachable. Last reached 5 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 Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1208 tokens (~201/item across 6 items; 6 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 Management0
- Stability check failed: schema churn in the 5 days we've observed: 4 tool removals, 0 breaking changes, 0 auth/transport breaks, 5 additions. See how to fix → Fail
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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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
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 0
- The server rewrote its instructions, which are the text every model session reads security
- 4 Nov 26 −2
- Stability: 0.10 → fail ▼ security
- Tool “catalog” was removed ▼ security
- Tool “quote” was removed ▼ security
- Tool “request_part” was removed ▼ security
- Tool “reserve” was removed ▼ security
- Tool “status” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “join_waitlist” rewrote its description, which is the text the model reads security
- Schema quality: 148 → 199 ▼ functional
- Schema quality: 740 → 914 ▼ functional
- Schema quality: good → excellent functional
- Destructive annotations: pass → 100 functional
- Server version: 0.3.0 → 0.4.0 functional
- Server version: 0.2.0 → 0.3.0 functional
- New tool “check_project” functional
- New tool “estimate_build” functional
- New tool “match_parts” functional
- New tool “request_finish” functional
- New tool “request_status” functional
- New tool “request_part” functional
- “join_waitlist” reworded the description of “device” cosmetic
- 2 Nov 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.
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 66
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 · Probed https://mcp.protoship.dev
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=protoship.dev | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 4abf4c9a8cb0463c0e2d643fbcd75df1 |
| SANs: protoship.dev, mcp.protoship.dev, *.mcp.protoship.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.protoship.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| protoship.dev. | 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://mcp.protoship.dev | Verified | 200 | |
| http (plaintext) | http://mcp.protoship.dev | Inconclusive | 405 |
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_project Check an ESP32 project ~210
Reads an ESP32 project from a public GitHub repo (or a folder or file in it, or a raw file link) or from files you pass inline, and returns: the board and chip, firmware type, the modules it uses, every GPIO it assigns with findings (flash pins, strapping pins, input-only pins, the board's own display/touch/SD pins, octal PSRAM pins), power notes, whether there is a custom PCB, BOM or enclosure files, whether the build fits Finish my build, and next steps. Free, read-only, stores nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | Project files inline instead of url: ESPHome YAML, platformio.ini, sketch (.ino/.cpp/.h), KiCad schematic, BOM CSV. Up to 12 files, 200 kB each. |
| url | string | – | https link to a public GitHub repo, a folder (…/tree/branch/path) or a file, or any raw file URL. |
No output schema declared.
No examples provided.
estimate_build Estimate cost and lead time ~221
Compares ordering a small PCB yourself (JLCPCB bare boards and Economic assembly, AISLER in Germany; fees, shipping, EU import duty and lead times read from the vendors' own pages, with links and the date checked) with having the existing build finished by Protoship. Leaves out what it does not know instead of guessing. Free, read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| assembled | integer | – | Boards to have assembled. Default 0. |
| board_mm | array | – | Board width and height in mm. Default [50, 50]. |
| boards | integer | – | Bare boards to order. Default 5. |
| country | string | – | Two-letter EU country code of the delivery address. Default DE. |
| extended_parts | integer | – | Unique parts outside basic/preferred (from match_parts). |
| joints | integer | – | Solder joints per board, if known. |
| layers | integer | – | Copper layers. Default 2. |
| parts_cost_usd | number | – | Parts cost per board in USD (from match_parts), if known. |
No output schema declared.
No examples provided.
join_waitlist Join the Protoship waitlist ~128
Puts your user on the Protoship waitlist for ordering PCBs, 3D prints, CNC parts and sheet metal through their agent. Protoship sends one email to confirm the address, later one with the invite. No newsletter. Use only your user's own email address and only with their consent. Privacy policy: https://protoship.dev/privacy
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | – | What your user wants to build, in a sentence. Optional. |
| string | yes | Your user's email address. | |
| interests | array | – | What your user wants to order. Optional. |
No output schema declared.
No examples provided.
match_parts Match a BOM against JLCPCB basic parts ~151
Checks each BOM line against JLCPCB's basic and preferred-extended parts in stock. Those load without a feeder fee on Economic assembly; every other unique part costs one. Matches by LCSC number (Cxxxx), manufacturer part number, or for resistors, capacitors and inductors by value and chip size, and suggests a footprint change when the same value is basic in another size. Returns per line status, part and price, plus the feeder fees in total. Free, read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| bom | – | yes | The BOM as CSV text (KiCad or JLCPCB export: reference/designator, value/comment, footprint, quantity, mpn, lcsc columns) or as a list of lines. |
No output schema declared.
No examples provided.
request_finish Request Finish my build ~238
Sends your user's working ESP32 build to Protoship as a Finish my build request: an individual service on their own hardware (case made for their board, wiring fixed, firmware flashed and tested, back as a USB-C device). Protoship sends one email to confirm the address; after that it answers within two working days with questions or a fixed price. Nothing is binding and nothing is paid until your user accepts a price. Use only your user's own email address, only with their consent. Privacy policy: https://protoship.dev/privacy
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | yes | The board and main modules, e.g. "Cheap Yellow Display with a BME280". |
| check | string | – | A short summary of check_project, if you ran it. Optional. |
| country | string | – | Two-letter country code for the return shipment. Optional. |
| description | string | yes | What the build does and where it should live (desk, wall, in the hand). |
| string | yes | Your user's email address. | |
| project_url | string | – | Link to the firmware repo, ESPHome YAML or AI chat. Optional. |
No output schema declared.
No examples provided.
request_status Check a Finish my build request ~60
Returns the state of a request: pending until your user confirms the email, then confirmed (Protoship answers by email).
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | The id request_finish returned, e.g. F-7KQ2M9XW. |
No output schema declared.
No examples provided.
How do I install the Protoship MCP server?
Protoship is a hosted endpoint at https://mcp.protoship.dev/, 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 · mcp.protoship.dev
claude mcp add --transport http dev-protoship-protoship 'https://mcp.protoship.dev/'
What is the Protoship MCP server?
Protoship is an MCP server listed in the public MCP registry as dev.protoship/protoship. Checks an ESP32 project (board, pins, power, JLCPCB parts, costs) and gets the build finished. This page covers its hosted endpoint (https://mcp.protoship.dev).
Is the Protoship MCP server safe to use?
Protoship scores 65 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 Protoship MCP server expose?
Protoship exposes 6 tools: check_project, match_parts, estimate_build, request_finish, request_status, join_waitlist. Their descriptions and schemas cost roughly 1,008 tokens of context every time the server is loaded.
Does the Protoship MCP server require authentication?
No. We connected to Protoship without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Protoship MCP server still maintained?
Protoship 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.