ocpp vs ChargeAlong public EV charging
ocpp is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑07.
ocpp is a plugin bundle for AI coding tools published by Alexei Moisseev. No marketplace we read lists it any more. ChargeAlong public EV charging is an MCP server published by chargealong.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  ChargeAlong public EV charging | |
|---|---|---|
| Community marketplace alexeimoisseev/ocpp.md | Removed on 2026-11-07 Version: 0.3.0 Forks (GitHub): 7 Stars (GitHub): 31 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | ocppno longer listed · | ChargeAlong public EV charging |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 31 | No figure on GitHub |
| Forks (GitHub) (differs) | 7 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (api.chargealong.io/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/alexeimoisseev/ocpp.md | Not stated |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 41 h ago returned HTTP 405 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of ocpp
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
OCPI versions, checks and payload validation, plus your own test runs and run starts with a key.
-
Execute ccs-chademo-protocol-mcp
Premium agentic endpoint for ccs-chademo-protocol-mcp.
-
askacharge.com — EV charging network
Operate a network of EV charge points over OCPP: status, sessions, tariffs, prices, remote commands
-
openchargemap-mcp-server io.github.cyanheads/openchargemap-mcp-server
Find EV charging stations, detail, and reliability check-ins via the global Open Charge Map.
-
Energy management platform — 61 tools for solar, battery, grid, and EV charging control
-
openchargemap-mcp io.github.mrfentmen/openchargemap-mcp
Search Open Charge Map: chargers near coordinates, details.
What each says it does
ocpp
OCPP protocol reference (2.1, 2.0.1 & 1.6J) for AI-assisted EV charging development
ChargeAlong public EV charging
EV chargers near a point and charging networks in AU, NZ, US, UK and Canada. Free, no key.
How to run each
ocpp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
ChargeAlong public EV charging As a remote MCP server
claude mcp add --transport http chargers https://api.chargealong.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only ChargeAlong public EV charging has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: ocpp · What it can do: ChargeAlong public EV charging · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.