MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Code & DevOps

ChargingNear.me

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

Checks passed
13 / 22

1 failed · 8 not measured

Median response
475 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
13

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Outdated check

Last connection measurement is over 24 hours old. Current availability is unknown.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
400
Publisher identityCan the publisher be traced to its source?
312

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 475 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-06-18, serverInfo.name chargingnearme.

  • Pass
    Lists tools

    tools/list returned 13 tools.

  • Pass
    Current protocol

    Negotiated 2025-06-18. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 475 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 475 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    47 of 53 parameters have a description (89%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Fail
    Source repo linked

    No repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-11-08T22:57:43.664175Z, within 180 days.

  • Not measured
    Open-source licence

    No GitHub repository to ask about a licence.

Start using ChargingNear.me

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

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

Capabilities

Tools 13

find_stations_on_route

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.

Discovered
get_catalog_totals

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.

Discovered
get_charging_gaps

Charging gaps on highways: "charging gaps on I-80", "where can't I fast charge on I-90 in Montana?". 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, filtered by state, highway and length. From our daily open-data file (CC BY 4.0); each answer carries the file's version, date and cite_as line.

Discovered
get_city_charging_stats

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.

Discovered
get_corridor_chargers

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.

Discovered
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, 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.

Discovered
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, 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.

Discovered
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 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.

Discovered
get_nearest_stations

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.

Discovered
get_nevi_status

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.

Discovered
get_state_charging_stats

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).

Discovered
get_station_details

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.

Discovered
search_stations

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.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected475 ms13