Perfboard Designer MCP server
com.perfboarddesigner/mcpperfboarddesigner.comstreamable-httpv0.1.0Scanned
Design perfboard and stripboard layouts, check the wiring and get a link to open them in the editor.
12 tools: 1 can delete or cancel things, 1 do something that can't be undone, 5 change things and 5 only read.
- Reads private data · 3
- Reads text others write · 3
- Can send data out · 1
- 6 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.
- 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 Perfboard Designer MCP server can do
The Perfboard Designer MCP server is published by perfboarddesigner.com, a domain the MCP Registry verified. It has 12 tools. It can delete or cancel things (1 tool: edit_project), do things that cannot be undone, such as sending, paying or publishing (render_board) and create or change data (5 tools: new_project, validate_project, get_nets, make_share_link and 1 more). 5 tools only read.
3 tools read private data (get_part, get_project and show_board); 3 tools bring in text other people can write (make_share_link, read_share_link and show_board); 1 tool can send data out of your system (render_board). 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 6 findings (tool-shadowing and 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 10, 2026, version 0.1.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.
12 tools
Deletes or cancels 1Claude Code: deny
edit_projectChanges a project kept here, by a list of ops applied in order: add_part, update_part (move, turn, change value or ref), remove_parts, add_wire (from/to, or a `path` of holes made …No findings
Why it is in this group
- The name "edit_project" says "edit": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Changes a project kept here, by a list of ops applied in order: add_part, update_part (move, turn, change value or ref), remove_parts, add_wire (from/to, or a `path` of holes made into one wire per leg), update_wire, remove_wires, set_board, add_cuts / remove_cuts (stripboard), set_pad (a note on a hole), set_description (what the board is and how it works, for whoever opens it). If any op can't be done, none are. Returns what changed, where the pins of added or moved parts landed, and the board checked as validate_project does (with any expectNets remembered for it); when it has no errors, also its nets. get_project returns the whole file. The goal is a board that's right, looks neat and is easy to solder, not just the shortest wires: parts in tidy rows near what they connect to, connectors at the edges, straight wires with few corners and no crossing you can avoid, none over a part's body. Before giving the user the link, look at it (render_board with format "png"), rework what's messy and check it again.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
Can't be undone 1Claude Code: ask
render_boardDraws the board as text, one cell per hole with column and row numbers: each part's pins by a key letter and pin number (a1, a2...), holes under a part's body, wire ends, the holes…Can send data out1 finding
Why it is in this group
- The input addresses people (input.area.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.area.to): what the tool writes goes there.
Findings
- Warn
The server marks "render_board" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The input addresses people (input.area.to): what it sends cannot be taken back.
Description, as the server wrote it Draws the board as text, one cell per hole with column and row numbers: each part's pins by a key letter and pin number (a1, a2...), holes under a part's body, wire ends, the holes a wire runs over without joining them, strip cuts and holes with notes. Below it, which part each key is and every wire with its ends and net. Use it to see where there's free space and how wires run before placing parts or routing more. With format "png", a picture of the board as the editor draws it instead, to see how it looks: parts' bodies and where they reach, labels, wire colours. To show the user the board, use show_board.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
Changes things 5Claude Code: ask
get_netsWhich pins the board connects: every net with its name (from its pins, e.g.1 finding
Why it is in this group
- The name "get_nets" says "get": a word for reading.
- The description's first verb is "pin": 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 "get_nets" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "get_nets" says "get": a word for reading.
Description, as the server wrote it Which pins the board connects: every net with its name (from its pins, e.g. GND), its pins ("U1.8 VCC" for a chip's pin, "D1.K" or "C1.+" for a polarized lead, "R1.1" otherwise) and the wires on it (indexes into wires). Also pins connected to nothing, wires that connect no pins, junctions (holes where three or more things are joined) and crossings (where a wire goes over another wire or over a hole without joining it). Wires are insulated jumpers: a wire joins only the holes at its two ends, so crossings are information, not connections or shorts. On a stripboard the strips connect too.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
new_projectStarts a project kept here under a projectId: a blank board, or one of the example projects (perfboard://examples/...) to copy from.1 finding
Why it is in this group
- The description's first verb is "start": a word for a change.
Findings
- Warn
The description contains "every other tool", wording about other tools or servers.
What this check looks forMatched text
description: "...edit_project, and pass the projectId to every other tool instead of the whole file."
Description, as the server wrote it Starts a project kept here under a projectId: a blank board, or one of the example projects (perfboard://examples/...) to copy from. Returns the projectId and the project file. Then add parts and wires with edit_project, and pass the projectId to every other tool instead of the whole file.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
validate_projectChecks a project file and lists every problem with where it is: entries the editor would leave out, unknown parts, pins off the board, two parts' pins or leads in one hole, overlap…2 findings
Why it is in this group
- The name "validate_project" says "validate": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The description contains "every other tool", wording about other tools or servers.
What this check looks forMatched text
description: "...the reply's projectId stands for it in every other tool."
- Warn
The server marks "validate_project" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "validate_project" says "validate": a word for reading.
Description, as the server wrote it Checks a project file and lists every problem with where it is: entries the editor would leave out, unknown parts, pins off the board, two parts' pins or leads in one hole, overlapping parts, wires that connect nothing (a loose end, or no pins on their net), duplicate wires, a two-lead part with both leads on one net (shorted out), a wire passing over a pin or lead without ending there (so not joined to it), IC pins and two-lead parts' leads connected to nothing, supply rails shorted together (a positive supply and ground, two different voltages, a battery's two terminals; VCC with 5V or GND with AGND is one rail), polarized parts in backwards (an LED, an electrolytic capacitor or + and − pins the wrong way round on the supply rails, or a diode conducting straight across the supply), and on a stripboard, pins shorted by a strip or sitting in a cut hole. The rails are pins named like VCC, GND or 5V, battery holders' terminals, and holes noted with a rail's name ("+9V"). With expectNets, every connection missing from the board or extra on it is an error. Enabled saved requirements also check intended connections, missing components/pins and unused pins; unspecified pins produce an incomplete-coverage warning, not a full match. Wires crossing each other are fine (insulated jumpers) and only listed in notes. Fix all errors before making a link. A project sent whole is kept here: the reply's projectId stands for it in every other tool.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
Only reads 5Show 5 read-only tools
get_partEverything needed to place parts: for each, which project file list it goes in, its pins (offsets from pin 1 at rotation 0) and pin labels, polarity, value unit, holes its body cov…Reads private dataNo findings
Why it is in this group
- The name "get_part" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
Description, as the server wrote it Everything needed to place parts: for each, which project file list it goes in, its pins (offsets from pin 1 at rotation 0) and pin labels, polarity, value unit, holes its body covers, and an example entry. Ask for every part you use in one call with `ids`.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_pin_positionsWhere every placed part's pins land, as [column, row] holes, with pin numbers and labels (e.g.No findings
Why it is in this group
- The name "get_pin_positions" says "get": a word for reading.
Description, as the server wrote it Where every placed part's pins land, as [column, row] holes, with pin numbers and labels (e.g. U1 pin 8 VCC), after rotation, plus holes a part's body covers. Use it to route wires to the right holes. The project file doesn't store these: they follow from each part's anchor, rotation and footprint.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_projectThe whole project file of a project kept here, as the editor would save it (through version 8, preserving component identities and optional requirements), one entry per line.Reads private dataNo findings
Why it is in this group
- The name "get_project" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
Description, as the server wrote it The whole project file of a project kept here, as the editor would save it (through version 8, preserving component identities and optional requirements), one entry per line.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
list_partsLists the parts a project can place.No findings
Why it is in this group
- The name "list_parts" says "list": a word for reading.
Description, as the server wrote it Lists the parts a project can place. Without a query: every part, grouped by category, as its id with its name and pin count; call it this way once to see what there is. With a query: the parts whose id, name, category or keywords contain all its words, or the closest ones when none do. Each part's `id` is its definitionId in the project file; use get_part for its pins and how to place it.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
show_boardShows the user a picture of the board right in the conversation, as the editor draws it, with a button that opens it in Perfboard Designer.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "show_board" says "show": a word for reading.
What it can reach
- private-dataThe description's first sentence says "show" and "conversation": it reads messages.
- untrusted-inputThe description's first sentence says "show" and "conversation": it reads messages, which other people can write.
Description, as the server wrote it Shows the user a picture of the board right in the conversation, as the editor draws it, with a button that opens it in Perfboard Designer. Only in clients that show MCP Apps (e.g. Claude, ChatGPT); elsewhere the user sees nothing, so give them make_share_link's link too. The picture goes to the user, not to you: to look at the board yourself, use render_board.
Annotations the server declares
- readOnlyHint: 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.
9 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 data3
- 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__perfboarddesigner__render_board"
]
}
}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 20, 2026, 18:44 UTC, unchanged since Oct 22, 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
- 7
- 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 7 tools that change things (1 destructive, 1 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.perfboarddesigner.com/mcp: tools/list returned 12 tools to an anonymous client, including edit_project (destructive), render_board (irreversible), new_project (write), validate_project (write), get_nets (write) and 2 more
Findings
Matches of fixed checks, with the text they matched.
- Warnnew_project
The description contains "every other tool", wording about other tools or servers.
What this check looks forMatched text
description: "...edit_project, and pass the projectId to every other tool instead of the whole file."
- Warnvalidate_project
The description contains "every other tool", wording about other tools or servers.
What this check looks forMatched text
description: "...the reply's projectId stands for it in every other tool."
- Warnvalidate_project
The server marks "validate_project" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "validate_project" says "validate": a word for reading.
- Warnget_nets
The server marks "get_nets" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "get_nets" says "get": a word for reading.
- Warnrender_board
The server marks "render_board" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The input addresses people (input.area.to): what it sends cannot be taken back.
- Warnread_share_link
The server marks "read_share_link" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":true}; The name "read_share_link" says "read": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:edit_projectDeletes or cancelsdescriptioninputSchema
- Changed:make_share_linkChanges thingsdescription
Tools9 changed.~9 changedView diff
- Changed:edit_projectDeletes or cancelsinputSchema
- Changed:get_netsChanges thingsinputSchema
- Changed:get_pin_positionsOnly readsinputSchema
- Changed:get_projectOnly readsdescription
- Changed:make_share_linkChanges thingsdescriptioninputSchema
- Changed:read_share_linkChanges thingsdescription
- Changed:render_boardCan't be undoneinputSchema
- Changed:show_boardOnly readsinputSchema
- Changed:validate_projectChanges thingsdescriptioninputSchema
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http perfboarddesigner https://mcp.perfboarddesigner.com/mcpclaude mcp add --transport http perfboarddesigner https://mcp.perfboarddesigner.com/mcpRun 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__perfboarddesigner__list_parts",
"mcp__perfboarddesigner__get_part",
"mcp__perfboarddesigner__get_project",
"mcp__perfboarddesigner__get_pin_positions",
"mcp__perfboarddesigner__show_board"
],
"ask": [
"mcp__perfboarddesigner__new_project",
"mcp__perfboarddesigner__validate_project",
"mcp__perfboarddesigner__get_nets",
"mcp__perfboarddesigner__render_board",
"mcp__perfboarddesigner__make_share_link",
"mcp__perfboarddesigner__read_share_link"
],
"deny": [
"mcp__perfboarddesigner__edit_project"
]
}
}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 perfboarddesigner. Review it before you use it.
Capability tags behind 6 rules
- mcp__perfboarddesigner__get_part private-data
- mcp__perfboarddesigner__get_project private-data
- mcp__perfboarddesigner__render_board outbound
- mcp__perfboarddesigner__make_share_link untrusted-input
- mcp__perfboarddesigner__read_share_link untrusted-input
- mcp__perfboarddesigner__show_board private-data, 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/com.perfboarddesigner/mcp/verify?hash=f84e25659c385b22c0257a9fa6de435fa5bea942d60f63bebd28c12a84072d43" | jq -e '.changed == false'Pinned hash f84e25659c38, from Nov 10, 2026, 23:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.perfboarddesigner/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.perfboarddesigner/mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:00 UTC.
Perfboard Designer MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Perfboard Designer MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 7 of which can change, send or delete something, and 6 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Perfboard Designer MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: edit_project.
Can the Perfboard Designer MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: render_board.
What tools does the Perfboard Designer MCP server have?
- 12 tools: 1 destructive, 1 irreversible, 5 write, 5 read. edit_project, render_board, new_project, validate_project, get_nets, make_share_link, read_share_link, list_parts and 4 more.
Does the Perfboard Designer MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Perfboard Designer 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): render_board.
Has the Perfboard Designer MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.