ChargeAlong public EV charging
REMOTE · API.CHARGEALONG.IO · SCANNED OCT 4
EV chargers near a point and charging networks in AU, NZ, US, UK and Canada. Free, no key.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 586 tokens (~146/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the ChargeAlong public EV charging MCP server?
ChargeAlong public EV charging is a hosted endpoint at https://api.chargealong.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.chargealong.io
claude mcp add --transport http io-chargealong-chargers 'https://api.chargealong.io/mcp'
{
"mcpServers": {
"io-chargealong-chargers": {
"url": "https://api.chargealong.io/mcp"
}
}
} {
"servers": {
"io-chargealong-chargers": {
"type": "http",
"url": "https://api.chargealong.io/mcp"
}
}
} [mcp_servers.io-chargealong-chargers] url = "https://api.chargealong.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-chargealong-chargers": {
"type": "remote",
"url": "https://api.chargealong.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-chargealong-chargers --url 'https://api.chargealong.io/mcp' --transport streamable-http
mcp_servers:
io-chargealong-chargers:
url: "https://api.chargealong.io/mcp" {
"McpServers": {
"io-chargealong-chargers": {
"Transport": "http",
"Url": "https://api.chargealong.io/mcp"
}
}
} assistant mcp add io-chargealong-chargers -t streamable-http -u 'https://api.chargealong.io/mcp'
{
"mcpServers": {
"io-chargealong-chargers": {
"type": "http",
"url": "https://api.chargealong.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Sept 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Oct 2026 · Probed https://api.chargealong.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chargealong.io | CN=YE1,O=Let's Encrypt,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 587bdd37210a0aa7bade197a1bae44e6bd9 |
| SANs: *.chargealong.io, chargealong.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.chargealong.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| chargealong.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.chargealong.io/mcp | Verified | 200 | |
| http (plaintext) | http://api.chargealong.io/mcp | HTTPS enforced | 301 | https://api.chargealong.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_chargers Find EV chargers near a coordinate ~246
The charging sites nearest a point, nearest first, with their power, plugs, price, network and the page each is on. Narrow with min_kw for fast charging, plugs for what the car takes, and network for one operator.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude in degrees, between -90 and 90. |
| limit | integer | – | How many sites to return, 1 to 30. Default 10. |
| lng | number | yes | Longitude in degrees, between -180 and 180. |
| min_kw | number | – | Only sites this fast or faster, in kW. 50 is rapid, 150 and above is ultra fast. |
| network | string | – | Only this network, by slug: tesla, evie-networks, chargefox and so on. Use list_networks to find one. |
| plugs | null|array | – | Only sites with one of these plugs: ccs2, ccs1, chademo, type-2, type-1, nacs, gbt. |
| radius_km | number | – | How far to look, in kilometres, up to 150. Default 50. |
| Name | Type | Req | Description |
|---|---|---|---|
| chargers | null|array | yes | Charging sites, nearest first. |
| near | string | – | The nearest named place to the point, for saying where this is. |
No examples provided.
get_charger Read one charging site in full ~66
Everything about one site from an earlier answer: its connectors with power and quantity, price, access notes, network and when the record was last checked.
| Name | Type | Req | Description |
|---|---|---|---|
| public_id | string | yes | The id from an earlier answer, the last part of a site's URL: abcd2345. |
| Name | Type | Req | Description |
|---|---|---|---|
| charger | object | yes | – |
No examples provided.
list_networks List the charging networks in a country ~58
Every network with charging sites in a country, biggest first, with how many sites and how many regions each reaches.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Country slug: australia, new-zealand, united-states, canada or united-kingdom. |
| Name | Type | Req | Description |
|---|---|---|---|
| networks | null|array | yes | – |
No examples provided.
search_places Find a suburb, town or postcode by name ~47
Places matching a name, each with a coordinate to search around and the count of charging sites in it.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | A suburb, town or postcode. At least two characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| places | null|array | yes | – |
No examples provided.
What is the ChargeAlong public EV charging MCP server?
ChargeAlong public EV charging is an MCP server listed in the public MCP registry as io.chargealong/chargers. EV chargers near a point and charging networks in AU, NZ, US, UK and Canada. Free, no key. This page covers its hosted endpoint (https://api.chargealong.io/mcp).
Is the ChargeAlong public EV charging MCP server safe to use?
ChargeAlong public EV charging scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ChargeAlong public EV charging MCP server expose?
ChargeAlong public EV charging exposes 4 tools: find_chargers, get_charger, list_networks, search_places. Their descriptions and schemas cost roughly 417 tokens of context every time the server is loaded.
Does the ChargeAlong public EV charging MCP server require authentication?
No. We connected to ChargeAlong public EV charging without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ChargeAlong public EV charging MCP server still maintained?
ChargeAlong public EV charging is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.