ChargingNear.me
REMOTE · CHARGINGNEAR.ME
U.S. EV charging stations: nearest, on a route, city and state stats, highway gaps and NEVI status.
Available components
Last scanned (3 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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 Usability67
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 0
- 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 security
- 4 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 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” functional
- 3 Nov 26 0
- 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 security
- Schema quality: 149 → 169 ▼ functional
- Schema quality: 149 → 167 ▼ functional
- Server version: 1.3.0 → 1.3.1 functional
- Server version: 1.2.0 → 1.3.0 functional
- “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 cosmetic
- 2 Nov 26 +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.
- 1 Nov 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 892 → 1496 ▼ functional
- 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” functional
- 31 Oct 26 +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.
- 29 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.
- 27 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.
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 5 Nov 2026 · Probed https://chargingnear.me/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chargingnear.me | CN=YE2,O=Let's Encrypt,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 588d4be4bc9a06c7e14928e3862495287ed |
| SANs: chargingnear.me | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 chargingnear.me. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| me. | present | 45352 | 8 | Verified |
| chargingnear.me. | 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=63072000; includeSubDomains |
| content-security-policy | default-src 'self';worker-src 'self' blob:;style-src 'self' 'unsafe-inline' https://fonts.googleapis.com;font-src 'self' https://fonts.gstatic.com data:;img-src 'self' data: blob: https://maps.googleapis.com https://maps.gstatic.com https://*.googleapis.com https://*.googleusercontent.com https://*.ggpht.com https://*.google.com https://www.google-analytics.com https://images.unsplash.com https://www.gstatic.com https://tiles.stadiamaps.com;connect-src 'self' https://maps.googleapis.com https://*.googleapis.com https://*.posthog.com https://*.ingest.sentry.io https://*.sentry.io https://www.google-analytics.com https://*.analytics.google.com https://tiles.stadiamaps.com https://api.stadiamaps.com;frame-src 'self' https://www.google.com https://maps.google.com;object-src 'none';base-uri 'self';form-action 'self';frame-ancestors 'self';script-src 'self' 'unsafe-inline' https://maps.googleapis.com https://maps.gstatic.com https://www.googletagmanager.com https://www.google-analytics.com https://*.posthog.com htt |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), ambient-light-sensor=(), autoplay=(), battery=(), camera=(), display-capture=(), document-domain=(), encrypted-media=(), fullscreen=(self), geolocation=(self), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), picture-in-picture=(), publickey-credentials-get=(self), screen-wake-lock=(), sync-xhr=(), usb=(), xr-spatial-tracking=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://chargingnear.me/api/mcp | Verified | 200 | |
| http (plaintext) | http://chargingnear.me/api/mcp | HTTPS enforced | 301 | https://chargingnear.me:443/api/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_stations_on_route Stations along a route ~329
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The stops in driving order: each one {place} or {lat, lng} |
No output schema declared.
No examples provided.
get_catalog_totals National catalog totals ~73
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_charging_gaps Highway charging gaps ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
get_city_charging_stats City charging statistics ~47
Get EV charging statistics for a specific city including station count, network breakdown, and top stations.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | City slug (e.g. los-angeles-ca) |
No output schema declared.
No examples provided.
get_corridor_chargers Fast chargers on a corridor ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| corridor | string | yes | Corridor slug |
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
get_my_alerts My alerts ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 50, max 100) |
No output schema declared.
No examples provided.
get_my_saved_stations My saved stations ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 50, max 100) |
No output schema declared.
No examples provided.
get_my_trips My saved trips ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 50, max 100) |
No output schema declared.
No examples provided.
get_nearest_stations Nearest charging stations ~303
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
get_nevi_status NEVI status ~160
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
get_state_charging_stats State charging statistics ~52
Get EV charging statistics for a US state including station count, cities, network breakdown.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | State: two-letter abbreviation (CO), name (Colorado) or slug (colorado) |
No output schema declared.
No examples provided.
get_station_details Station details ~47
Get detailed information about a specific EV charging station by its ID: name, address, network, connector types, power, access hours and pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Station ID |
No output schema declared.
No examples provided.
search_stations Search charging stations ~282
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
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.
remote · chargingnear.me
claude mcp add --transport http me-chargingnear-mcp 'https://chargingnear.me/api/mcp'
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.