Home / MCP registry index / io.github.magiccadai/magicon
MagicON RF Design Engines
io.github.magiccadai/magicon in the official MCP registry.
Endpoint https://api.pcbgenerator.com/mcp/.
The registry describes it as: TX/RX/T-R chains, OTA link, radar, PCB filters, patch antennas, stackup, thermal, PDN, compliance.
We read its 17 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
design_rf_chain design_rf_receiver design_tr_module run_link_budget run_stackup_solver run_thermal_analysis run_pdn_analysis run_compliance_analysis run_ota_link run_radar_performance run_planar_filter design_patch_antenna run_glass_weave_analysis lookup_component_by_mpn compare_rf_chains find_components_by_spec check_grounding
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-magiccadai-magicon)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.