
RIVET / AliEV EV Charging Site Intelligence
io.github.jgaethle10Published by GitHub account jgaethle10v1.0.6Updated Oct 24, 2026
Start with analyze_ev_site(address) for a free, source-backed EV charging opportunity screen.
The publisher's own server: Rivet
Overview
A remote MCP endpoint that lets an assistant run a free, source-backed EV charging opportunity screen for a given address.
- What you can do
- Run an EV charging opportunity screen for a street address using the analyze_ev_site tool, which returns a free, source-backed assessment of charging potential at that location.
- When to use it
- Useful when you want a quick, evidence-backed first look at whether a specific address is a promising site for EV charging, before deeper site analysis or investment work.
- Requirements
- A remote MCP endpoint at the provider's hosted address; no packages, environment variables or headers are declared, and no authentication is declared.
Installation
In SourceWeft
- Open RIVET / AliEV EV Charging Site Intelligence in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.jgaethle10%2Faliev/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"rivet-aliev-ev-charging-site-intelligenc": {
"type": "http",
"url": "https://aliev.base44.app/functions/alievMcp"
}
}
}README
This repository has no README.
Tools
0Version history
5- v1.0.6LatestSep 29, 2026
- v1.0.5Sep 26, 2026
- v1.0.3Sep 25, 2026
- v1.0.2Sep 24, 2026
- v1.0.1Sep 24, 2026
Score
60% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.