CircuitAgent
PYPI · CIRCUIT-AGENT-CLIENT · SCANNED OCT 4
AI hardware synthesis: CircuitBlocks DSL, live LCSC parts, industrial DFX audit, stdio MCP server.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to mo9652962-ai/circuit-agent). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 2731 tokens (~97/item across 28 items; 20 tools + 8 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "audit_industrial_dfx" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the CircuitAgent MCP server?
CircuitAgent runs locally as a PyPI package, launched with uvx circuit-agent-client. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · circuit-agent-client
claude mcp add mo9652962-ai-circuit-agent-client -- uvx circuit-agent-client
{
"mcpServers": {
"mo9652962-ai-circuit-agent-client": {
"command": "uvx",
"args": [
"circuit-agent-client"
]
}
}
} {
"servers": {
"mo9652962-ai-circuit-agent-client": {
"command": "uvx",
"args": [
"circuit-agent-client"
]
}
}
} codex mcp add mo9652962-ai-circuit-agent-client -- uvx circuit-agent-client
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mo9652962-ai-circuit-agent-client": {
"type": "local",
"command": [
"uvx",
"circuit-agent-client"
],
"enabled": true
}
}
} openclaw mcp add mo9652962-ai-circuit-agent-client --command uvx --arg circuit-agent-client
mcp_servers:
mo9652962-ai-circuit-agent-client:
command: "uvx"
args: ["circuit-agent-client"] {
"McpServers": {
"mo9652962-ai-circuit-agent-client": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"circuit-agent-client"
]
}
}
} assistant mcp add mo9652962-ai-circuit-agent-client -t stdio -c uvx -a circuit-agent-client
{
"mcpServers": {
"mo9652962-ai-circuit-agent-client": {
"command": "uvx",
"args": [
"circuit-agent-client"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Oct 26 +6
- Tool safety: pass → unverified ▼ security
- Source repository: fail → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Schema quality: 66 → 97 ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Stability: unverified → 0.07 ▲ functional
- Security disclosure: fail → pass ▲ functional
- Schema quality: good → excellent functional
- Destructive annotations: pass → 0 functional
- Package version: 0.1.5 → 0.1.9 functional
- 2 Oct 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Analysed pypi/circuit-agent-client@0.1.9
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | mo9652962-ai/circuit-agent |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/mo9652962-ai/circuit-agent/.github/workflows/publish.yml@refs/tags/v0.1.9 |
| Rekor log index | 3077512070 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:50131f6b4bda1910c55be96b5e262bb34f049a6bd382e4da5add70751b17d262 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_power_tree ~104
Analyze system-level power distribution architecture, load current budgets (typical & peak mA), regulator dropout headroom, and LDO thermal dissipation / junction temperature estimates.
| Name | Type | Req | Description |
|---|---|---|---|
| ambient_temp_c | number | – | Operating ambient temperature in °C (default: 25.0). |
| modules | object | yes | Component modules dict (from synthesize_circuit output). |
| netlist | object | yes | Netlist dict with 'connections' (from synthesize_circuit output). |
No output schema declared.
No examples provided.
audit_industrial_dfx ~109
Execute an enterprise-grade DFX (DFM/DFA/DFT/DFC/EMC) compliance audit on a schematic netlist. Verifies optical fiducials (MARK points), ICT testpoint coverage on power/debug rails, IEC 61000-4-2 TVS surge protection on exposed ports (USB, RS485, CAN), reverse polarity protection, and SMT costs.
| Name | Type | Req | Description |
|---|---|---|---|
| netlist | object | yes | Hardware netlist dictionary containing 'components' and 'connections'. |
No output schema declared.
No examples provided.
audit_supply_chain ~64
Audit BOM component multi-sourcing resilience (ISO 9001 supply chain audit), identifying single-source bottlenecks and mapping pin-compatible second-source drop-in replacements with LCSC cross-references.
| Name | Type | Req | Description |
|---|---|---|---|
| modules | object | yes | Component modules dict (from synthesize_circuit output). |
No output schema declared.
No examples provided.
calculate_bom_cost ~96
Calculate PCBA component cost breakdown and estimate JLCPCB SMT manufacturing surcharges. Identifies Basic library parts (¥0 feeder fee) vs Extended library parts (+¥20/type feeder fee) and suggests cost optimizations.
| Name | Type | Req | Description |
|---|---|---|---|
| queries | array | yes | List of component names, models, or descriptions (e.g. ['STM32F103C8T6', 'SP3485', '0603 10k']). |
No output schema declared.
No examples provided.
calculate_ipc2152_trace_current ~206
Calculate conductor current-carrying capacity or solve required PCB trace width according to IPC-2152 standards for given copper weight (oz), temperature rise (ΔT °C), and layer position.
| Name | Type | Req | Description |
|---|---|---|---|
| copper_oz | number | – | Finished copper thickness in ounces (default: 1.0 oz = 35 um). |
| layer | string | – | Conductor layer position: 'external' (outer copper) or 'internal' (inner plane). |
| mode | string | yes | 'solve_current' calculates max Amps for given trace_width_mm; 'solve_width' calculates required mm for target_current_a. |
| target_current_a | number | – | Target continuous current in Amperes (required for 'solve_width'). |
| temp_rise_c | number | – | Allowable conductor temperature rise above ambient in °C (default: 20.0 °C). |
| trace_width_mm | number | – | Trace width in mm (required for 'solve_current'). |
No output schema declared.
No examples provided.
calculate_ipc2221_clearance ~142
Calculate minimum electrical clearance (conductor spacing) according to IPC-2221B Table 6-1 based on peak voltage and conductor classification (B1 internal, B2 external uncoated, B4 coated, A6 leads).
| Name | Type | Req | Description |
|---|---|---|---|
| conductor_type | string | – | Conductor classification: B1 (internal), B2 (external uncoated), B4 (coated), A6 (leads). Default: B2. |
| peak_voltage_v | number | yes | Peak working or test voltage in Volts (e.g., 5.0, 12.0, 24.0, 230.0). |
No output schema declared.
No examples provided.
calculate_parametric_circuit ~147
Solve discrete parametric circuit equations: optimal E96 resistor dividers, LDO thermal dissipation, I2C bus pullups, or RC filters.
| Name | Type | Req | Description |
|---|---|---|---|
| params | object | yes | Calculation arguments: for 'resistor_divider' (v_in, v_out_target, max_quiescent_current_ma); for 'ldo_thermal' (v_in, v_out, i_load_a, package); for 'i2c_pullup' (v_cc, bus_capacitance_pf, mode); fo… |
| type | string | yes | Type of parametric calculation to perform. |
No output schema declared.
No examples provided.
calculate_trace_impedance ~267
Calculate characteristic impedance (Z0) or differential impedance (Zdiff) for PCB microstrip traces using IPC-2141 / Wheeler equations. Solves exact trace width W and spacing S for target impedance (e.g. 50Ω RF, 90Ω USB, 120Ω RS485/CAN).
| Name | Type | Req | Description |
|---|---|---|---|
| dielectric_er | number | – | Relative dielectric permittivity (Er) (default: 4.2 for FR4). |
| dielectric_h_mm | number | – | Dielectric height between trace and reference ground plane in mm (default: 0.1mm for JLC04161H 4-layer). |
| mode | string | yes | Trace mode: 'single' for single-ended microstrip, 'differential' for edge-coupled microstrip pair. |
| target_z | number | yes | Target impedance in ohms (e.g. 50.0 for single-ended, 90.0 for USB differential, 120.0 for CAN/RS485). |
| trace_gap_mm | number | – | Spacing between differential traces in mm (only used in differential mode, default: 0.15mm). |
| trace_thickness_mm | number | – | Finished copper thickness in mm (default: 0.035mm for 1oz copper). |
No output schema declared.
No examples provided.
export_kicad_netlist ~70
Export standard KiCad S-Expression netlist (.net) compatible with KiCad 6/7/8/9/10 Pcbnew.
| Name | Type | Req | Description |
|---|---|---|---|
| netlist | object | yes | Hardware netlist dictionary or synthesis result. |
| title | string | – | Schematic / board project title. |
No output schema declared.
No examples provided.
export_kicad_schematic ~101
Export modern KiCad 8/9 S-Expression schematic file (.kicad_sch) directly viewable and editable in KiCad Eeschema with sheet layout, component symbols, pin references, and LCSC attributes.
| Name | Type | Req | Description |
|---|---|---|---|
| connections | array | – | Netlist connections list (optional). |
| modules | object | yes | Component modules dict (from synthesize_circuit output). |
| title | string | – | Schematic sheet title block title. |
No output schema declared.
No examples provided.
export_manufacturing_bom ~50
Generate production-ready JLCPCB SMT BOM CSV with part grouping, designator aggregation, and Basic/Extended classification.
| Name | Type | Req | Description |
|---|---|---|---|
| netlist | object | yes | Hardware netlist dictionary or synthesis result. |
No output schema declared.
No examples provided.
export_specctra_dsn ~187
Generate universal Specctra DSN (v15.0) auto-router interchange file for automated PCB track routing in Freerouting, Cadence Specctra, Altium, or KiCad. Includes heuristic component auto-placement.
| Name | Type | Req | Description |
|---|---|---|---|
| board_height_mm | number | – | PCB height in mm (default: 50.0). |
| board_width_mm | number | – | PCB width in mm (default: 70.0). |
| clearance_mm | number | – | Default routing clearance in mm (default: 0.200 / 8mil). |
| modules | object | yes | Component modules dict (from synthesize_circuit output). |
| netlist | object | yes | Netlist dict with 'connections' (from synthesize_circuit output). |
| trace_width_mm | number | – | Default routing trace width in mm (default: 0.254 / 10mil). |
No output schema declared.
No examples provided.
list_circuit_blocks ~26
List all 10 pre-validated CircuitBlocks available in the hardware DSL catalog.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_supported_chips ~41
List all registered MCU chips and third-party pinout allocation rules (e.g. CH32V003, STM32G030, ATmega328P).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
register_custom_chip ~279
Register or dynamically override a third-party microcontroller pinout and peripheral multiplexing rule.
| Name | Type | Req | Description |
|---|---|---|---|
| chip_id | string | yes | Unique identifier, e.g. 'CH32V003F4P6' |
| default_gpio_assignments | object | – | Default signal mappings, e.g. {'/LED1': 'PD4'} |
| description | string | – | Human-readable description of the chip |
| mcu_family | string | – | MCU family, e.g. 'QingKe-RISC-V', 'ARM-Cortex-M0+' |
| package | string | – | Physical package, e.g. 'TSSOP-20', 'QFN-32' |
| peripheral_routes | object | – | Peripheral routing defaults, e.g. {'I2C1': {'I2C_SCL': 'PC2', 'I2C_SDA': 'PC1'}} |
| pin_numbers | object | – | Map of pin names to physical pin numbers, e.g. {'PD1': '8'} |
| pins | array | yes | List of available GPIO and power pins |
| reserved_pins | object | – | Map of reserved pins and reasons, e.g. {'PD1': 'SWDIO', 'NRST': 'RESET'} |
| supply_voltage | number | – | Operating voltage (typically 3.3 or 5.0) |
No output schema declared.
No examples provided.
render_circuit_topology ~45
Render a clean, structured ASCII architectural diagram of power domains, buses, and connected subsystems.
| Name | Type | Req | Description |
|---|---|---|---|
| netlist | object | yes | Hardware netlist dictionary or synthesis result. |
No output schema declared.
No examples provided.
run_erc ~108
Run deterministic Electrical Rules Check (ERC) on a netlist: floating nets, missing GND, unknown designators, missing power domain, missing decoupling. Every finding carries severity + source; blocking/error issues gate BOM/CPL delivery.
| Name | Type | Req | Description |
|---|---|---|---|
| modules | object | – | Optional modules dict (ref -> {kind, value, package, lcsc}) for component-aware rules. |
| netlist | object | yes | Netlist dict with 'connections' (synthesize_circuit output passes directly). |
No output schema declared.
No examples provided.
search_lcsc_parts ~97
Query live LCSC / JLCPCB component inventory, stock, package, and pricing with zero API keys required. Features 24-hour disk cache and exponential backoff.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of component matches to return (default: 5). |
| query | string | yes | Component part number, model, or description (e.g. 'CH340N', 'SP3485', 'TP4056'). |
No output schema declared.
No examples provided.
synthesize_circuit ~271
Synthesize a deterministic hardware netlist and component modules from a natural language prompt. Supported MCUs: STM32F103, ESP32-C3, ESP32-S3, RP2040, STC89C52, CH32V003, STM32G030, ATmega328P. Peripherals: Type-C, LDO, Crystal, Buttons, LEDs, Buzzer, I2C, RS485, CAN, TP4056 Battery, AHT20 Temp/Humidity Sensor, MPU6050 6-Axis Motion Sensor.
| Name | Type | Req | Description |
|---|---|---|---|
| chip_id | string | – | Optional explicit MCU chip model (e.g. 'CH32V003F4P6', 'STM32G030F6P6', 'ATmega328P', 'STM32F103C8T6') |
| custom_chip | object | – | Optional third-party chip definition with custom pinout, package, and peripheral multiplexing rules |
| pin_mapping | object | – | Optional custom signal-to-pin allocations, e.g. {'/SCL': 'PC2', '/SDA': 'PC1'} |
| prompt | string | yes | Natural language circuit description, e.g. '基于 CH32V003 的 AHT20 温湿度与 MPU6050 姿态传感器节点' |
No output schema declared.
No examples provided.
validate_netlist ~47
Validate a hardware netlist dictionary against the formal CircuitAgent JSON Schema specification.
| Name | Type | Req | Description |
|---|---|---|---|
| netlist | object | yes | Netlist dictionary containing 'connections' list with 'net' and 'points'. |
No output schema declared.
No examples provided.
What is the CircuitAgent MCP server?
CircuitAgent is an MCP server listed in the public MCP registry as io.github.mo9652962-ai/circuit-agent-client. AI hardware synthesis: CircuitBlocks DSL, live LCSC parts, industrial DFX audit, stdio MCP server. This page covers its PyPI package (circuit-agent-client).
Is the CircuitAgent MCP server safe to use?
CircuitAgent scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 October 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CircuitAgent MCP server expose?
CircuitAgent exposes 20 tools: synthesize_circuit, list_supported_chips, register_custom_chip, search_lcsc_parts, list_circuit_blocks, and 15 more. Their descriptions and schemas cost roughly 2,457 tokens of context every time the server is loaded.
Is the CircuitAgent MCP server still maintained?
CircuitAgent is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the CircuitAgent MCP server under?
CircuitAgent declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.