_ registry / mcp http-sse · checked 29m ago

wiring-diagram-mcp

https://mcp.voltplan.app

Registry code: d4c2b446cfe32cfb

api record

Generate electrical wiring diagrams for campers, boats, and off-grid setups.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.voltplan.app/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is wiring-diagram-mcp live?
Yes — it answered the hub's last check (checked 29m ago). It answered 99% of checks over the last 30 days.
Is wiring-diagram-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does wiring-diagram-mcp have?
9 tools: calculate_battery_bank, calculate_battery_config, calculate_inverter_size, calculate_solar_size, calculate_wire_gauge, generate_wiring_diagram, calculate_charging_time, calculate_power_budget, ….
Is wiring-diagram-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99.5%· all time 99.5%

latency
114ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 433 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
energy & utilities renewables & storage
used for
  • generate a camper wiring diagram
  • size a battery bank
  • calculate solar panel size
  • calculate wire gauge
  • size an inverter
takes → gives
data → data, images
tools
9 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
1 open 8 never probed 1 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_component_types reads open 29m ago

    List all available component types and example configurations for building wiring diagrams. Use this to understand what parameters are needed before calling generate_wiring_diagram.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • calculate_battery_bank reads unknown 29m ago

    Calculate the recommended battery bank size based on daily energy consumption. Accounts for days of autonomy (how many days without charging) and depth of discharge. Returns required capacity, number of batteries, and wiring configuration.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "dailyConsumptionWh",
    "systemVoltage",
    "singleBatteryAh",
    "singleBatteryVoltage"
  ],
  "properties": {
    "systemVoltage": {
      "type": "number",
      "description": "Target system voltage in volts (e.g. 12, 24, 48)"
    },
    "daysOfAutonomy": {
      "type": "number",
      "default": 2,
      "description": "Days the system should run without any charging (default: 2)"
    },
    "singleBatteryAh": {
      "type": "number",
      "description": "Capacity of a single battery in amp-hours (e.g. 100, 200)"
    },
    "dailyConsumptionWh": {
      "type": "number",
      "description": "Daily energy consumption in watt-hours (from calculate_power_budget)"
    },
    "singleBatteryVoltage": {
      "type": "number",
      "description": "Voltage of a single battery (e.g. 12.8 for LiFePO4, 12 for lead-acid)"
    },
    "depthOfDischargePercent": {
      "type": "number",
      "default": 80,
      "description": "Usable percentage of battery capacity. LiFePO4: 80-90%, AGM: 50%, Gel: 50% (default: 80)"
    }
  },
  "additionalProperties": false
}
    arguments 39 lines
  • calculate_battery_config reads unknown 29m ago

    Determine how to arrange batteries in series and/or parallel to achieve a target voltage and capacity. Returns the number of batteries needed, the wiring configuration (e.g. 2S3P), and step-by-step wiring instructions.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "targetVoltage",
    "targetCapacityAh",
    "singleBatteryVoltage",
    "singleBatteryAh"
  ],
  "properties": {
    "targetVoltage": {
      "type": "number",
      "description": "Desired system voltage (e.g. 12, 24, 48)"
    },
    "singleBatteryAh": {
      "type": "number",
      "description": "Capacity of one battery in amp-hours"
    },
    "targetCapacityAh": {
      "type": "number",
      "description": "Desired total capacity in amp-hours"
    },
    "singleBatteryVoltage": {
      "type": "number",
      "description": "Nominal voltage of one battery (e.g. 12.8 for LiFePO4, 12 for lead-acid, 3.2 for LiFePO4 cells)"
    }
  },
  "additionalProperties": false
}
    arguments 29 lines
  • calculate_inverter_size reads unknown 14h ago

    Calculate the recommended inverter size for running AC loads from a DC battery system. Accounts for continuous power, startup surge power (motors typically surge 2-3x), and includes a 25% headroom for the continuous rating. Returns the recommended inverter wattage and the DC current draw at system voltage.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "systemVoltage",
    "loads"
  ],
  "properties": {
    "loads": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "name",
          "continuousWatts"
        ],
        "properties": {
          "name": {
            "type": "string",
            "description": "Name of the AC load (e.g. \"Microwave\", \"Coffee Machine\")"
          },
          "quantity": {
            "type": "number",
            "default": 1,
            "description": "Number of identical units (default: 1)"
          },
          "surgeWatts": {
            "type": "number",
            "description": "Startup surge power in watts (for motors, compressors). If omitted, assumed equal to continuous watts."
          },
          "continuousWatts": {
            "type": "number",
            "description": "Continuous power draw in watts"
          }
        },
        "additionalProperties": false
      },
      "description": "List of AC loads that will run through the inverter"
    },
    "systemVoltage": {
      "type": "number",
      "description": "DC system voltage (e.g. 12, 24, 48)"
    }
  },
  "additionalProperties": false
}
    arguments 46 lines
  • calculate_solar_size reads unknown 10h ago

    Calculate the required solar panel wattage to cover daily energy consumption. Accounts for peak sun hours at the location and system efficiency losses (MPPT conversion, wiring, temperature derating). Returns required wattage and common panel configurations.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "dailyConsumptionWh",
    "peakSunHours"
  ],
  "properties": {
    "peakSunHours": {
      "type": "number",
      "description": "Average daily peak sun hours for the location. Examples: Northern Europe winter 1-2h, summer 4-6h. Southern US 5-6h. Equatorial regions 5-7h."
    },
    "systemEfficiency": {
      "type": "number",
      "default": 0.85,
      "description": "Overall system efficiency factor (default: 0.85). Accounts for MPPT losses, wiring losses, temperature derating, and panel soiling."
    },
    "dailyConsumptionWh": {
      "type": "number",
      "description": "Daily energy consumption in watt-hours (from calculate_power_budget)"
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • calculate_wire_gauge reads unknown 10h ago

    Calculate the recommended wire gauge / cable cross-section for a DC circuit. Considers both ampacity (current carrying capacity) and voltage drop to recommend the optimal cable size. Also returns total resistance, power loss, and a fuse recommendation. Supports copper conductors from 0.75 mm² (18 AWG) to 240 mm² (300 MCM).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "voltage",
    "cableLengthM"
  ],
  "properties": {
    "power": {
      "type": "number",
      "description": "Load power in watts. Will be converted to current using the voltage. Provide either current or power."
    },
    "current": {
      "type": "number",
      "description": "Load current in amps. Provide either current or power."
    },
    "voltage": {
      "type": "number",
      "description": "System voltage in volts (e.g. 12, 24, 48)"
    },
    "isRoundTrip": {
      "type": "boolean",
      "default": true,
      "description": "Account for both positive and negative conductor (default: true). Set to false for chassis-ground returns."
    },
    "cableLengthM": {
      "type": "number",
      "description": "One-way cable length in meters"
    },
    "temperatureCelsius": {
      "type": "number",
      "default": 20,
      "description": "Ambient temperature in °C (default: 20°C). Affects copper resistance."
    },
    "maxVoltageDropPercent": {
      "type": "number",
      "default": 3,
      "description": "Maximum acceptable voltage drop in percent (default: 3%)"
    }
  },
  "additionalProperties": false
}
    arguments 42 lines
  • generate_wiring_diagram reads unknown 10h ago

    Generate an electrical wiring diagram for campers, boats, or off-grid setups. Returns a complete schematic with batteries, chargers, protection components, and loads. Protection components (shunt, main switch, low-voltage cutoff) are auto-generated when both batteries and loads are provided.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "systemName"
  ],
  "properties": {
    "loads": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "name",
          "power",
          "voltage",
          "current"
        ],
        "properties": {
          "name": {
            "type": "string",
            "description": "Load name (e.g. \"LED Lights\")"
          },
          "power": {
            "type": "number",
            "description": "Power consumption in watts"
          },
          "current": {
            "type": "number",
            "description": "Current draw in amps"
          },
          "voltage": {
            "type": "number",
            "description": "Operating voltage"
          }
        },
        "additionalProperties": false
      },
      "description": "Electrical loads / consumers"
    },
    "format": {
      "enum": [
        "svg",
        "png"
      ],
      "type": "string",
      "default": "svg",
      "description": "Output format: svg (recommended, renders inline) or png (base64-encoded image, may not display in all clients)"
    },
    "chargers": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "name",
          "inputVoltage",
          "outputVoltage",
          "power"
        ],
        "properties": {
          "name": {
            "type": "string",
            "description": "Charger name (e.g. \"MPPT Solar Charger\")"
          },
          "power": {
            "type": "number",
            "description": "Power rating in watts"
          },
          "sourceType": {
            "enum": [
              "shore",
              "solar",
              "wind",
              "generator",
              "alternator"
            ],
            "type": "string",
            "description": "Type of power source feeding this charger"
          },
          "inputVoltage": {
            "type": "number",
            "description": "Input voltage. For shore/generator (AC) chargers use the regional mains voltage: 230 V in Europe, UK, Australia, most of Asia and Africa; 120 V in North America and Japan. For solar/wind use the panel or turbine output voltage. For alternator use the vehicle system voltage (typically 14 V)."
          },
          "outputVoltage": {
            "type": "number",
            "description": "Output voltage"
          }
        },
        "additionalProperties": false
      },
      "description": "Chargers with their power sources"
    },
    "batteries": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "name",
          "voltage",
          "capacityAh",
          "energyWh"
        ],
        "properties": {
          "name": {
            "type": "string",
            "description": "Battery name (e.g. \"LiFePO4 100Ah\")"
          },
          "voltage": {
            "type": "number",
            "description": "Nominal voltage (e.g. 12)"
          },
          "energyWh": {
            "type": "number",
            "description": "Energy in watt-hours"
          },
          "capacityAh": {
            "type": "number",
            "description": "Capacity in amp-hours"
          }
        },
        "additionalProperties": false
      },
      "description": "Batteries in the system"
    },
    "systemName": {
      "type": "string",
      "description": "Name of the electrical system (e.g. \"My Camper Van\")"
    }
  },
  "additionalProperties": false
}
    arguments 130 lines
  • calculate_charging_time reads unknown 14h ago

    Estimate how long it takes to charge a battery bank from a given state of charge to a target level. Accounts for the bulk charging phase (constant current, up to ~80% SoC) and the slower absorption phase (tapering current, 80-100% SoC). Works for any charging source: solar, shore power, alternator.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "batteryCapacityAh",
    "batteryVoltage",
    "currentStateOfChargePercent",
    "chargePowerWatts"
  ],
  "properties": {
    "batteryVoltage": {
      "type": "number",
      "description": "Battery bank voltage (e.g. 12, 24, 48)"
    },
    "chargePowerWatts": {
      "type": "number",
      "description": "Charger output power in watts"
    },
    "batteryCapacityAh": {
      "type": "number",
      "description": "Total battery bank capacity in amp-hours"
    },
    "chargeCurrentAmps": {
      "type": "number",
      "description": "Maximum charge current in amps (if limited by the charger or battery BMS). If omitted, calculated from power and voltage."
    },
    "targetStateOfChargePercent": {
      "type": "number",
      "default": 100,
      "description": "Target state of charge in percent (default: 100)"
    },
    "currentStateOfChargePercent": {
      "type": "number",
      "description": "Current state of charge in percent (e.g. 20 for 20%)"
    }
  },
  "additionalProperties": false
}
    arguments 38 lines
  • calculate_power_budget reads unknown 14h ago

    Calculate total daily energy consumption from a list of electrical loads. Each load specifies its power draw, how many hours per day it runs, and quantity. Returns total daily energy (Wh and Ah), peak power draw, and average power. This is typically the first step in sizing a battery bank and solar system.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "systemVoltage",
    "loads"
  ],
  "properties": {
    "loads": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "name",
          "powerWatts",
          "hoursPerDay"
        ],
        "properties": {
          "name": {
            "type": "string",
            "description": "Name of the load (e.g. \"LED Lights\")"
          },
          "quantity": {
            "type": "number",
            "default": 1,
            "description": "Number of identical units (default: 1)"
          },
          "powerWatts": {
            "type": "number",
            "description": "Power consumption of a single unit in watts"
          },
          "hoursPerDay": {
            "type": "number",
            "description": "Average hours of use per day"
          }
        },
        "additionalProperties": false
      },
      "description": "List of electrical loads to include in the budget"
    },
    "systemVoltage": {
      "type": "number",
      "description": "System voltage in volts (e.g. 12, 24, 48)"
    }
  },
  "additionalProperties": false
}
    arguments 47 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d4c2b446cfe32cfb.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d4c2b446cfe32cfb/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d4c2b446cfe32cfb/badge.svg)](https://brick.blue/agent/d4c2b446cfe32cfb?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.