# ChargingNear.me (remote · chargingnear.me)

U.S. EV charging stations: nearest, on a route, city and state stats, highway gaps and NEVI status.

- Trust score: 75/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `chargingnear.me`: 75/100 (this document), [markdown](https://verifymcp.io/servers/me-chargingnear-mcp/api-mcp.md), [page](https://verifymcp.io/servers/me-chargingnear-mcp/api-mcp)

## Channel facts

- Endpoint: `https://chargingnear.me/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2038 tokens (~156/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the ChargingNear.me MCP server?

ChargingNear.me is a hosted endpoint at https://chargingnear.me/api/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.

### Claude

```bash
claude mcp add --transport http me-chargingnear-mcp 'https://chargingnear.me/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "me-chargingnear-mcp": {
      "url": "https://chargingnear.me/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "me-chargingnear-mcp": {
      "type": "http",
      "url": "https://chargingnear.me/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.me-chargingnear-mcp]
url = "https://chargingnear.me/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "me-chargingnear-mcp": {
      "type": "remote",
      "url": "https://chargingnear.me/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add me-chargingnear-mcp --url 'https://chargingnear.me/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  me-chargingnear-mcp:
    url: "https://chargingnear.me/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "me-chargingnear-mcp": {
      "Transport": "http",
      "Url": "https://chargingnear.me/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add me-chargingnear-mcp -t streamable-http -u 'https://chargingnear.me/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "me-chargingnear-mcp": {
      "type": "http",
      "url": "https://chargingnear.me/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 75, 0)

- [security] Tool “get_my_alerts” rewrote its description, which is the text the model reads
- [security] Tool “get_my_saved_stations” rewrote its description, which is the text the model reads
- [security] Tool “get_my_trips” rewrote its description, which is the text the model reads

### 2026-11-04 (score 75, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 1690 → 1999
- [functional] Server version: 1.3.1 → 1.4.0
- [functional] New tool “get_my_alerts”
- [functional] New tool “get_my_saved_stations”
- [functional] New tool “get_my_trips”

### 2026-11-03 (score 74, 0)

- [security] Tool “get_catalog_totals” rewrote its description, which is the text the model reads
- [security] Tool “get_station_details” rewrote its description, which is the text the model reads
- [security] Tool “search_stations” rewrote its description, which is the text the model reads
- [security] Tool “find_stations_on_route” rewrote its description, which is the text the model reads
- [security] Tool “get_nearest_stations” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 149 → 169
- [functional regression] Schema quality: 149 → 167
- [functional] Server version: 1.3.0 → 1.3.1
- [functional] Server version: 1.2.0 → 1.3.0
- [cosmetic] “get_nearest_stations” added an optional parameter “place”
- [cosmetic] “find_stations_on_route” reworded the description of “available_now”
- [cosmetic] “get_nearest_stations” reworded the description of “available_now”
- [cosmetic] “search_stations” reworded the description of “available_now”
- [cosmetic] “find_stations_on_route” reworded the description of “waypoints”
- [cosmetic] “get_nearest_stations” reworded the description of “lat”
- [cosmetic] “get_nearest_stations” reworded the description of “lng”
- [cosmetic] “get_nearest_stations” made “lat” optional
- [cosmetic] “get_nearest_stations” made “lng” optional

### 2026-11-02 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 73, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 892 → 1496
- [functional regression] Tool coverage: 100% → 85%
- [functional] Server version: 1.1.0 → 1.2.0
- [functional] New tool “get_catalog_totals”
- [functional] New tool “get_charging_gaps”
- [functional] New tool “get_corridor_chargers”
- [functional] New tool “get_nevi_status”

### 2026-10-31 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 73, +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.

### 2026-10-27 (score 72, +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.

## MCP tools (13)

### `search_stations` (~282 tokens)

Search charging stations

Search EV charging stations by city, state, network, connector, speed, power or live availability. Returns station details including name, address, connector types and pricing, sorted by station name.

Input parameters:

- `available_now` (boolean): Only stations showing a free port in a live reading under 15 minutes old. Live availability is available only to clients with a commercial API key; without one, this filter is ignored and the answer…
- `city` (string): City name
- `connector` (string): Connector type, case-insensitive: CCS, NACS, CHAdeMO, J1772, or a raw NREL code (J1772COMBO, TESLA, CHADEMO). Comma-separate to match any.
- `limit` (integer): Max results (default 10, max 50)
- `min_power_kw` (number): Minimum charger power in kW (e.g. 50, 150, 250). 150 and up only match stations with a known wattage.
- `network` (string): Charging network name (e.g. Tesla, ChargePoint)
- `speed` (string): Charging level: dcfc (DC fast), level2 or level1
- `state` (string): State: two-letter abbreviation (CO), name (Colorado) or slug (colorado)

### `get_nearest_stations` (~303 tokens)

Nearest charging stations

Find the nearest EV charging stations to a place (a U.S. city, address or business name) or a latitude/longitude, optionally filtered by speed, power or live availability. Send place or lat and lng. Results are sorted by distance, nearest first. With place, the answer's place field names the match.

Input parameters:

- `available_now` (boolean): Only stations showing a free port in a live reading under 15 minutes old. Live availability is available only to clients with a commercial API key; without one, this filter is ignored and the answer…
- `lat` (number): Latitude (with lng), if you have coordinates instead of a place
- `limit` (integer): Max results (default 10, max 50)
- `lng` (number): Longitude (with lat)
- `min_power_kw` (number): Minimum charger power in kW (e.g. 50, 150, 250). 150 and up only match stations with a known wattage.
- `place` (string): A U.S. city, address or business name, e.g. "Union Station, Denver, CO". Use instead of lat and lng; sent with them, the match nearest that point is used.
- `radius` (number): Search radius in miles (default 25, max 100)
- `speed` (string): Charging level: dcfc (DC fast), level2 or level1

### `get_station_details` (~47 tokens)

Station details

Get detailed information about a specific EV charging station by its ID: name, address, network, connector types, power, access hours and pricing.

Input parameters:

- `id` (integer, required): Station ID

### `get_city_charging_stats` (~47 tokens)

City charging statistics

Get EV charging statistics for a specific city including station count, network breakdown, and top stations.

Input parameters:

- `slug` (string, required): City slug (e.g. los-angeles-ca)

### `get_state_charging_stats` (~52 tokens)

State charging statistics

Get EV charging statistics for a US state including station count, cities, network breakdown.

Input parameters:

- `slug` (string, required): State: two-letter abbreviation (CO), name (Colorado) or slug (colorado)

### `get_catalog_totals` (~73 tokens)

National catalog totals

Get the size of the ChargingNear.me U.S. catalog, computed live: charging locations (physical sites; every charger at one address counts once), ports (plugs; each charges one car at a time), DC fast ports, states covered and networks. The summary field is the same sentence the website shows.

### `find_stations_on_route` (~329 tokens)

Stations along a route

Find EV charging stations along a drive, for trip planning. Give the stops in driving order as waypoints, either place names (2 to 10, e.g. [{"place": "Denver, CO"}, {"place": "Salt Lake City, UT"}]; the route then follows roads and each station gets route_mile, its miles from the start) or {lat, lng} points (2 to 100; add one every 50 to 100 miles). Searches within a corridor around the route. With place names, results are sorted by route_mile; with points, by segment in driving order, then by distance from the segment's midpoint.

Input parameters:

- `available_now` (boolean): Only stations showing a free port in a live reading under 15 minutes old. Live availability is available only to clients with a commercial API key; without one, this filter is ignored and the answer…
- `corridor_miles` (number): Width of search corridor in miles from route (default 5, max 25)
- `limit_per_waypoint` (integer): Max stations per waypoint segment (default 5, max 10)
- `min_power_kw` (number): Minimum charger power in kW (e.g. 50, 150, 250). 150 and up only match stations with a known wattage.
- `speed` (string): Charging level: dcfc (DC fast), level2 or level1
- `waypoints` (array, required): The stops in driving order: each one {place} or {lat, lng}

### `get_charging_gaps` (~179 tokens)

Highway charging gaps

Stretches of U.S. Interstates, U.S. highways and designated EV Alternative Fuel Corridors where open public DC fast chargers are more than 50 miles apart, longest first. From our daily open-data file (CC BY 4.0); each answer carries the file's version, date and cite_as line.

Input parameters:

- `designated` (boolean): true: only gaps on FHWA-designated Alternative Fuel Corridors; false: only undesignated ones
- `highway` (string): Highway as signed, e.g. I-70, US-40, CO-82
- `limit` (integer)
- `min_miles` (number): Only gaps at least this long, in miles
- `offset` (integer)
- `state` (string): Two-letter code (CO) or name (Colorado)

### `get_corridor_chargers` (~146 tokens)

Fast chargers on a corridor

Every DC fast charging location on a corridor, in driving order, with mile points, distance from the previous charger, ports and power, plus the corridor's longest gaps and how many miles meet the NEVI 50-mile rule. Colorado corridors: I-70, Denver to Grand Junction; I-25, Wyoming to New Mexico; I-76, Denver to the Nebraska Line; US-285, Denver to the New Mexico Line; CO-82, Glenwood Springs to Aspen; US-40, I-70 to Steamboat Springs.

Input parameters:

- `corridor` (string, required): Corridor slug
- `limit` (integer)
- `offset` (integer)

### `get_nevi_status` (~160 tokens)

NEVI status

Which open public DC fast stations meet the federal NEVI minimums (four CCS ports at 150 kW, within 1 mile of a designated corridor), with the reason each one fails, a pass/fail count, and corridor coverage of the 50-mile rule for a state or highway. The rule and its dated sources come with every answer.

Input parameters:

- `grade` (string): Only passing or only failing stations
- `highway` (string): Nearest designated corridor, e.g. I-70
- `limit` (integer)
- `network` (string): Network name contains, e.g. Electrify America
- `offset` (integer)
- `state` (string): Two-letter code (CO) or name (Colorado)

### `get_my_saved_stations` (~97 tokens)

My saved stations

The charging stations the signed-in driver saved on ChargingNear.me, newest first: name, network, city, state, DC fast and Level 2 port counts, their note and the station page link. Needs the driver to sign in to ChargingNear.me; without a valid sign-in the server answers HTTP 401 with a sign-in challenge.

Input parameters:

- `limit` (integer): Max results (default 50, max 100)

### `get_my_trips` (~105 tokens)

My saved trips

The road trips the signed-in driver saved on ChargingNear.me, newest first: start, destination, distance, driving time, the charging stops in driving order (name, network, city, state, station page link) and the trip page link. Needs the driver to sign in to ChargingNear.me; without a valid sign-in the server answers HTTP 401 with a sign-in challenge.

Input parameters:

- `limit` (integer): Max results (default 50, max 100)

### `get_my_alerts` (~106 tokens)

My alerts

The alerts the signed-in driver set up on ChargingNear.me: stations watched for a free charger, price alerts on stations and saved trips, network status alerts and alert areas, each with what triggers it, whether it is on and when it last sent. Needs the driver to sign in to ChargingNear.me; without a valid sign-in the server answers HTTP 401 with a sign-in challenge.

Input parameters:

- `limit` (integer): Max results (default 50, max 100)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/me-chargingnear-mcp/api-mcp#diagnostics

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 74
- 2026-11-02: 74
- 2026-11-01: 73
- 2026-10-31: 74
- 2026-10-30: 73
- 2026-10-29: 73
- 2026-10-28: 72
- 2026-10-27: 72
- 2026-10-26: 71
- 2026-10-25: 71

## Common questions

### What is the ChargingNear.me MCP server?

ChargingNear.me is an MCP server listed in the public MCP registry as me.chargingnear/mcp. U.S. EV charging stations: nearest, on a route, city and state stats, highway gaps and NEVI status. This page covers its hosted endpoint (https://chargingnear.me/api/mcp).

### Is the ChargingNear.me MCP server safe to use?

ChargingNear.me scores 75 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 ChargingNear.me MCP server expose?

ChargingNear.me exposes 13 tools: search_stations, get_nearest_stations, get_station_details, get_city_charging_stats, get_state_charging_stats, and 8 more. Their descriptions and schemas cost roughly 1,926 tokens of context every time the server is loaded.

### Does the ChargingNear.me MCP server require authentication?

No. We connected to ChargingNear.me without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ChargingNear.me MCP server still maintained?

ChargingNear.me is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://chargingnear.me/api/mcp
- Website: https://chargingnear.me/mcp
- Changelog RSS feed: https://verifymcp.io/servers/me-chargingnear-mcp/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/me-chargingnear-mcp/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/me-chargingnear-mcp/api-mcp