Remote MCP · Endpoint

io.github.cyanheads/openchargemap-mcp-server MCP server

No. io.github.cyanheads/openchargemap-mcp-server answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://openchargemap.caseyjhand.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.cyanheads/openchargemap-mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
124 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Find EV charging stations, detail, and reliability check-ins via the global Open Charge Map.
Listing
From the official MCP registry (active).
Recent checks of io.github.cyanheads/openchargemap-mcp-server
CheckedResultHandshake
2 hours agoHandshake completed124 ms
2 days agoHandshake completed141 ms
4 days agoHandshake completed104 ms
5 days agoHandshake completed71 ms
7 days agoHandshake completed111 ms
8 days agoHandshake completed557 ms
9 days agoHandshake completed100 ms
12 days agoHandshake completed74 ms
13 days agoHandshake completed162 ms
15 days agoHandshake completed137 ms
17 days agoHandshake completed171 ms
18 days agoHandshake completed89 ms
19 days agoHandshake completed112 ms
20 days agoHandshake completed69 ms
20 days agoHandshake completed77 ms
21 days agoHandshake completed86 ms
23 days agoHandshake completed84 ms

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

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 io.github.cyanheads/openchargemap-mcp-server and makes no claim about it beyond what these checks measured.