Skip to content

MagicON RF Design Engines MCP server

io.github.magiccadai/magiconmagiccadaistreamable-httpv1.1.0Scanned

TX/RX/T-R chains, OTA link, radar, PCB filters, patch antennas, stackup, thermal, PDN, compliance.

19 tools: 16 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 16 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 12 findings

Tools listed without sign-in. Remote posture

With Anlyon

16 tools here change things. 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 MagicON RF Design Engines MCP server can do

The MagicON RF Design Engines MCP server is published by the GitHub account magiccadai. It has 19 tools. It can create or change data (16 tools: design_rf_chain, design_rf_receiver, design_tr_module, run_link_budget and 12 more), but cannot delete data. 3 tools only read.

1 tool brings in text other people can write (compare_rf_chains).

The fixed checks matched 12 findings (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 21, 2026, version 1.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.

19 tools

Changes things 16Claude Code: ask
  • check_groundingCheck a draft passage against the engine results computed in THIS session.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
    Check a draft passage against the engine results computed in THIS session. It returns every figure no engine produced, and every claim it checks that the results do not support or contradict (for example a solver score called a loss), each in `findings` with the reason. Run it before publishing or handing over a report, fabrication sheet, BOM summary or any other figure-bearing deliverable built from these tools. It computes nothing and adds no evidence — it only reports what the results back. Fix each finding the way its `why` says: quote the engine's own value, call the tool that computes it, correct the wording, or say plainly in the text that the figure is not from a tool.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Check a draft against engine results
  • design_patch_antennaDesign a rectangular microstrip patch antenna (and, when both nx and ny are given, a uniform planar array of it) using the Balanis cavity/transmission-line + array-factor model — t…1 finding

    Why it is in this group

    • The name "design_patch_antenna" says "patch": 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 "design_patch_antenna" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "design_patch_antenna" says "patch": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Design a rectangular microstrip patch antenna (and, when both nx and ny are given, a uniform planar array of it) using the Balanis cavity/transmission-line + array-factor model — the SAME engine behind POST /api/antenna/patch/design and the Guided Phase IV antenna panel. The substrate (dk/df/h) derives from the latest solved stackup's outer prepreg dielectric unless dk/df/h_mm are given explicitly. Returns patch dimensions, resonance/bandwidth/gain, and (for an array) beamwidths, pattern cuts, and a grating-lobe check. The designed gain auto-applies to the chain's antennaGainDbi (compliance/SAR) unless apply_gain=false.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Design a patch antenna or array
  • design_rf_chainDesign a complete RF transmitter chain with the convergent orchestrator: selects the driver, PA, filter, and connector (the signal source is the user's input power by default — no …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
    Design a complete RF transmitter chain with the convergent orchestrator: selects the driver, PA, filter, and connector (the signal source is the user's input power by default — no VCO unless one is explicitly the generator), matches drive power between stages, inserts a pre-driver or attenuator when needed to reach the target output power, and returns the BOM plus a convergence summary (achieved vs target output). When the BOM's pricingCoverage is 'partial', total_usd is a subtotal of pricedLines of totalLines parts: never call it the total, and state no figure for the unpriced parts. For a receiver, use design_rf_receiver instead. For a module that shares one antenna between transmit and receive, use design_tr_module instead.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Design a transmit chain
  • design_rf_receiverDesign or analyse a superheterodyne RECEIVER.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
    Design or analyse a superheterodyne RECEIVER. Selects catalog parts for each slot (limiter, LNA, image filter, mixer, LO, IF filter, IF amp, step attenuator) and returns the frequency plan (image, half-IF, LO leakage), the cascaded noise figure, noise floor, MDS, sensitivity, SFDR and dynamic range, plus the ADC interface (sample rate, Nyquist zone, ENOB, jitter limit). Pass rfFrequencyHz to design one; pass stages[] only for a bench receiver the user described with their own numbers. For a transmitter, use design_rf_chain instead. For a module that shares one antenna between transmit and receive, use design_tr_module instead.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Design a superheterodyne receiver
  • design_tr_moduleDesign a T/R (transmit/receive) module that shares ONE antenna between a transmitter and a receiver.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
    Design a T/R (transmit/receive) module that shares ONE antenna between a transmitter and a receiver. Designs both chains through the existing engines, selects the shared front end (a T/R switch, or a circulator with a receive-path limiter), and returns four safety budgets: TX-to-RX isolation against the receiver's damage limit, the receive window left after switching and limiter recovery (with the blind range: the closest echo the receiver can hear), limiter leakage driving the LNA into compression, and transmit power against each part's survivability rating. Pass frequencyGhz and targetOutputPowerDbm to design one; pass txPeakPowerDbm and isolationDb only to check a front end the user already described with their own numbers. For a transmitter alone, use design_rf_chain instead. For a receiver alone, use design_rf_receiver instead.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Design a T/R module
  • generate_test_planBench test plan for the designed transmit chain: power, harmonics, stages, rails, temperature, spurious, test points.1 finding

    Why it is in this group

    • The name "generate_test_plan" says "generate": 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 "generate_test_plan" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "generate_test_plan" says "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Bench test plan for the designed transmit chain: power, harmonics, stages, rails, temperature, spurious, test points. Pass lines only from the design or regulatory data; gaps in `missing`.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Write a bench test plan for a transmit chain
  • run_compliance_analysisAudit the solved stackup against PCB standards (IPC-2221, IPC-6012, IPC-4101, MIL, UL-94, RoHS, REACH): per-rule pass/fail with severities and remediation.1 finding

    Why it is in this group

    • The name "run_compliance_analysis" says "run": 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 "run_compliance_analysis" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "run_compliance_analysis" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Audit the solved stackup against PCB standards (IPC-2221, IPC-6012, IPC-4101, MIL, UL-94, RoHS, REACH): per-rule pass/fail with severities and remediation. Layers are derived from the solved stackup and standards default to IPC-2221 + IPC-6012 Class 2 — call with no arguments once a stackup exists.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Run compliance checks
  • run_glass_weave_analysisRecommend PCB glass-weave (fiber-weave) styles for the current design: ranks catalogued styles by impedance variation and cost for the design frequency and marks the cheapest one m…1 finding

    Why it is in this group

    • The name "run_glass_weave_analysis" says "run": 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 "run_glass_weave_analysis" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "run_glass_weave_analysis" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Recommend PCB glass-weave (fiber-weave) styles for the current design: ranks catalogued styles by impedance variation and cost for the design frequency and marks the cheapest one meeting the impedance tolerance. Reuses the Phase-24 engine behind POST /api/glass-weave/recommend. Frequency is derived from the solved stackup / RF specs; tolerance and trace width default to stated assumptions — call with no arguments once a design exists.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Recommend a PCB glass-weave style
  • run_pdn_analysisRun a PDN (power delivery network) impedance analysis: interplanar plane-pair capacitance, multi-cap decoupling impedance vs.1 finding

    Why it is in this group

    • The name "run_pdn_analysis" says "run": 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 "run_pdn_analysis" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "run_pdn_analysis" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run a PDN (power delivery network) impedance analysis: interplanar plane-pair capacitance, multi-cap decoupling impedance vs. target impedance, violations, and recommended decoupling caps. Inputs are derived server-side from the solved stackup, the BOM's PDN passives, and the power-tree rail — call with no arguments once a design exists.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Run power-delivery analysis
  • run_planar_filterSynthesize a passive planar (copper-on-PCB) filter from analytical formulas: stepped-impedance / open-stub low-pass, or parallel-coupled / hairpin band-pass, Chebyshev or Butterwor…1 finding

    Why it is in this group

    • The name "run_planar_filter" says "run": 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 "run_planar_filter" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "run_planar_filter" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Synthesize a passive planar (copper-on-PCB) filter from analytical formulas: stepped-impedance / open-stub low-pass, or parallel-coupled / hairpin band-pass, Chebyshev or Butterworth. Returns per-section line impedances (Z0e/Z0o for coupled sections), width/spacing, quarter-wave lengths, the total occupied board area, a copper footprint, passband markers, a simulated S21/S11 frequency response (response_curve) with modeled insertion loss / return loss / 3-dB bandwidth (response_summary), and accuracy warnings. Reuses the engine behind POST /api/planar-filter/compute (SSOT). Use it to replace a purchased SMT filter with board copper. Interdigital/combline are not implemented.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Synthesize a planar PCB filter
  • run_radar_performanceCompute radar performance — the monostatic range equation (received power, SNR vs range, maximum detection range, coherent/non-coherent integration gain) and pulsed-waveform relati…1 finding

    Why it is in this group

    • The name "run_radar_performance" says "run": 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 "run_radar_performance" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "run_radar_performance" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Compute radar performance — the monostatic range equation (received power, SNR vs range, maximum detection range, coherent/non-coherent integration gain) and pulsed-waveform relations (duty cycle, unambiguous range/velocity, range resolution, blind speeds) — using the SAME engine behind POST /api/radar/performance. Antenna gain enters as a dBi number; the detection floor is reused from a prior link budget's MDS when not given. RCS, target range, and system loss are user assumptions, disclosed on the result.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Compute radar range and waveform limits
  • run_sparam_cascadeCascade a chain's parts from maker .s2p files: S21/S11/S22/S12 at the design frequency, 2x and 3x, plus a sweep (match between parts, harmonic rejection).1 finding

    Why it is in this group

    • The name "run_sparam_cascade" says "run": 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 "run_sparam_cascade" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "run_sparam_cascade" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Cascade a chain's parts from maker .s2p files: S21/S11/S22/S12 at the design frequency, 2x and 3x, plus a sweep (match between parts, harmonic rejection). Small-signal only. No file: datasheet stand-in (assumedParts) or leftOut.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Cascade a chain's maker S-parameter files
  • run_stackup_solverRun the impedance-aware stackup constraint solver to find optimal PCB configurations.1 finding

    Why it is in this group

    • The name "run_stackup_solver" says "run": 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 "run_stackup_solver" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "run_stackup_solver" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run the impedance-aware stackup constraint solver to find optimal PCB configurations. Use when the user wants ranked material/thickness/copper solutions for a given layer count and frequency. Returns scored and ranked feasible stackups. Each solution's prepreg_thickness_mm is ONE prepreg layer: prepreg_sheets (1-3) x prepreg_sheet_thickness_mm (maker's table). Per-layer numbers do NOT sum to total_thickness_mm — the total uses the pressed thickness, 0.04064 mm thinner per layer. Report both as returned; never 'correct' one to match the other.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Solve a PCB stackup
  • run_thermal_analysisPCB thermal analysis: via array Rth, junction-to-ambient stack, Kennedy spreading, Coffin-Manson barrel stress, Timoshenko warpage, and resin-flow estimation.1 finding

    Why it is in this group

    • The name "run_thermal_analysis" says "run": 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 "run_thermal_analysis" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "run_thermal_analysis" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    PCB thermal analysis: via array Rth, junction-to-ambient stack, Kennedy spreading, Coffin-Manson barrel stress, Timoshenko warpage, and resin-flow estimation. Call with no arguments once a design exists: the server takes power_w from the designed chain's dissipated power and defaults ambient_c to 25 C. The result carries `recommendations` (thermal vias, copper, plating) — answer adjustment questions from those entries. If the user states a heatsink or airframe spreader, pass `heatsink` (θcs, θsa and mount, all three as stated — never guessed); Tj is then computed through it instead of still-air convection.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Run thermal analysis
Only reads 3Show 3 read-only tools
  • compare_rf_chainsMulti-objective RF chain comparison: designs the primary chain with the convergent orchestrator, generates alternative chains by swapping components, scores every variant on cost /…Reads text others writeNo findings

    Why it is in this group

    • The name "compare_rf_chains" says "compare": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "post": it reads posts, which other people can write.
    Description, as the server wrote it
    Multi-objective RF chain comparison: designs the primary chain with the convergent orchestrator, generates alternative chains by swapping components, scores every variant on cost / size / performance / DC power, and returns the ranked list with a Pareto frontier — the same engine as the Guided 'Compare Alternatives' panel (POST /api/rf-chain/design-multi). Call with no arguments after a chain design to compare that design.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Compare transmit chain alternatives
  • find_components_by_specFind real parts in the validated catalog that meet a spec: a part type, an operating frequency in GHz, and optional limits (noise figure, gain, P1dB, Psat, OIP3, insertion loss, te…No findings

    Why it is in this group

    • The name "find_components_by_spec" says "find": a word for reading.
    Description, as the server wrote it
    Find real parts in the validated catalog that meet a spec: a part type, an operating frequency in GHz, and optional limits (noise figure, gain, P1dB, Psat, OIP3, insertion loss, temperature grade or range). Returns the matching parts, best first on the first limit, each with its headline figures and the datasheet page for each figure where one is on file, as lookup_component_by_mpn gives them. Parts whose record lacks a limited figure are named as not compared, never counted as matches. Pass only figures your user stated; an untraceable one is refused.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Find parts that meet a spec
  • lookup_component_by_mpnLook up an RF component in the validated catalog by manufacturer part number: the catalog's summary of its headline figures, not the full datasheet.No findings

    Why it is in this group

    • The name "lookup_component_by_mpn" says "lookup": a word for reading.
    Description, as the server wrote it
    Look up an RF component in the validated catalog by manufacturer part number: the catalog's summary of its headline figures, not the full datasheet. Returns the frequency, power and gain ranges, package, datasheet link, and the headline figures (Psat, P1dB, gain, noise figure, OIP3, insertion and conversion loss, junction-to-case thermal resistance, maximum junction temperature), each with its datasheet page where one is on file. Figures the record lacks are listed as not in the record, and internal estimates are named but never given as numbers. It does NOT hold derating, absolute-maximum ratings, bias, test conditions or footnotes: for those, read the datasheet link. Use this whenever the user names a specific part, so answers come from catalog data rather than recall.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
    • title: Look up a part's datasheet figures

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

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:07 UTC, unchanged since Nov 20, 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
16
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
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 16 tools that change things (16 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.pcbgenerator.com/mcp/: tools/list returned 19 tools to an anonymous client, including design_rf_chain (write), design_rf_receiver (write), design_tr_module (write), run_link_budget (write), run_stackup_solver (write) and 11 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 14 to 16

Findings

Matches of fixed checks, with the text they matched.

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

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "run_link_budget" says "run": a word for a change.

    What this check looks for
  • The server marks "run_stackup_solver" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "run_stackup_solver" says "run": a word for a change.

    What this check looks for
  • The server marks "run_thermal_analysis" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "run_thermal_analysis" says "run": a word for a change.

    What this check looks for
  • The server marks "run_pdn_analysis" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "run_pdn_analysis" says "run": a word for a change.

    What this check looks for
  • The server marks "run_compliance_analysis" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "run_compliance_analysis" says "run": a word for a change.

    What this check looks for
  • The server marks "run_ota_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "run_ota_link" says "run": a word for a change.

    What this check looks for
Show 6 more findings
  • The server marks "run_radar_performance" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "run_radar_performance" says "run": a word for a change.

    What this check looks for
  • The server marks "run_planar_filter" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "run_planar_filter" says "run": a word for a change.

    What this check looks for
  • The server marks "design_patch_antenna" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "design_patch_antenna" says "patch": a word for a change.

    What this check looks for
  • The server marks "run_glass_weave_analysis" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "run_glass_weave_analysis" says "run": a word for a change.

    What this check looks for
  • The server marks "run_sparam_cascade" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "run_sparam_cascade" says "run": a word for a change.

    What this check looks for
  • The server marks "generate_test_plan" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "generate_test_plan" says "generate": a word for a change.

    What this check looks for

History

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

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

Install

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

claude mcp add --transport http magicon https://api.pcbgenerator.com/mcp/
claude mcp add --transport http magicon https://api.pcbgenerator.com/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__magicon__lookup_component_by_mpn",
      "mcp__magicon__compare_rf_chains",
      "mcp__magicon__find_components_by_spec"
    ],
    "ask": [
      "mcp__magicon__design_rf_chain",
      "mcp__magicon__design_rf_receiver",
      "mcp__magicon__design_tr_module",
      "mcp__magicon__run_link_budget",
      "mcp__magicon__run_stackup_solver",
      "mcp__magicon__run_thermal_analysis",
      "mcp__magicon__run_pdn_analysis",
      "mcp__magicon__run_compliance_analysis",
      "mcp__magicon__run_ota_link",
      "mcp__magicon__run_radar_performance",
      "mcp__magicon__run_planar_filter",
      "mcp__magicon__design_patch_antenna",
      "mcp__magicon__run_glass_weave_analysis",
      "mcp__magicon__run_sparam_cascade",
      "mcp__magicon__generate_test_plan",
      "mcp__magicon__check_grounding"
    ],
    "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 magicon. Review it before you use it.

Capability tags behind 1 rule
  • mcp__magicon__compare_rf_chains 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.magiccadai/magicon/verify?hash=25c570019dfeb0752d7c5c60b956905f475cb5e89c944cbfe87c47320676a20e" | jq -e '.changed == false'

Pinned hash 25c570019dfe, from Nov 21, 2026, 00: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.magiccadai/magicon/changes.xml

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

Badge

Anlyon Radar badge for io.github.magiccadai/magicon
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.magiccadai/magicon.svg)](https://radar.anlyon.com/servers/io.github.magiccadai/magicon)

Source: MCP Registry. Synced Oct 21, 2026, 18:38 UTC.

MagicON RF Design Engines MCP server: questions and answers

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

Is the MagicON RF Design Engines MCP server safe?

No scan can promise that. What its definitions show: 19 tools, 16 of which can change, send or delete something, and 12 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 MagicON RF Design Engines MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the MagicON RF Design Engines MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the MagicON RF Design Engines MCP server have?

19 tools: 16 write, 3 read. design_rf_chain, design_rf_receiver, design_tr_module, run_link_budget, run_stackup_solver, run_thermal_analysis, run_pdn_analysis, run_compliance_analysis and 11 more.

Does the MagicON RF Design Engines MCP server need sign-in or OAuth?

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

Does the MagicON RF Design Engines MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the MagicON RF Design Engines MCP server changed its tools?

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