Skip to content

EV Load Check MCP server

io.github.pindotcom/ev-load-checkpindotcomstreamable-httpv0.1.0Scanned

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

4 tools: 1 can delete or cancel things, 2 change things and 1 only read.

Tools: 1 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the EV Load Check MCP server can do

The EV Load Check MCP server is published by the GitHub account pindotcom. It has 4 tools. It can delete or cancel things (1 tool: check_voltage_drop) and create or change data (2 tools: check_panel_capacity and recommend_charger_setup). 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Deletes or cancels 1Claude Code: deny
  • check_voltage_dropCheck whether a cable run length causes excessive voltage drop for an EV charger circuit.2 findings

    Why it is in this group

    • The name "check_voltage_drop" says "drop": a word for removing or ending something.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    • The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "check_voltage_drop" read-only (readOnlyHint: true), and its own name, description or input give the class "destructive".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "check_voltage_drop" says "drop": a word for removing or ending something.

      What this check looks for
    • Warn

      The server marks "check_voltage_drop" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "check_voltage_drop" says "drop": a word for removing or ending something.

      What this check looks for
    Description, as the server wrote it
    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%.

    Annotations the server declares

    • title: Check Voltage Drop
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Changes things 2Claude Code: ask
  • check_panel_capacityCheck whether a home's electrical panel has capacity for an EV charger.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check Panel Capacity
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • recommend_charger_setupRecommend breaker size, wire gauge, conduit, and ground wire for a home EV charger circuit.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Recommend Charger Setup
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • lookup_georgia_rebateLook up Georgia EV charger rebates and incentives: the Georgia Power EV rebate program and the Georgia state tax credit.No findings

    Why it is in this group

    • The name "lookup_georgia_rebate" says "lookup": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Lookup Georgia Rebate
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:09 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://ev-load-check.permitev.com/mcp: tools/list returned 4 tools to an anonymous client, including check_voltage_drop (destructive), check_panel_capacity (write), recommend_charger_setup (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "check_voltage_drop" read-only (readOnlyHint: true), and its own name, description or input give the class "destructive".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "check_voltage_drop" says "drop": a word for removing or ending something.

    What this check looks for
  • The server marks "check_voltage_drop" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "check_voltage_drop" says "drop": a word for removing or ending something.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http ev-load-check https://ev-load-check.permitev.com/mcp
claude mcp add --transport http ev-load-check https://ev-load-check.permitev.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ev-load-check__lookup_georgia_rebate"
    ],
    "ask": [
      "mcp__ev-load-check__check_panel_capacity",
      "mcp__ev-load-check__recommend_charger_setup"
    ],
    "deny": [
      "mcp__ev-load-check__check_voltage_drop"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ev-load-check. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.pindotcom/ev-load-check/verify?hash=dd6376f06993eb5e23fdc6edff67705b5898f6069b27186df1945143f84bb018" | jq -e '.changed == false'

Pinned hash dd6376f06993, from Nov 21, 2026, 02:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.pindotcom/ev-load-check/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.pindotcom/ev-load-check
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.pindotcom/ev-load-check.svg)](https://radar.anlyon.com/servers/io.github.pindotcom/ev-load-check)

Source: MCP Registry. Synced Oct 21, 2026, 18:43 UTC.

EV Load Check MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the EV Load Check MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the EV Load Check MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: check_voltage_drop.

Can the EV Load Check MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the EV Load Check MCP server have?

4 tools: 1 destructive, 2 write, 1 read. check_voltage_drop, check_panel_capacity, recommend_charger_setup and lookup_georgia_rebate.

Does the EV Load Check MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the EV Load Check MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the EV Load Check MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.