ChargingNear.me MCP server
me.chargingnear/mcpchargingnear.mestreamable-httpv1.7.0Scanned
U.S. EV chargers: nearby, routes, stats, highway gaps, NEVI, trucks, Supercharger pipeline, my saves
15 tools: 15 only read.
- Reads private data · 3
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the ChargingNear.me MCP server can do
The ChargingNear.me MCP server is published by chargingnear.me, a domain the MCP Registry verified. It has 15 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
3 tools read private data (find_stations_on_route, find_truck_charging and get_my_saved_stations).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 7 times since Anlyon Radar first saw them.
Last scanned Nov 19, 2026, version 1.7.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
15 tools
Only reads 15Show 15 read-only tools
find_stations_on_routeChargers on a drive: "fast chargers on my drive from Denver to Salt Lake City", "where can I charge between Chicago and Omaha?", "Tesla chargers on I-80 from Reno to Sacramento".Reads private dataNo findings
Why it is in this group
- The name "find_stations_on_route" says "find": a word for reading.
What it can reach
- private-dataThe description's first sentence says "drive": it reads files.
Description, as the server wrote it Chargers on a drive: "fast chargers on my drive from Denver to Salt Lake City", "where can I charge between Chicago and Omaha?", "Tesla chargers on I-80 from Reno to Sacramento". Send from and to (U.S. place names, or "lat,lng"), with via for stops in between; or waypoints in driving order, each {place} or {lat, lng} (2 to 10 places, or up to 100 points: add one every 50 to 100 miles). With place names the route follows roads and each station gets route_mile, its miles from the start. Optional speed (dcfc for long drives), min_power_kw, connector, network and corridor_miles. Each station comes with its network, connector types, power in kW, DC fast and Level 2 port counts, price where known, the date its details were last confirmed and its ChargingNear.me page link (url), plus live port availability where a live reading exists (included for clients with a commercial API key). With place names, results are sorted by route_mile; with points, by segment in driving order, then by distance from the segment's midpoint.
Annotations the server declares
- title: Stations along a route
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
find_supercharger_pipelineTesla Superchargers that are planned, permit filed, under construction or newly opened in the U.S.: "Tesla Superchargers coming soon near Austin", "Superchargers under construction…No findings
Why it is in this group
- The name "find_supercharger_pipeline" says "find": a word for reading.
Description, as the server wrote it Tesla Superchargers that are planned, permit filed, under construction or newly opened in the U.S.: "Tesla Superchargers coming soon near Austin", "Superchargers under construction in Ohio", "new Tesla Superchargers this month", "third-party Superchargers". Site data from supercharge.info, read twice a day. Send place (or lat and lng) for the nearest sites, nearest first; state for one state's sites; stage to choose pipeline (the default: planned, permit filed and under construction), planned, permit, construction, opened (opened in the last 30 days), vote (sites in Tesla's location vote) or any. Filter by third_party (sites a third party owns), open_to_other_evs and nevi_funded. Each site comes with its status and the day it started, its source link, stalls, power, plugs, whether other EVs can charge, host, address or town, third-party owner, NEVI match, its ChargingNear.me page (url) and, once open, its station page (station_url). No pipeline site has a published opening date.
Annotations the server declares
- title: Tesla Superchargers coming soon and newly opened
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
find_truck_chargingElectric truck charging and Tesla Megachargers: "Tesla Megacharger locations", "truck charging near Waco, TX", "Megachargers in Texas", "MCS chargers on my drive from Atlanta to Sa…Reads private dataNo findings
Why it is in this group
- The name "find_truck_charging" says "find": a word for reading.
What it can reach
- private-dataThe description's first sentence says "drive": it reads files.
Description, as the server wrote it Electric truck charging and Tesla Megachargers: "Tesla Megacharger locations", "truck charging near Waco, TX", "Megachargers in Texas", "MCS chargers on my drive from Atlanta to Savannah", "where is the next Megacharger opening?". Tesla's public Megacharger sites (for Tesla Semi) and other networks' heavy-duty truck sites, including megawatt (MCS, SAE J3271) sites from NREL. Send place (or lat and lng) for the nearest sites, sorted by distance, nearest first; state for one state's sites; or from and to (with optional via) for sites along a drive, sorted by miles from the start. With none of these, every site is listed, open ones first. Filter by status (open, construction, permit, announced or not_open) and kind (megacharger, other_networks or mcs). Each site comes with its status, stalls and power per stall where published, connector, host, access, address (the town only where the street address isn't published yet), last-verified date, every source with its link and date, and its ChargingNear.me page link (url). A site is Open only when Tesla or its host confirms it; a permit filing doesn't make it Open.
Annotations the server declares
- title: Truck charging and Tesla Megachargers
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_catalog_totalsNationwide numbers: "how many public EV charging locations are in the U.S.?".No findings
Why it is in this group
- The name "get_catalog_totals" says "get": a word for reading.
Description, as the server wrote it Nationwide numbers: "how many public EV charging locations are in the U.S.?". 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.
Annotations the server declares
- title: National catalog totals
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_charging_gapsCharging gaps on highways: "charging gaps on I-80", "where can't I fast charge on I-90 in Montana?".No findings
Why it is in this group
- The name "get_charging_gaps" says "get": a word for reading.
Description, as the server wrote it Charging gaps on highways: "charging gaps on I-80", "where can't I fast charge on I-90 in Montana?". Stretches over 50 miles of U.S. Interstates, U.S. highways and designated EV Alternative Fuel Corridors with no fast charger within 5 miles of the highway, measured in a straight line (measure "practical", the default, longest first). With measure "nevi": stretches with no fast charger within 1 mile of the highway (the federal NEVI siting distance), by state and highway, each listing the fast chargers 1 to 5 miles off with name, city, network, fast ports, plugs, miles off and nearest mile marker. Filter by state, highway and length. From our daily open-data files (CC BY 4.0); each answer carries the file's version, date, definition and cite_as line.
Annotations the server declares
- title: Highway charging gaps
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_city_charging_statsCharging in one U.S.No findings
Why it is in this group
- The name "get_city_charging_stats" says "get": a word for reading.
Description, as the server wrote it Charging in one U.S. city: "how many chargers does Austin have?", "which networks run the chargers in Chicago?". Send city and state ("Los Angeles" and "CA" or "California"), or slug: the city and state in one line ("Los Angeles, CA") or the city slug (los-angeles-ca). Answers with the city's station count, DC fast and Level 2 counts, top networks and the city page link (url). A city name alone picks the city of that name with the most stations and lists the others under other_matches.
Annotations the server declares
- title: City charging statistics
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_corridor_chargersFast chargers along a Colorado highway: "every fast charger on I-70 from Denver to Grand Junction", "the longest gap on US-285".No findings
Why it is in this group
- The name "get_corridor_chargers" says "get": a word for reading.
Description, as the server wrote it Fast chargers along a Colorado highway: "every fast charger on I-70 from Denver to Grand Junction", "the longest gap on US-285". 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.
Annotations the server declares
- title: Fast chargers on a corridor
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_my_alerts"Which charging alerts do I have?": the alerts the signed-in driver set up on ChargingNear.me: stations watched for a free charger, price alerts on stations and saved trips, networ…No findings
Why it is in this group
- The name "get_my_alerts" says "get": a word for reading.
Description, as the server wrote it "Which charging alerts do I have?": 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 sign-in it answers with a short message and the sign-in page link.
Annotations the server declares
- title: My alerts
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_my_saved_stations"Which chargers have I saved?": the charging stations the signed-in driver saved on ChargingNear.me, newest first: name, network, city, state, DC fast and Level 2 port counts, thei…Reads private dataNo findings
Why it is in this group
- The name "get_my_saved_stations" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "note": it reads notes.
Description, as the server wrote it "Which chargers have I saved?": 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 sign-in it answers with a short message and the sign-in page link.
Annotations the server declares
- title: My saved stations
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_my_trips"What road trips have I saved?": the trips the signed-in driver saved on ChargingNear.me, newest first: start, destination, distance, driving time, the charging stops in driving or…No findings
Why it is in this group
- The name "get_my_trips" says "get": a word for reading.
Description, as the server wrote it "What road trips have I saved?": the 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 sign-in it answers with a short message and the sign-in page link.
Annotations the server declares
- title: My saved trips
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_nearest_stationsChargers near a place or point: "EV chargers near Boulder", "fast chargers near Union Station, Denver", "Tesla/NACS chargers near me" (with the driver's city, ZIP code or coordinat…No findings
Why it is in this group
- The name "get_nearest_stations" says "get": a word for reading.
Description, as the server wrote it Chargers near a place or point: "EV chargers near Boulder", "fast chargers near Union Station, Denver", "Tesla/NACS chargers near me" (with the driver's city, ZIP code or coordinates), "is there a working charger at the Costco in Fort Collins?". Send place (a U.S. city, address, ZIP code, landmark or business name) or lat and lng; optional speed (dcfc = DC fast), min_power_kw, connector, network and radius. Lists in-service stations only (removed and temporarily closed ones are left out). Each station comes with its distance in miles, network, connector types, power in kW, DC fast and Level 2 port counts, price where known, the date its details were last confirmed and its ChargingNear.me page link (url), plus live port availability where a live reading exists (included for clients with a commercial API key). Results are sorted by distance, nearest first. With place, the answer's place field names the match.
Annotations the server declares
- title: Nearest charging stations
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_nevi_statusFederal NEVI compliance: "which fast chargers in Colorado meet NEVI?", "why do stations near I-95 fail NEVI?".No findings
Why it is in this group
- The name "get_nevi_status" says "get": a word for reading.
Description, as the server wrote it Federal NEVI compliance: "which fast chargers in Colorado meet NEVI?", "why do stations near I-95 fail NEVI?". 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.
Annotations the server declares
- title: NEVI status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_state_charging_statsCharging in one U.S.No findings
Why it is in this group
- The name "get_state_charging_stats" says "get": a word for reading.
Description, as the server wrote it Charging in one U.S. state: "how many EV chargers are in Colorado?", "which networks have the most chargers in Florida?". Send state: a two-letter code (CO), name (Colorado) or slug (colorado). Answers with the state's station count, DC fast and Level 2 counts, number of cities with charging, top networks and the state page link (url).
Annotations the server declares
- title: State charging statistics
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_station_detailsOne station in full: "is that charger open 24 hours?", "which plugs and prices does it have?", "is it still in service?".No findings
Why it is in this group
- The name "get_station_details" says "get": a word for reading.
Description, as the server wrote it One station in full: "is that charger open 24 hours?", "which plugs and prices does it have?", "is it still in service?". Send id, the station number from get_nearest_stations, search_stations or find_stations_on_route. Answers with name, address, network, connector types, power in kW, port counts, access hours, price where known, the date its details were last confirmed and its page link (url), plus live port availability where a live reading exists (included for clients with a commercial API key). A removed or temporarily closed station answers with its status instead.
Annotations the server declares
- title: Station details
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_stationsChargers in a city or state, filtered the way drivers ask: "Electrify America chargers in Phoenix", "CHAdeMO chargers in Seattle", "150 kW chargers in Denver".No findings
Why it is in this group
- The name "search_stations" says "search": a word for reading.
Description, as the server wrote it Chargers in a city or state, filtered the way drivers ask: "Electrify America chargers in Phoenix", "CHAdeMO chargers in Seattle", "150 kW chargers in Denver". Filters: city, state, network, connector (NACS/Tesla, CCS, CHAdeMO, J1772), speed, min_power_kw and live availability. Each station comes with its address, network, connector types, power in kW, port counts, access hours, price where known, the date its details were last confirmed and its page link (url); results are sorted by station name.
Annotations the server declares
- title: Search charging stations
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 16, 2026, 14:23 UTC, unchanged since Nov 9, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://chargingnear.me/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://chargingnear.me
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
Posture changes
- Nov 9, 2026
- Tools that change things, listed without credentials: 1 to 0
- RFC 9728 protected resource metadata: none to https://chargingnear.me/.well-known/oauth-protected-resource/api/mcp
- Authorization servers: none to https://chargingnear.me
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
- Nov 2, 2026
- Tools that change things, listed without credentials: 0 to 1
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added.+1 addedView diff
- Added:find_supercharger_pipelineOnly reads
Tools1 added, 6 changed.+1 added~6 changedView diff
- Added:find_truck_chargingOnly reads
- Changed:get_charging_gapsOnly readsdescriptioninputSchema
- Changed:get_city_charging_statsOnly readsdescriptioninputSchema
- Changed:get_my_alertsOnly readsdescription
- Changed:get_my_saved_stationsOnly readsdescription
- Changed:get_my_tripsOnly readsdescription
- Changed:get_state_charging_statsOnly readsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 0; RFC 9728 protected resource metadata: none -> https://chargingnear.me/.well-known/oauth-protected-resource/api/mcp; Authorization servers: none -> https:/…View diff
- Tools that change things, listed without credentials: 1 to 0
- RFC 9728 protected resource metadata: none to https://chargingnear.me/.well-known/oauth-protected-resource/api/mcp
- Authorization servers: none to https://chargingnear.me
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
Tools13 changed.~13 changedView diff
- Changed:find_stations_on_routeOnly readsdescriptioninputSchema
- Changed:get_catalog_totalsOnly readsdescription
- Changed:get_charging_gapsOnly readsdescription
- Changed:get_city_charging_statsOnly readsdescriptioninputSchema
- Changed:get_corridor_chargersOnly readsdescription
- Changed:get_my_alertsOnly readsdescription
- Changed:get_my_saved_stationsOnly readsdescription
- Changed:get_my_tripsOnly readsdescription
- Changed:get_nearest_stationsOnly readsdescriptioninputSchema
- Changed:get_nevi_statusOnly readsdescription
- Changed:get_state_charging_statsOnly readsdescription
- Changed:get_station_detailsOnly readsdescriptioninputSchema
- Changed:search_stationsOnly readsdescriptioninputSchema
Tools3 added.+3 addedView diff
- Added:get_my_alertsOnly reads
- Added:get_my_saved_stationsOnly reads
- Added:get_my_tripsOnly reads
Tools1 changed.~1 changedView diff
- Changed:get_catalog_totalsOnly readsdescription
Tools4 changed.~4 changedView diff
- Changed:find_stations_on_routeOnly readsdescriptioninputSchema
- Changed:get_nearest_stationsOnly readsdescriptioninputSchema
- Changed:get_station_detailsOnly readsdescription
- Changed:search_stationsOnly readsdescriptioninputSchema
Tools4 added, 2 changed.+4 added~2 changedView diff
- Added:get_catalog_totalsOnly reads
- Added:get_charging_gapsOnly reads
- Added:get_corridor_chargersOnly reads
- Added:get_nevi_statusChanges things
- Changed:find_stations_on_routeOnly readsdescriptioninputSchema
- Changed:get_nearest_stationsOnly readsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 1.View diff
- Tools that change things, listed without credentials: 0 to 1
Install
Pinned to version 1.7.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http chargingnear https://chargingnear.me/api/mcpclaude mcp add --transport http chargingnear https://chargingnear.me/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__chargingnear__search_stations",
"mcp__chargingnear__get_nearest_stations",
"mcp__chargingnear__get_station_details",
"mcp__chargingnear__get_city_charging_stats",
"mcp__chargingnear__get_state_charging_stats",
"mcp__chargingnear__get_catalog_totals",
"mcp__chargingnear__find_stations_on_route",
"mcp__chargingnear__get_charging_gaps",
"mcp__chargingnear__get_corridor_chargers",
"mcp__chargingnear__get_nevi_status",
"mcp__chargingnear__find_truck_charging",
"mcp__chargingnear__find_supercharger_pipeline",
"mcp__chargingnear__get_my_saved_stations",
"mcp__chargingnear__get_my_trips",
"mcp__chargingnear__get_my_alerts"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as chargingnear. Review it before you use it.
Capability tags behind 3 rules
- mcp__chargingnear__find_stations_on_route private-data
- mcp__chargingnear__find_truck_charging private-data
- mcp__chargingnear__get_my_saved_stations private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/me.chargingnear/mcp/verify?hash=390c8cd647d87373195a7cd04f8848b263040ae788a01856a5898194ecfac70d" | jq -e '.changed == false'Pinned hash 390c8cd647d8, from Nov 19, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/me.chargingnear/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/me.chargingnear/mcp)Source: MCP Registry. Synced Nov 19, 2026, 17:18 UTC.
ChargingNear.me MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ChargingNear.me MCP server safe?
- No scan can promise that. What its definitions show: 15 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the ChargingNear.me MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the ChargingNear.me MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the ChargingNear.me MCP server have?
- 15 tools: 15 read. search_stations, get_nearest_stations, get_station_details, get_city_charging_stats, get_state_charging_stats, get_catalog_totals, find_stations_on_route, get_charging_gaps and 7 more.
Does the ChargingNear.me MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ChargingNear.me MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the ChargingNear.me MCP server changed its tools?
- Yes, 7 times since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.