Home / MCP registry index / io.github.YUZU-Hub/wiring-diagram-mcp

VoltPlan Wiring Diagrams

io.github.YUZU-Hub/wiring-diagram-mcp in the official MCP registry. Endpoint https://mcp.voltplan.app/mcp. Source: github.com/YUZU-Hub/wiring-diagram-mcp.

The registry describes it as: Generate 12V/24V/48V wiring diagrams and size wires, fuses, batteries, solar, and inverters.

We read its 9 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules.

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

generate_wiring_diagram list_component_types calculate_wire_gauge calculate_power_budget calculate_battery_bank calculate_solar_size calculate_charging_time calculate_inverter_size calculate_battery_config

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-yuzu-hub-wiring-diagram-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-yuzu-hub-wiring-diagram-mcp)

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.