Skip to content

Picodev Lab MCP server

io.github.PICODEV-SAS/picodev-labPICODEV-SASstreamable-httpv0.11.0Scanned

Arduino benches simulated in the browser: sessions, sketch push, simulation, tests, challenges.

23 tools: 1 can delete or cancel things, 6 do something that can't be undone, 10 change things and 6 only read.

Tools: 1 delete, 6 irreversible, 10 write, 6 read.
  • Reads private data · 1
  • Reads text others write · 4
  • Can send data out · 1
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 6 do 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.
Govern this server →

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 Picodev Lab MCP server can do

The Picodev Lab MCP server is published by the GitHub account PICODEV-SAS. It has 23 tools. It can delete or cancel things (1 tool: close_session), do things that cannot be undone, such as sending, paying or publishing (decode_capture, push_program, capture_logic, capture_analog and 2 more) and create or change data (10 tools: open_session, push_to_editor, set_visibility, queue_join and 6 more). 6 tools only read.

1 tool reads private data (read_setup); 4 tools bring in text other people can write (read_simulation, session_status, brief_submit and 1 more); 1 tool can send data out of your system (decode_capture). 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 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.

Last scanned Nov 8, 2026, version 0.11.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.

23 tools

Deletes or cancels 1Claude Code: deny
  • close_sessionEnd the session now, as when it expires: the place or turn ends, viewers and the browser are disconnected, everything is forgotten.No findings

    Why it is in this group

    • The name "close_session" says "close": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    End the session now, as when it expires: the place or turn ends, viewers and the browser are disconnected, everything is forgotten.

    Annotations the server declares

    • destructiveHint: true
    • openWorldHint: false
    • readOnlyHint: false
Can't be undone 6Claude Code: ask
  • brief_submitSend Picodev the specification of the visitor's project, as a PDF, or only return its preview (send=false).Reads text others writeNo findings

    Why it is in this group

    • The name "brief_submit" 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.

    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
    Send Picodev the specification of the visitor's project, as a PDF, or only return its preview (send=false). sections: {id: text in simple Markdown}, ids envelope, fonctionPrincipale, fonctions, alimentation, format, environnement, production, preferences (the 8 sections of a product specification), 4000 characters at most each; a missing section reads "À préciser" (to be specified). send=false: preview, nothing is sent, contact and consent are not required. send=true: requires contact {name, email, company?, phone?} and consent=true. nda=true: the visitor wants a non-disclosure agreement first; without sections, only contact and title are sent, without PDF. session and agent_token, optional: the mail also says what the visitor did in the lab. language: fr or en, the PDF's headings. sections.contact and figures: as for spec_draft (refused with nda=true, as sections). Write the sections with spec_draft first. Before passing consent=true, show the visitor the consent text in the visitor's language, and wait until they accept it. In French: "J'accepte que mes coordonnées et la description de mon projet soient envoyées à Picodev par courriel, pour qu'ils me répondent. Picodev les garde 3 ans après le dernier échange et ne les utilise pour rien d'autre. Détails : lab.picodev.fr/confidentialite" In English: "I agree that my contact details and the description of my project are sent to Picodev by e-mail, so that they can answer me. Picodev keeps them for 3 years after our last exchange and uses them for nothing else. Details: lab.picodev.fr/en/privacy" Returns {sent, filename, pdf (base 64, absent with nda), missing (empty or too short sections), next (a sentence for the visitor, to say in their language)}}: write the PDF on the visitor's machine.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: true
    • readOnlyHint: false
  • capture_analogSample the voltage of 1 to 4 board pins (the board's own numbers: Nano A0-A7 = 14-21, Uno A0-A5 = 14-19, Mega A0-A15 = 54-69; by default the setup's scope probes) at rate_hz (100 t…No findings

    Why it is in this group

    • The name "capture_analog" says "capture": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Sample the voltage of 1 to 4 board pins (the board's own numbers: Nano A0-A7 = 14-21, Uno A0-A5 = 14-19, Mega A0-A15 = 54-69; by default the setup's scope probes) at rate_hz (100 to 10 000) for duration_ms (1 to 10 000 simulated ms), 200 000 samples at most in all. An ADC input reads the voltage the circuit applies; any other pin, its logic level times the supply (PWM shows as a square wave). Simulation only: refused during a turn on a real bench, whose analyser has no analog channel. Read the result with read_capture.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • capture_logicRecord every edge of the requested pins (probes of the setup sheet; by default the logic ones) for duration_ms (1 to 10 000 ms).No findings

    Why it is in this group

    • The name "capture_logic" says "capture": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Record every edge of the requested pins (probes of the setup sheet; by default the logic ones) for duration_ms (1 to 10 000 ms). In the browser's simulation, in simulated time; during the session's turn on a real bench, at the bench's logic analyser, in real time (no browser or running simulation needed then). trigger {pin, edge}: pin among pins, edge rising, falling or any; the recording then lasts wait_ms + duration_ms (10 000 ms at most) and keeps pre_ms (0 to wait_ms) before the first matching edge within wait_ms and duration_ms after it; with no such edge, the whole recording. Read the result with read_capture, decode it with decode_capture.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • decode_captureDecode a ready logic capture of the session (browser or bench).Can send data out1 finding

    Why it is in this group

    • The name "decode_capture" says "capture": a word that usually means money moves, which 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.channels): what the tool writes goes there.

    Findings

    • Warn

      The server marks "decode_capture" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "decode_capture" says "capture": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Decode a ready logic capture of the session (browser or bench). protocol "uart" with channels {rx} and options {baud (300-1000000, 9600), bits (5-9, 8), parity (none, even, odd), stop (1, 2), invert (false)}; "spi" with {sck, mosi?, miso?, cs?} (one data pin at least) and options {mode (0-3, 0), bit_order (msb, lsb), bits (8)}; "i2c" with {scl, sda}. channels are pins of the capture. Returns {capture, protocol, frames, next, problems}, 2000 frames from offset. uart frames {t_us, value, error?} (framing, parity) and text, the printable bytes of the page; spi {t_us, mosi?, miso?} per word, while cs is low when given; i2c {t_us, kind (start, restart, address, data, stop), value?, rw?, ack?}. problems: what makes the decoding doubtful.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • push_programSend a program compiled on the visitor's machine (Intel HEX text, 48 KiB at most, e.g.No findings

    Why it is in this group

    • The name "push_program" says "push": a word for a change.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
    Description, as the server wrote it
    Send a program compiled on the visitor's machine (Intel HEX text, 48 KiB at most, e.g. arduino-cli's <sketch>.ino.hex) to the human's browser, which loads it in the simulator without compiling and, if run, starts it. files: the sources, shown read-only in the editor, never compiled. During a turn on a real bench, the bench gets it too. Prefer it to push_to_editor, which is the fallback when the local toolchain is missing.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • request_meetingSend Picodev a meeting request.Reads text others writeNo findings

    Why it is in this group

    • The name "request_meeting" 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
    Send Picodev a meeting request. contact: {name, email, company?, phone?}. context: the project in a few sentences (2000 characters at most): what the visitor wants to do, where they stand, what they did in the lab. availabilities: 1 to 10 slots {from, to}, ISO 8601 dates with a time zone, within the next 60 days; or {text}, one sentence ("Tuesday mornings"). Requires consent=true. session and agent_token, optional: the mail also says what the visitor did in the lab. Before passing consent=true, show the visitor the consent text in the visitor's language, and wait until they accept it. In French: "J'accepte que mes coordonnées et la description de mon projet soient envoyées à Picodev par courriel, pour qu'ils me répondent. Picodev les garde 3 ans après le dernier échange et ne les utilise pour rien d'autre. Détails : lab.picodev.fr/confidentialite" In English: "I agree that my contact details and the description of my project are sent to Picodev by e-mail, so that they can answer me. Picodev keeps them for 3 years after our last exchange and uses them for nothing else. Details: lab.picodev.fr/en/privacy" Returns {sent, next}: Picodev answers by e-mail to confirm a slot.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: true
    • readOnlyHint: false
Changes things 10Claude Code: ask
  • bench_snapshotDuring the session's turn on a real bench: a photo of the bench, as an image, and t_ms, the instant of the photo in ms since the start of the turn (null when unknown).1 finding

    Why it is in this group

    • The name "bench_snapshot" says "snapshot": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "bench_snapshot" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "bench_snapshot" says "snapshot": a word for reading.

      What this check looks for
    Description, as the server wrote it
    During the session's turn on a real bench: a photo of the bench, as an image, and t_ms, the instant of the photo in ms since the start of the turn (null when unknown). One every 2 seconds.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • next_levelChallenge mode: move to the next level, as the bench's "Next level" button, and only when it would be offered: every test of the current level passed and a next level exists.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
    Challenge mode: move to the next level, as the bench's "Next level" button, and only when it would be offered: every test of the current level passed and a next level exists. Returns {level, levels}, the new level (index); session_status's level changes with the bench's next state. No level skipping.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • open_sessionCreate a session (mode: free or challenge).No findings

    Why it is in this group

    • The name "open_session" says "open": a word for a change.
    Description, as the server wrote it
    Create a session (mode: free or challenge). Give open_url to the human: nothing simulates until they open it in their browser.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • push_circuitFree mode only: replace the circuit in the human's browser (the simulation stops).No findings

    Why it is in this group

    • The name "push_circuit" says "push": a word for a change.
    Description, as the server wrote it
    Free mode only: replace the circuit in the human's browser (the simulation stops). components: [{type, id, properties, x?, y?}] (the board is not a component), wires: [{id, start: {componentId, pinName}, end: {...}, color?, waypoints?: [{x, y}] (the wire's route, 16 points at most)}], in the shape of the setup sheet's circuit; 40 components, 120 wires, 48 KiB. The editor checks types and pins: read the outcome with read_simulation (circuit, circuit_error). 6 per minute.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • push_to_editorReplace the code in the human's browser and, if run, compile it in the lab's cloud and start it.No findings

    Why it is in this group

    • The name "push_to_editor" says "push": a word for a change.
    Description, as the server wrote it
    Replace the code in the human's browser and, if run, compile it in the lab's cloud and start it. The fallback of push_program: use it only when the toolchain to compile locally is missing (no arduino-cli, core or library).

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • queue_joinTake a place in the queue for benches of this kind (for example real or sim).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
    Take a place in the queue for benches of this kind (for example real or sim). The browser must be connected.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • queue_leaveGive back the place in the queue, or the turn if it has started.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
    Give back the place in the queue, or the turn if it has started.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • set_visibilityChange the visibility (private, link, public).No findings

    Why it is in this group

    • The name "set_visibility" says "set": a word for a change.
    Description, as the server wrote it
    Change the visibility (private, link, public). Returns the viewer link; current viewers are disconnected.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • spec_draftDraft the specification of the visitor's own project with Picodev's interview: you ask the visitor, this tool says what to ask next and makes the PDF.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
    Draft the specification of the visitor's own project with Picodev's interview: you ask the visitor, this tool says what to ask next and makes the PDF. Nothing is sent and nothing is kept. Call it with the sections written so far (none at first). sections: {id: text in simple Markdown}, ids envelope, fonctionPrincipale, fonctions, alimentation, format, environnement, production, preferences, 4000 characters at most each. sections.contact, optional: the contact details the visitor wants printed at the end of the document (1000 characters at most; not part of the interview's progress). language: fr or en, the one the visitor answers in (headings, look_for and questions, the PDF). pdf=true: also the PDF, with Picodev Lab's template; requires title (one line). figures, with pdf=true, optional: the drawings the visitor approved, 3 at most, each {section (a section id), caption (one line), type (png or svg), data (base 64, 200 KiB at most decoded)}, placed after their section's text; an SVG loads nothing (no script, no DTD, href # or data:image/ only). Returns {rules (how to run the interview: follow them), sections [{id, heading, required, state (empty, thin, filled), look_for and questions while not filled}], next (the section to ask about, or null), ready (the four required sections filled: enough for Picodev to start), filename and pdf (base 64) with pdf=true}.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • submit_answerChallenge mode: propose `value` as the answer of the current level's test `test` (an answer test of the level's brief).No findings

    Why it is in this group

    • The name "submit_answer" says "submit": a word for a change.
    Description, as the server wrote it
    Challenge mode: propose `value` as the answer of the current level's test `test` (an answer test of the level's brief). One answer per second at most. The hub checks it and returns {test, ok}; the verdict is also shown in the bench. For a hint, ask the visitor to reveal one in the bench.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: false
Only reads 6Show 6 read-only tools
  • list_setupsThe setups: status available (open_session works) or soon (listed, cannot be opened yet), their modes (free, challenge) and their benches by kind (status open, or soon: not offered…No findings

    Why it is in this group

    • The name "list_setups" says "list": a word for reading.
    Description, as the server wrote it
    The setups: status available (open_session works) or soon (listed, cannot be opened yet), their modes (free, challenge) and their benches by kind (status open, or soon: not offered yet).

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • queue_statusThe session's place: state none, waiting (position, estimated wait eta_s) or turn (bench, end of the turn ends_at, Unix seconds).No findings

    Why it is in this group

    • The name "queue_status" says "status": a word for reading.
    Description, as the server wrote it
    The session's place: state none, waiting (position, estimated wait eta_s) or turn (bench, end of the turn ends_at, Unix seconds).

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • read_captureState of a capture (recording, ready, failed) and its kind (logic, analog).No findings

    Why it is in this group

    • The name "read_capture" says "read": a word for reading.
    Description, as the server wrote it
    State of a capture (recording, ready, failed) and its kind (logic, analog). Once ready, the measures per pin and, for a logic capture, the edges [t_us, pin, v], 2000 from offset; for an analog one, rate_hz and the samples, rows [mv_1, ...] in the order of pins (row k at k / rate_hz), 2000 rows from offset. next: the following offset, or null. t0_ms: the first sample on the session's clock (ms since the simulation's launch, or since the start of the turn on a real bench), null when unknown; t_us and rows count from the capture's start. format="png": the same without edges or samples, plus a chart of the signals as an image (from_ms and to_ms, from the capture's start, to zoom; 4 per minute).

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • read_setupA served setup sheet (setup.json, files included; never a solution): board, components and wires (circuit), probes, levels (without their hints: hints come through read_simulation …Reads private dataNo findings

    Why it is in this group

    • The name "read_setup" says "read": 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
    A served setup sheet (setup.json, files included; never a solution): board, components and wires (circuit), probes, levels (without their hints: hints come through read_simulation as the visitor reveals them). Plus, when it exists, schema.png, the starting circuit as the editor draws it, as an image.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • read_simulationLast state (with circuit, the browser's components and wires), last compilation and the events after since_ms (2000 at most).Reads text others writeNo findings

    Why it is in this group

    • The name "read_simulation" says "read": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "browser": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Last state (with circuit, the browser's components and wires), last compilation and the events after since_ms (2000 at most). `serial` is the full serial output of the current run (up to 16 KiB), reset at each compile and NOT starved by pin events: prefer it over reconstructing serial from `events`. During a turn on a real bench, `serial` and the serial events come from the bench's board (since the turn began or the last compile), `t` on the turn's clock. In challenge mode: the level's brief and its results. circuit_modified: the circuit differs from the setup sheet's (types, ids, properties, wires; not positions or colours), null when unknown. circuit_error: the editor's last refusal of a pushed circuit, returned once.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • session_statusThe session's state without its events, cheap enough to poll: browser connected (owner), visibility, current viewer link (not renewed), viewers, created_at and expires_at (Unix sec…Reads text others writeNo findings

    Why it is in this group

    • The name "session_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "browser": it reads web pages, which anyone can write.
    Description, as the server wrote it
    The session's state without its events, cheap enough to poll: browser connected (owner), visibility, current viewer link (not renewed), viewers, created_at and expires_at (Unix seconds), run (compilations so far: event times restart at each), level and levels (null in free mode), capture ({id, kind, state} of the session's capture, logic or analog, or null). Not reported to the human's journal.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true

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.

4 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 write4
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.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__picodev-lab__decode_capture"
    ]
  }
}

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.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:59 UTC, unchanged since Oct 29, 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
17
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 17 tools that change things (1 destructive, 6 irreversible, 10 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://lab.picodev.fr/mcp: tools/list returned 23 tools to an anonymous client, including close_session (destructive), decode_capture (irreversible), push_program (irreversible), capture_logic (irreversible), capture_analog (irreversible) and 12 more

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • Tools that change things, listed without credentials: 15 to 17

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "decode_capture" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "decode_capture" says "capture": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "bench_snapshot" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":false}; The name "bench_snapshot" says "snapshot": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 15 -> 17.View diff
    • Tools that change things, listed without credentials: 15 to 17
  3. Tools1 added, 2 changed.+1 added~2 changedView diff
  4. Tools1 added, 16 changed.+1 added~16 changedView diff

Install

Pinned to version 0.11.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http picodev-lab https://lab.picodev.fr/mcp
claude mcp add --transport http picodev-lab https://lab.picodev.fr/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__picodev-lab__list_setups",
      "mcp__picodev-lab__read_simulation",
      "mcp__picodev-lab__queue_status",
      "mcp__picodev-lab__session_status",
      "mcp__picodev-lab__read_capture",
      "mcp__picodev-lab__read_setup"
    ],
    "ask": [
      "mcp__picodev-lab__decode_capture",
      "mcp__picodev-lab__open_session",
      "mcp__picodev-lab__push_to_editor",
      "mcp__picodev-lab__push_program",
      "mcp__picodev-lab__set_visibility",
      "mcp__picodev-lab__queue_join",
      "mcp__picodev-lab__queue_leave",
      "mcp__picodev-lab__submit_answer",
      "mcp__picodev-lab__next_level",
      "mcp__picodev-lab__capture_logic",
      "mcp__picodev-lab__capture_analog",
      "mcp__picodev-lab__push_circuit",
      "mcp__picodev-lab__bench_snapshot",
      "mcp__picodev-lab__spec_draft",
      "mcp__picodev-lab__brief_submit",
      "mcp__picodev-lab__request_meeting"
    ],
    "deny": [
      "mcp__picodev-lab__close_session"
    ]
  }
}

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 picodev-lab. Review it before you use it.

Capability tags behind 6 rules
  • mcp__picodev-lab__decode_capture outbound
  • mcp__picodev-lab__read_simulation untrusted-input
  • mcp__picodev-lab__session_status untrusted-input
  • mcp__picodev-lab__read_setup private-data
  • mcp__picodev-lab__brief_submit untrusted-input
  • mcp__picodev-lab__request_meeting 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/io.github.PICODEV-SAS/picodev-lab/verify?hash=1412bcb18953ec166b236b37ab2adea2a42a1e9516e00471328f08ba75a3f36f" | jq -e '.changed == false'

Pinned hash 1412bcb18953, from Nov 8, 2026, 21:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.PICODEV-SAS/picodev-lab/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.PICODEV-SAS/picodev-lab
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.PICODEV-SAS/picodev-lab.svg)](https://radar.anlyon.com/servers/io.github.PICODEV-SAS/picodev-lab)

Source: MCP Registry · repository. Synced Oct 23, 2026, 14:20 UTC.

Picodev Lab MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Picodev Lab MCP server safe?

No scan can promise that. What its definitions show: 23 tools, 17 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 Picodev Lab MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: close_session.

Can the Picodev Lab MCP server do things that cannot be undone?

Yes. 6 tools can send, pay, publish or merge: decode_capture, push_program, capture_logic, capture_analog, brief_submit and request_meeting.

What tools does the Picodev Lab MCP server have?

23 tools: 1 destructive, 6 irreversible, 10 write, 6 read. close_session, decode_capture, push_program, capture_logic, capture_analog, brief_submit, request_meeting, open_session and 15 more.

Does the Picodev Lab MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Picodev Lab 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): decode_capture.

Has the Picodev Lab MCP server changed its tools?

Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.