Remote MCP · Endpoint

EV Load Check MCP server

No. EV Load Check answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://ev-load-check.permitev.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.pindotcom/ev-load-check
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
700 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
NEC-based screening for a home EV charger: panel capacity, wire sizing, voltage drop, GA incentives.
Listing
From the official MCP registry (active).
Recent checks of EV Load Check
CheckedResultHandshake
35 minutes agoHandshake completed700 ms
3 days agoHandshake completed196 ms
13 days agoHandshake completed193 ms
14 days agoHandshake completed350 ms
15 days agoHandshake completed189 ms
16 days agoHandshake completed161 ms
17 days agoHandshake completed162 ms
18 days agoHandshake completed195 ms
19 days agoHandshake completed166 ms
20 days agoHandshake completed356 ms
22 days agoHandshake completed421 ms
25 days agoHandshake completed1.04 s
27 days agoHandshake completed197 ms
29 days agoHandshake completed215 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 22 responding of 22.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with EV Load Check and makes no claim about it beyond what these checks measured.