← Registry

API Tools

chargealong.io

Wraps an EV charging-site API to find nearby chargers, fetch full details for a single charging site, list charging networks by country, and look up places with coordinates for searching around.

1 endpoint4 known toolsFirst detected October 1, 2026Last detected October 18, 2026

ENDPOINT 1

https://api.chargealong.io/mcp

No auth detected

MCP server metadata

Name
chargealong
Version
1
Capabilities
loggingtools.listChanged
Server instructions

Public EV charging sites in Australia, New Zealand, the United States, Canada and the United Kingdom, with their plugs, power, price, network and access. Use find_chargers for what is nearest a coordinate, which is the usual question, and narrow it with min_kw, plugs and network when the question does; use search_places first when there is a suburb name but no coordinate; use get_charger to read one site in full, with its connectors and how to get in; use list_networks for who operates chargers in a country. No key and no account: this is free to call. Every answer carries the page's URL and the date the record was last checked, so cite the page and say when it was checked. A charging site's status matters: only active sites are worth sending a driver to.

Known tools 4

find_chargers

The charging sites nearest a point, nearest first, with their power, plugs, price, network and the page each is on.

Inferred read-only
get_charger

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.

Inferred read-only
list_networks

Every network with charging sites in a country, biggest first, with how many sites and how many regions each reaches.

Inferred read-only
search_places

Places matching a name, each with a coordinate to search around and the count of charging sites in it.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.chargealong]
url = "https://api.chargealong.io/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "chargealong": {
      "type": "http",
      "url": "https://api.chargealong.io/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: chargealong
Remote MCP URL: https://api.chargealong.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "chargealong": {
      "url": "https://api.chargealong.io/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "chargealong": {
      "type": "http",
      "url": "https://api.chargealong.io/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "chargealong",
  "transport": "streamable-http",
  "url": "https://api.chargealong.io/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for chargealong.io was fetched 2026-10-02T15:42:21.386Z.

Trust status Neutral

chargealong.io is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.