Protoship MCP server
dev.protoship/protoshipprotoship.devstreamable-httpv0.4.0Scanned
Checks an ESP32 project (board, pins, power, JLCPCB parts, costs) and gets the build finished.
6 tools: 1 do something that can't be undone, 3 change things and 2 only read.
- Reads private data · 1
- Reads text others write · 3
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Protoship MCP server can do
The Protoship MCP server is published by protoship.dev, a domain the MCP Registry verified. It has 6 tools. It can do things that cannot be undone, such as sending, paying or publishing (request_finish) and create or change data (3 tools: match_parts, request_status and join_waitlist), but cannot delete data. 2 tools only read.
1 tool reads private data (check_project); 3 tools bring in text other people can write (check_project, request_finish and join_waitlist); 1 tool can send data out of your system (check_project). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 18, 2026, version 0.4.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Can't be undone 1Claude Code: ask
request_finishSends 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 flas…Reads text others writeNo findings
Why it is in this group
- The name "request_finish" says "request": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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
Annotations the server declares
- title: Request Finish my build
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Changes things 3Claude Code: ask
join_waitlistPuts your user on the Protoship waitlist for ordering PCBs, 3D prints, CNC parts and sheet metal through their agent.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "put": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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
Annotations the server declares
- title: Join the Protoship waitlist
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
match_partsChecks each BOM line against JLCPCB's basic and preferred-extended parts in stock.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Match a BOM against JLCPCB basic parts
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
request_statusReturns the state of a request: pending (waits for your user to confirm the email), confirmed (on its way to Protoship), forward_failed (confirmed, sent again within the hour), for…1 finding
Why it is in this group
- The name "request_status" says "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "request_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "request_status" says "request": a word for a change.
Description, as the server wrote it Returns the state of a request: pending (waits for your user to confirm the email), confirmed (on its way to Protoship), forward_failed (confirmed, sent again within the hour), forwarded (Protoship has it and answers by email within two working days), answered, closed.
Annotations the server declares
- title: Check a Finish my build request
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
check_projectReads 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 …Reads private dataReads text others writeCan send data outNo findings
Why it is in this group
- The description's first verb is "read": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "repo": it reads repositories.
- private-dataThe input names a file (input.files), and the tool reads: it reads files.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check an ESP32 project
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
estimate_buildCompares 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,…No findings
Why it is in this group
- The description's first verb is "compare": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Estimate cost and lead time
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
3 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__protoship__check_project"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:21 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.protoship.dev: tools/list returned 6 tools to an anonymous client, including request_finish (irreversible), match_parts (write), request_status (write), join_waitlist (write)
Posture changes
- Nov 8, 2026
- Tools that change things, listed without credentials: 3 to 4
Findings
Matches of fixed checks, with the text they matched.
- Warnrequest_status
The server marks "request_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "request_status" says "request": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools4 changed.~4 changedView diff
- Changed:check_projectOnly readsannotations
- Changed:estimate_buildOnly readsannotations
- Changed:match_partsChanges thingsannotations
- Changed:request_statusChanges thingsdescriptionannotations
PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 4.View diff
- Tools that change things, listed without credentials: 3 to 4
Tools5 added, 4 removed, 1 changed.+5 added−4 removed~1 changedView diff
- Added:check_projectOnly reads
- Added:estimate_buildOnly reads
- Added:match_partsChanges things
- Added:request_finishCan't be undone
- Added:request_statusChanges things
- Removed:catalog
- Removed:quote
- Removed:reserve
- Removed:status
- Changed:join_waitlistChanges thingsdescriptioninputSchema
Install
Pinned to version 0.4.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http protoship https://mcp.protoship.devclaude mcp add --transport http protoship https://mcp.protoship.devRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__protoship__estimate_build"
],
"ask": [
"mcp__protoship__check_project",
"mcp__protoship__match_parts",
"mcp__protoship__request_finish",
"mcp__protoship__request_status",
"mcp__protoship__join_waitlist"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as protoship. Review it before you use it.
Capability tags behind 3 rules
- mcp__protoship__check_project private-data, untrusted-input, outbound
- mcp__protoship__request_finish untrusted-input
- mcp__protoship__join_waitlist untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.protoship/protoship/verify?hash=c35a9385f5e2dd70848d9239e0f60e3d6b36fa38213ff55d4956a05e22fe3726" | jq -e '.changed == false'Pinned hash c35a9385f5e2, from Nov 18, 2026, 15:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.protoship/protoship/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.protoship/protoship)Source: MCP Registry. Synced Nov 4, 2026, 22:17 UTC.
Protoship MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Protoship MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Protoship MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Protoship MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: request_finish.
What tools does the Protoship MCP server have?
- 6 tools: 1 irreversible, 3 write, 2 read. request_finish, match_parts, request_status, join_waitlist, check_project and estimate_build.
Does the Protoship MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Protoship MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_project.
Has the Protoship MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.