Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

EV Load Check

REMOTE · EV-LOAD-CHECK.PERMITEV.COM

NEC-based screening for a home EV charger: panel capacity, wire sizing, voltage drop, GA incentives.

+3 this week 85 Trust /100

Last scanned (6 hours ago)

Scores higher than 91% of remote servers

Reachable. Last reached 5 Nov 2026.

Category IoT and Hardware

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability87
  • 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 547 tokens (~109/item across 5 items; 4 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 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; "check_voltage_drop" implies "drop" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 5 Nov 2026 · Probed https://ev-load-check.permitev.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=permitev.com CN=YE2,O=Let's Encrypt,C=US 18 Sept 2026 17 Dec 2026 ECDSA 256 ECDSA-SHA384 6c5b1257f45f5dd2a51a1dfb209b3ff77b4
SANs: *.permitev.com, permitev.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ev-load-check.permitev.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
permitev.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ev-load-check.permitev.com/mcp Verified 200
http (plaintext) http://ev-load-check.permitev.com/mcp HTTPS enforced 301 https://ev-load-check.permitev.com/mcp
MCP tools · 4 exposed · ~515 tokens

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 →

Tool Tokens
check_panel_capacity ~174

Check whether a home's electrical panel has capacity for an EV charger. Use when a user asks if their panel or breaker box can handle an EV charger, or whether they need a panel upgrade or load management. Returns a verdict (fits / tight / does-not-fit), amps, and a plain-language explanation.

NameTypeReqDescription
appliancesarray–Major appliances with nameplate VA. Optional; improves accuracy.
charger_ampsintegeryesCharger charging current in amps, e.g. 32, 40, 48, 80
main_breaker_ampsintegeryesMain breaker rating of the panel in amps, e.g. 100, 150, 200
square_footageinteger–Home size in square feet. Omit if unknown (assumes 2000).

No output schema declared.

No examples provided.

check_voltage_drop ~119

Check whether a cable run length causes excessive voltage drop for an EV charger circuit. Use when a user asks about long garage/driveway runs, voltage drop, upsizing wire for distance. Returns pass/fail at 3%.

NameTypeReqDescription
charger_ampsintegeryesCharging current in amps
run_length_ftintegeryesOne-way cable run length in feet
wire_materialstring–Default copper.
wire_sizestringyesWire gauge in AWG, e.g. '8' for 8 AWG

No output schema declared.

No examples provided.

lookup_georgia_rebate ~71

Look up Georgia EV charger rebates and incentives: the Georgia Power EV rebate program and the Georgia state tax credit. Use when a user asks about EV charger rebates, incentives, or tax credits in Georgia.

NameTypeReqDescription
charger_typestring–Level 2 charger or DC fast charger. Default level2.

No output schema declared.

No examples provided.

recommend_charger_setup ~151

Recommend breaker size, wire gauge, conduit, and ground wire for a home EV charger circuit. Use when a user asks what wire size, breaker, or circuit their charger needs. Returns wire gauge, breaker amps, EGC size, and a plain-language explanation with NEC citations.

NameTypeReqDescription
ambient_temp_cnumber–Ambient temperature in Celsius. Default 30 (standard).
charger_ampsintegeryesCharger charging current in amps, e.g. 32, 40, 48
run_length_ftinteger–Cable run length in feet. Omit if unknown.
wire_materialstring–Copper (Cu) or aluminum (Al) wire. Default copper.

No output schema declared.

No examples provided.

Install

How do I install the EV Load Check MCP server?

EV Load Check is a hosted endpoint at https://ev-load-check.permitev.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · ev-load-check.permitev.com

# add to Claude Code
claude mcp add --transport http pindotcom-ev-load-check 'https://ev-load-check.permitev.com/mcp'
Common questions

What is the EV Load Check MCP server?

EV Load Check is an MCP server listed in the public MCP registry as io.github.pindotcom/ev-load-check. NEC-based screening for a home EV charger: panel capacity, wire sizing, voltage drop, GA incentives. This page covers its hosted endpoint (https://ev-load-check.permitev.com/mcp).

Is the EV Load Check MCP server safe to use?

EV Load Check scores 85 out of 100 on VerifyMCP. 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 EV Load Check MCP server expose?

EV Load Check exposes 4 tools: check_panel_capacity, recommend_charger_setup, check_voltage_drop, lookup_georgia_rebate. Their descriptions and schemas cost roughly 515 tokens of context every time the server is loaded.

Does the EV Load Check MCP server require authentication?

No. We connected to EV Load Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the EV Load Check MCP server still maintained?

EV Load Check is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.