Remote MCP · Endpoint

RIVET / AliEV EV Charging Site Intelligence MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://aliev.base44.app/functions/alievMcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.jgaethle10/aliev
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
6 tools
Uptime, last 30 days
38.9% from 18 checks
Described by its publisher as
Start with analyze_ev_site(address) for a free, source-backed EV charging opportunity screen.
Website
https://aliev.base44.app/
Repository
https://github.com/jgaethle10/forge-operator
Listing
From the official MCP registry (active).
Recent checks of RIVET / AliEV EV Charging Site Intelligence
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
1 day agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
6 days agoFailed - the server returned an HTTP error—
9 days agoFailed - the server returned an HTTP error—
11 days agoFailed - the server returned an HTTP error—
14 days agoFailed - the server returned an HTTP error—
16 days agoFailed - the server returned an HTTP error—
18 days agoHandshake completed415 ms
20 days agoHandshake completed785 ms
22 days agoHandshake completed220 ms
24 days agoHandshake completed376 ms
26 days agoHandshake completed355 ms
27 days agoHandshake completed375 ms
28 days agoHandshake completed389 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with RIVET / AliEV EV Charging Site Intelligence and makes no claim about it beyond what these checks measured.