protogrid

Search / me.chargingnear/mcp

ChargingNear.me

R0· no sign-in

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

v1.5.0 · active · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality78good
Trust83of 100
Uptime, 30 days100%
Latency p50314 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "chargingnear": {
      "type": "http",
      "url": "https://chargingnear.me/api/mcp"
    }
  }
}
claude mcp add --transport http chargingnear https://chargingnear.me/api/mcp
[mcp_servers.chargingnear]
url = "https://chargingnear.me/api/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "chargingnear": {
      "type": "remote",
      "url": "https://chargingnear.me/api/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "chargingnear": {
      "type": "http",
      "url": "https://chargingnear.me/api/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=chargingnear&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vY2hhcmdpbmduZWFyLm1lL2FwaS9tY3AifQ%3D%3D"
}
{
  "servers": {
    "chargingnear": {
      "type": "http",
      "url": "https://chargingnear.me/api/mcp"
    }
  }
}
{
  "mcpServers": {
    "chargingnear": {
      "httpUrl": "https://chargingnear.me/api/mcp"
    }
  }
}
extensions:
  "chargingnear":
    enabled: true
    name: "chargingnear"
    type: streamable_http
    uri: "https://chargingnear.me/api/mcp"
    timeout: 300

Quality 78 / 100good

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene94 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • warn
    tools.description_length1 tools have descriptions over 1,024 characters, which crowds the context
  • pass
    tools.schemasevery tool has an object input schema
  • pass
    tools.annotations13 of 13 tools declare readOnlyHint or destructiveHint
  • pass
    tools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
  • pass
    tools.token_costabout 4,222 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
  • pass
    tools.hidden_textno hidden text in tool names, descriptions, schemas or annotations
stability50 · weight 15
  • warn
    stability.changes35 tool changes in 30 days
  • fail
    stability.rug_pull8 tools kept their name but changed most of their description in 30 days; review before trusting them
  • pass
    stability.new_linksno tool change named a new site
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

13 tools, about 4,222 tokens to load them all · tool set 6c5d136f4f7e · tools last changed 2026-11-11 · checked 2026-11-14 07:36 UTC

Tool changes

  • get_my_alertschangeddescription
    before

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

    after · 83% of words in common

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

  • get_my_tripschangeddescription
    before

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

    after · 83% of words in common

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

  • get_my_saved_stationschangeddescription
    before

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

    after · 83% of words in common

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

  • get_charging_gapschangeddescription, input schema
    before

    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.

    after · 58% of words in common

    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.

  • get_my_alertschangeddescription
    before

    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.

    after · 90% of words in common

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

  • get_my_tripschangeddescription
    before

    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.

    after · 93% of words in common

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

  • get_my_saved_stationschangeddescription
    before

    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.

    after · 91% of words in common

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

  • get_nevi_statuschangeddescription
    before

    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.

    after · 84% of words in common

    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.

  • get_corridor_chargerschangeddescription
    before

    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.

    after · 93% of words in common

    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.

  • get_charging_gapschangeddescription
    before

    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.

    after · 75% of words in common

    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.

Showing the latest 10. Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 83 / 100

no-repository
provenance55
liveness100
freshness100
hygiene80

+dns-namespace +website +reachable +uptime-100% +updated-5d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://chargingnear.me/api/mcp streamable-httpnoneyes100%314 ms2025-06-182026-11-14

Tools (13)

find_stations_on_routeread-onlyChargers 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.
get_catalog_totalsread-onlyNationwide 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.
get_charging_gapsread-onlyCharging 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.
get_city_charging_statsread-onlyCharging 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.
get_corridor_chargersread-onlyFast 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.
get_my_alertsread-only"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.
get_my_saved_stationsread-only"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.
get_my_tripsread-only"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.
get_nearest_stationsread-onlyChargers 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.
get_nevi_statusread-onlyFederal 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.
get_state_charging_statsread-onlyCharging 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).
get_station_detailsread-onlyOne 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.
search_stationsread-onlyChargers 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.

Schemas: list_tools.

Similar MCP servers

Official server.json
{
  "name": "me.chargingnear/mcp",
  "_meta": {
    "io.modelcontextprotocol.registry/publisher-provided": {
      "authentication": {
        "oauth2": {
          "scopes": [
            "account:read"
          ],
          "optional": true,
          "authorizationServer": "https://chargingnear.me",
          "protectedResourceMetadata": "https://chargingnear.me/.well-known/oauth-protected-resource/api/mcp"
        },
        "schemes": [
          "bearer",
          "oauth2"
        ],
        "required": false,
        "description": "None required: every directory tool works without sign-in. Optional OAuth 2.1 sign-in (PKCE, dynamic client registration) lets get_my_saved_stations, get_my_trips and get_my_alerts read the driver's own data. Optional API key for higher limits: Authorization: Bearer cnm_…"
      }
    }
  },
  "icons": [
    {
      "src": "https://chargingnear.me/icons/chargingnearme-mcp-512.png",
      "sizes": [
        "512x512"
      ],
      "mimeType": "image/png"
    },
    {
      "src": "https://chargingnear.me/icons/chargingnearme-mcp.svg",
      "sizes": [
        "any"
      ],
      "mimeType": "image/svg+xml"
    }
  ],
  "title": "ChargingNear.me",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://chargingnear.me/api/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.5.0",
  "websiteUrl": "https://chargingnear.me/mcp",
  "description": "U.S. EV charging stations: nearest, on a route, city and state stats, highway gaps and NEVI status."
}