EasyGerber: AI PCB design, layout, and routing MCP server
io.github.EasyGerber/easygerberEasyGerberstreamable-httpv0.1.1Scanned
AI PCB design, layout, and routing
16 tools: 5 can delete or cancel things, 1 do something that can't be undone, 3 change things and 7 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools 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 EasyGerber: AI PCB design, layout, and routing MCP server can do
The EasyGerber: AI PCB design, layout, and routing MCP server is published by the GitHub account EasyGerber. It has 16 tools. It can delete or cancel things (5 tools: save_board_to_account, update_board, delete_board, generate_layout and 1 more), do things that cannot be undone, such as sending, paying or publishing (submit_feedback) and create or change data (3 tools: create_board, check_board_layout and export_board). 7 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 2 findings (credentials-mention and long-description). 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 15, 2026, version 0.1.1.
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.
16 tools
Deletes or cancels 5Claude Code: deny
delete_boardPermanently deletes the specified saved account board when the user requests its removal.No findings
Why it is in this group
- The name "delete_board" says "delete": a word for removing or ending something.
- The description says "Permanently deletes".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Permanently deletes the specified saved account board when the user requests its removal. Requires explicit boards:delete authorization and personal ownership or organization owner/admin access; guest boards are unsupported. Read get_board first and pass its current revision. Deletion cancels active generation jobs and cannot be undone. A revision conflict requires reading the board again. Missing, already deleted or inaccessible boards return the same not_found error; this does not confirm that an earlier request succeeded. No requestId or replay receipt is supported.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
- title: Permanently delete an account board
generate_layoutStarts one durable layout job for boardRef at expectedRevision and returns generation.id and generation.status without waiting.No findings
Why it is in this group
- The name "generate_layout" says "generate": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Starts one durable layout job for boardRef at expectedRevision and returns generation.id and generation.status without waiting. create_board and update_board start layout automatically, so call this only to retry: after a failed or cancelled layout, after a save returned layoutNotStarted, or to regenerate a current layout. If a layout of that same revision is already running or was just saved, returns that job instead of starting another. Use the latest revision from get_generation or get_board. Read status with get_generation using the same boardRef; do not regenerate to inspect progress. Successful completion replaces the saved layout. A requestId supports IDENTICAL retries only; changed arguments need a new requestId. revision_conflict requires get_board; board_busy identifies the existing job to poll. Subject to normal compute capacity and board complexity limits, without AI credits.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
- title: Generate PCB layout
save_board_to_accountSaves a private board into the connected EasyGerber account when the user asks to keep it there.No findings
Why it is in this group
- The name "save_board_to_account" says "save": a word for a change.
- The description says "cannot be undone".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Saves a private board into the connected EasyGerber account when the user asks to keep it there. Requires account authorization; an unauthenticated call requests sign-in. Supply the same boardRef. The board must have no layout running: wait for get_generation to finish, then retry. Saving copies the design and its layout into a personal account board and retires the anonymous access, which cannot be undone. The result is that account board, with a new id and revision to use from now on. Keep the same boardRef; after a save it works only while this account is connected. A board already in the account is returned unchanged.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
- title: Save board to account
stop_generationCancels a queued or running layout generation belonging to the specified board; use get_generation when only checking progress.No findings
Why it is in this group
- The name "stop_generation" says "stop": a word for a change.
- The description's first verb is "cancel": a word for removing or ending something.
- The description says "cannot be undone".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Cancels a queued or running layout generation belonging to the specified board; use get_generation when only checking progress. A completed, failed or already cancelled job retains its terminal status. Cancellation cannot be undone; starting again requires a new job. It can update the saved board revision, so read get_board before further edits. A later job is unaffected.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
- title: Stop generation
update_boardEdits a saved board at expectedRevision; supply at least one of name, intent or boardEdits.No findings
Why it is in this group
- The name "update_board" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Edits a saved board at expectedRevision; supply at least one of name, intent or boardEdits. Read get_board first. Omitted fields are preserved; schematic edits require the complete replacement thin intent, while boardEdits is a physical patch. Schematic changes discard the old layout and physical changes make it stale; either way this save starts a new layout automatically and returns it as generation. Follow it with get_generation, without calling generate_layout. An edit made while a layout is running replaces that job with one for the edited board. If layoutNotStarted is returned instead, the edit is saved but its layout did not start; call generate_layout after any stated wait. A stale expectedRevision requires a fresh get_board; a completed layout also advances the revision. Thin intent format: each parts entry is an array of strings [id, dbId, value], with an optional fourth designator. Choose id as the design-local part ID; copy dbId from the catalog result's id; value is the required value/display label. Omit the fourth designator when it matches id. Each connections entry is {net, class, pins}; class is power, signal, or ground. Each pins entry is [partId, padId]: use the design-local part ID and copy padId from the catalog result's pins[].number, both as strings. Optional pinCurrentRequirements uses those same partId and padId identities with requiredCurrentA in amperes and direction into, out, or bidirectional relative to the net. Omit the list to retain existing values; a supplied list replaces it, and [] clears it. If validation rejects the proposal, preserve the schematic and valid catalog parts, correct the returned detailed issues, and keep the same boardRef. Use a new requestId when input changes; reuse the same requestId and arguments for an unchanged retry. Research again only when an issue needs missing part or pin information.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
- title: Edit board
Can't be undone 1Claude Code: ask
submit_feedbackSends a bug report, feature request or general feedback to EasyGerber only when the user asks or agrees to report it.1 finding
Why it is in this group
- The name "submit_feedback" says "submit": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
Findings
- Info
The input schema at properties.message.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.message.description: "...atically include private board content, credentials, transcripts or diagnostics."
Description, as the server wrote it Sends a bug report, feature request or general feedback to EasyGerber only when the user asks or agrees to report it. Send only the approved message; never automatically attach private board content, raw diagnostics, transcripts or exports. No account, board or guest session is required. A connected account attributes the report to that account; otherwise an optional existing guestToken attributes it to that guest. Reuse requestId with the identical category and message on retries. Returns a submission receipt, without promising a response. Account feedback is limited to 10/hour and 50/day; guest and anonymous feedback share those limits by network.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Submit EasyGerber feedback
Changes things 3Claude Code: ask
check_board_layoutChecks a saved PCB layout at expectedRevision for manufacturing or layout review.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.
Description, as the server wrote it Checks a saved PCB layout at expectedRevision for manufacturing or layout review. Its geometry and applied electrical requirements must both be current. A missing or stale layout must complete first: follow the job a save started with get_generation, or call generate_layout when none is active. electrical_requirements_not_applied also requires a completed regeneration before checking or manufacturing export. Reuses a current assessment or computes and saves one, which requires write access and normal compute capacity. If the board changes during the check, read get_board again. Returns hasBlockingIssues and actionable blockingIssues; no numeric score or deductions.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Check PCB layout for blocking issues
create_boardCreates a saved schematic from published catalog parts and verified pins, and starts its PCB layout automatically.1 finding
Why it is in this group
- The name "create_board" says "create": a word for a change.
Findings
- Info
The description is 2,617 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...d retry. Research again only when an issue needs missing part or pin information."
Description, as the server wrote it Creates a saved schematic from published catalog parts and verified pins, and starts its PCB layout automatically. Supply a fresh private boardRef, name, requestId and intent. To make boardRef, generate 32 random bytes locally, encode as unpadded base64url and prepend egbr1_. The server uses the connected account when available; otherwise it establishes private board access automatically. Keep this SAME boardRef for all later reads, edits, status and export calls. Store it in this conversation or supported private execution state before submitting; do not discard it between isolated calls. Identical retries with the same boardRef, requestId and arguments recover the original creation. Do not use a new reference to recover existing work. Return the complete private board link to this user after creation so later turns can continue it; never log private references or put them in source files. Omit boardEdits unless physical customization is requested; server defaults supply settings, footprints, models and manufacturing limits. Account boards are personal unless organizationId is specified. The result includes generation, the layout job this save started: follow it with get_generation using the same boardRef, without calling generate_layout. If layoutNotStarted is returned instead, the board is saved but its layout did not start; call generate_layout after any stated wait. A completed layout saves a new revision, so use boardRevision from get_generation for later edits. Use update_board for existing work. Thin intent format: each parts entry is an array of strings [id, dbId, value], with an optional fourth designator. Choose id as the design-local part ID; copy dbId from the catalog result's id; value is the required value/display label. Omit the fourth designator when it matches id. Each connections entry is {net, class, pins}; class is power, signal, or ground. Each pins entry is [partId, padId]: use the design-local part ID and copy padId from the catalog result's pins[].number, both as strings. Optional pinCurrentRequirements uses those same partId and padId identities with requiredCurrentA in amperes and direction into, out, or bidirectional relative to the net. Omit the list to retain existing values; a supplied list replaces it, and [] clears it. If validation rejects the proposal, preserve the schematic and valid catalog parts, correct the returned detailed issues, and keep the same boardRef. Use a new requestId when input changes; reuse the same requestId and arguments for an unchanged retry. Research again only when an issue needs missing part or pin information.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Create board
export_boardCreates a stable private download of a saved board as a manufacturing ZIP or editable .egb project backup.No findings
Why it is in this group
- The description's first verb is "create": a word for a change.
Description, as the server wrote it Creates a stable private download of a saved board as a manufacturing ZIP or editable .egb project backup. Read get_board for expectedRevision. Use format egb directly for project backups, including empty or incomplete projects and unapplied geometry or electrical changes; no layout generation or check is required. Manufacturing ZIPs require a current saved layout with applied electrical requirements; generate and wait for completion when needed, then read the new revision. New exports require current board access. Issued download links have no automatic expiry and retain this exact export after board edits, deletion, guest claim or cleanup. Only explicit download-link revocation or deletion of the exported file ends access. Keep each complete private URL unchanged, including its fragment; anyone with it can download the file.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- title: Export board files
Only reads 7Show 7 read-only tools
get_boardReads the current revision, thin schematic, supported settings, physical context, layout freshness and latest layout job from one saved-state snapshot.No findings
Why it is in this group
- The name "get_board" says "get": a word for reading.
Description, as the server wrote it Reads the current revision, thin schematic, supported settings, physical context, layout freshness and latest layout job from one saved-state snapshot. Reading never saves or moves a board: a private board has ownerUserId null and a private link as url, while a board in an account has an owner and a /boards/ url; use save_board_to_account to keep a private board in the connected account. Use the same boardRef before editing, checking or exporting. A completed older job does not imply a current layout. Use get_generation with boardRef for status, never generate_layout as a status probe. includePreview optionally adds a saved-layout image; previewing does not change the board design or revision. Normal compute capacity limits apply.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Read board
get_generationReads stored layout generation status using the same boardRef.No findings
Why it is in this group
- The name "get_generation" says "get": a word for reading.
Description, as the server wrote it Reads stored layout generation status using the same boardRef. Omit generationId to read the active/latest layout job; supply it only to inspect that exact job. Returns generation:null if no layout job exists. While queued or running, wait pollAfterSeconds; stop polling at completed, failed or cancelled. boardRevision is the current saved revision, which a completed layout advances; use it for the next edit, check or export, or read get_board for the saved layout. Never call generate_layout to inspect status. Polling does not save private work to an account.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Read generation status
get_partReturns a published catalog part and verified pins.No findings
Why it is in this group
- The name "get_part" says "get": a word for reading.
Description, as the server wrote it Returns a published catalog part and verified pins. Skip this call when search_parts already supplied the needed pins and facts. Use the selected catalog result’s id; returned pins[].number is the padId used in board connections. Use search_parts to find alternatives. factQuery and factOffset select or page cached datasheet facts. An optional boardRef applies that board’s strict Part List restriction, when enabled.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Get part and pins
get_profileReturns the connected account identity.No findings
Why it is in this group
- The name "get_profile" says "get": a word for reading.
Description, as the server wrote it Returns the connected account identity. Requires account authorization; unauthenticated calls request OAuth. Public catalog browsing and creating a new board do not require probing account identity.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Get EasyGerber profile
list_boardsLists accessible boards with their private boardRef, most recently updated first.No findings
Why it is in this group
- The name "list_boards" says "list": a word for reading.
Description, as the server wrote it Lists accessible boards with their private boardRef, most recently updated first. A supplied boardRef selects only that board. Account access returns personal boards unless organizationId is specified. Without access, returns guidance, not a claim that an account has no boards. Continue existing work using its original boardRef or owning account. Continue with nextOffset until null, then use get_board for the selected board.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: List boards
list_organizationsReturns the connected account’s organizations and membership roles.No findings
Why it is in this group
- The name "list_organizations" says "list": a word for reading.
Description, as the server wrote it Returns the connected account’s organizations and membership roles. Requires account authorization. Use the returned organizationId with list_boards or create_board for organization work; omit organizationId for personal boards.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: List organizations
search_partsSearches published catalog components.No findings
Why it is in this group
- The name "search_parts" says "search": a word for reading.
Description, as the server wrote it Searches published catalog components. Supply known catalog filters such as category and exact package. Use query for the remaining terms or exact MPN. Put electrical bounds and applicable test conditions in requirements. Use forwardVoltage for LED Vf. Use candidateIds to check previously found parts under the same constraints. Reuse a qualified candidate’s catalog ID. On mismatch, check the next candidate. For unknown, verify the exact part’s datasheet at the required conditions or leave the requirement unresolved. The first candidate includes verified pins when available; other candidates may omit them. Reuse returned IDs, pins and facts; call get_part only when the selected candidate lacks needed pins or facts. factQuery selects cached facts for the matching candidates. Include boardRef on every lookup for a board with a strict Part List. If results are unrelated, make at most two retries with simpler text, preserving every required filter, specification and board restriction. If none qualifies, report the unmet requirement.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Search published parts
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.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
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:57 UTC, unchanged since Nov 6, 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
- 9
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://www.easygerber.com/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://www.easygerber.com/api/auth
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 9 tools that change things (5 destructive, 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://www.easygerber.com/api/mcp: tools/list returned 16 tools to an anonymous client, including save_board_to_account (destructive), update_board (destructive), delete_board (destructive), generate_layout (destructive), stop_generation (destructive) and 4 more
Posture changes
- Nov 6, 2026
- Tools that change things, listed without credentials: 11 to 9
Findings
Matches of fixed checks, with the text they matched.
- Infosubmit_feedback
The input schema at properties.message.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.message.description: "...atically include private board content, credentials, transcripts or diagnostics."
- Infocreate_board
The description is 2,617 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...d retry. Research again only when an issue needs missing part or pin information."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added, 2 removed, 13 changed.+1 added−2 removed~13 changedView diff
- Added:save_board_to_accountDeletes or cancels
- Removed:claim_guest_board
- Removed:start_guest_session
- Changed:check_board_layoutChanges thingsdescriptioninputSchema
- Changed:create_boardChanges thingsdescriptioninputSchema
- Changed:delete_boardDeletes or cancelsinputSchema
- Changed:export_boardChanges thingsdescriptioninputSchema
- Changed:generate_layoutDeletes or cancelsdescriptioninputSchema
- Changed:get_boardOnly readsdescriptioninputSchemaannotations
- Changed:get_generationOnly readsdescriptioninputSchema
- Changed:get_partOnly readsdescriptioninputSchema
- Changed:get_profileOnly readsdescription
- Changed:list_boardsOnly readsdescriptioninputSchema
- Changed:search_partsOnly readsdescriptioninputSchema
- Changed:stop_generationDeletes or cancelsdescriptioninputSchema
- Changed:update_boardDeletes or cancelsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 11 -> 9.View diff
- Tools that change things, listed without credentials: 11 to 9
Tools9 changed.~9 changedView diff
- Changed:check_board_layoutChanges thingsdescriptioninputSchema
- Changed:create_boardChanges thingsdescriptioninputSchema
- Changed:delete_boardDeletes or cancelsinputSchema
- Changed:export_boardChanges thingsdescription
- Changed:generate_layoutDeletes or cancelsdescriptioninputSchema
- Changed:get_partOnly readsdescriptioninputSchema
- Changed:search_partsOnly readsdescriptioninputSchema
- Changed:start_guest_sessionChanges thingsdescription
- Changed:update_boardDeletes or cancelsdescriptioninputSchema
Install
Pinned to version 0.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http easygerber https://www.easygerber.com/api/mcpclaude mcp add --transport http easygerber https://www.easygerber.com/api/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__easygerber__get_profile",
"mcp__easygerber__list_organizations",
"mcp__easygerber__search_parts",
"mcp__easygerber__get_part",
"mcp__easygerber__list_boards",
"mcp__easygerber__get_board",
"mcp__easygerber__get_generation"
],
"ask": [
"mcp__easygerber__submit_feedback",
"mcp__easygerber__create_board",
"mcp__easygerber__check_board_layout",
"mcp__easygerber__export_board"
],
"deny": [
"mcp__easygerber__save_board_to_account",
"mcp__easygerber__update_board",
"mcp__easygerber__delete_board",
"mcp__easygerber__generate_layout",
"mcp__easygerber__stop_generation"
]
}
}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 easygerber. Review it before you use it.
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/io.github.EasyGerber/easygerber/verify?hash=6ac5480bb86fa9f0277eba4c881d84abb208510b404e667f00bc7d3b7141354d" | jq -e '.changed == false'Pinned hash 6ac5480bb86f, from Nov 15, 2026, 19:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.EasyGerber/easygerber/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.EasyGerber/easygerber)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:15 UTC.
EasyGerber: AI PCB design, layout, and routing MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the EasyGerber: AI PCB design, layout, and routing MCP server safe?
- No scan can promise that. What its definitions show: 16 tools, 9 of which can change, send or delete something, and 2 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 EasyGerber: AI PCB design, layout, and routing MCP server delete data?
- Yes. 5 tools can delete, cancel or revoke something: save_board_to_account, update_board, delete_board, generate_layout and stop_generation.
Can the EasyGerber: AI PCB design, layout, and routing MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: submit_feedback.
What tools does the EasyGerber: AI PCB design, layout, and routing MCP server have?
- 16 tools: 5 destructive, 1 irreversible, 3 write, 7 read. save_board_to_account, update_board, delete_board, generate_layout, stop_generation, submit_feedback, create_board, check_board_layout and 8 more.
Does the EasyGerber: AI PCB design, layout, and routing MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the EasyGerber: AI PCB design, layout, and routing MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the EasyGerber: AI PCB design, layout, and routing MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.