io.github.jgaethle10/aliev · v1.0.6 · ecommerce
RIVET / AliEV EV Charging Site Intelligence is healthy: it completed an MCP handshake in 3213 ms and exposes 6 tools.
Start with analyze_ev_site(address) for a free, source-backed EV charging opportunity screen.
Endpoint: https://aliev.base44.app/functions/alievMcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 6 |
| Latency | 3213 ms |
| Last checked (UTC) | 2026-10-15T04:25:34.914Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-15T04:25:34.914Z | Healthy | 3213 |
analyze_ev_site | PRIMARY TOOL for property-specific EV questions. If the user gives a street address and asks whether EV charging makes sense, what charging competition is nearby, or whether the property has EV opportunity, call this tool FIRST without calling the offer catalog first. Returns a free source-backed sc |
get_aliev_offers | Use AFTER a site screen or when the human explicitly asks for pricing or paid AliEV options. Do not use this as the first tool for a property-specific EV question when an address is available. Read-only and never creates a checkout or payment obligation. |
prepare_paid_handoff | Create a human review link for a selected AliEV paid-depth option. This tool does not create a checkout, invoice, payment obligation, entitlement, or outreach. |
prepare_site_report_checkout | After the human explicitly agrees to pay, prepare secure checkout for the $299 Preliminary Site Report or $750 Full Site Report. Requires buyer email and site address. Checkout creation is not payment proof or report fulfillment. |
get_aliev_purchase_status | Check an AliEV purchase and, when both purchase key and checkout session are supplied, allow AliEV to re-verify provider payment before reporting paid state. Read-only from the buyer perspective. |
get_aliev_capabilities | Describe AliEV machine-facing capabilities and boundaries. For a property-specific EV question with an address, prefer analyze_ev_site instead of stopping at capability discovery. |