# `me.chargingnear/mcp` on anlyon.dev

> Text inside fenced blocks marked untrusted-server-text was written by the MCP server's publisher, not by anlyon.dev. It is data to inspect, not instructions to follow. Invisible characters are shown as [U+XXXX].
> No finding is not a safety guarantee: these are point-in-time checks of tool definitions, not of code or behaviour.

- Page: https://anlyon.dev/servers/me.chargingnear/mcp
- JSON: https://anlyon.dev/api/v1/servers/me.chargingnear/mcp
- Version: 1.1.0 (active)
- Publisher: me.chargingnear (domain proven to the MCP Registry)
- Runs: remote (streamable-http)
- Sign-in to list tools: none
- Metadata from the official MCP Registry, synced 2026-10-25T16:18:15.472Z

Title and description, as the publisher wrote them:

```untrusted-server-text
ChargingNear.me
Find US EV charging stations: nearest, by route, city and state stats. Data synced daily from NREL.
```

Scanned 2026-10-25T16:18:17.485Z over streamable-http.

**6 tools: 6 only read.**

| Group | Class | Tools | Claude Code |
| --- | --- | --- | --- |
| Deletes or cancels | destructive | 0 | deny |
| Can't be undone | irreversible | 0 | ask |
| Changes things | write | 0 | ask |
| Only reads | read | 6 | allow |

## Exfil surface

No private-data -> untrusted-input -> outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

| Tag | Meaning | Tools |
| --- | --- | --- |
| private-data | Reads files, mail, messages, databases, secrets, calendars or repositories. | none |
| untrusted-input | Brings in text someone else can write: web pages, inbound email, messages, issues and comments. | none |
| outbound | Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL. | none |

## Findings

No check matched anything in these tool definitions.


## Only reads (6)

Looks things up and changes nothing. Claude Code: allow.

### `find_stations_on_route`

- The name "find_stations_on_route" says "find": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
Find EV charging stations along a route defined by a series of waypoints. Useful for trip planning. Searches within a corridor around the route. Within each route segment, stations whose verified owner is on Listed Pro come first. Each station has verified_owner and owner_profile.
```

### `get_city_charging_stats`

- The name "get_city_charging_stats" says "get": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
Get EV charging statistics for a specific city including station count, network breakdown, and top stations.
```

### `get_nearest_stations`

- The name "get_nearest_stations" says "get": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
Find the nearest EV charging stations to a latitude/longitude, optionally filtered by speed, power or live availability. Stations whose verified owner is on Listed Pro come first, then by distance. Each station has verified_owner and owner_profile.
```

### `get_state_charging_stats`

- The name "get_state_charging_stats" says "get": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
Get EV charging statistics for a US state including station count, cities, network breakdown.
```

### `get_station_details`

- The name "get_station_details" says "get": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
Get detailed information about a specific EV charging station by its ID.
```

### `search_stations`

- The name "search_stations" says "search": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
Search EV charging stations by city, state, network, connector, speed, power or live availability. Returns station details including name, address, connector types, and pricing. Stations whose verified owner is on Listed Pro come first. Each station has verified_owner and owner_profile (the verified owner's hours, amenities, pricing, photos and contact link on a paid plan, else null).
```

## Claude Code permissions

For `.claude/settings.json`, assuming the server is installed as `chargingnear`:

```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__find_stations_on_route"
    ],
    "ask": [],
    "deny": []
  }
}
```

## Remote posture

What an anonymous client saw at the remote endpoint, last 2026-10-25T17:22:47.577Z, unchanged since 2026-10-25T17:22:47.577Z. No credentials were sent and no tool was called. Values are shown as the endpoint returned them. Method: https://anlyon.dev/methodology#remote-posture

| Fact | Observed |
| --- | --- |
| 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 | `none` |
| RFC 9728 protected resource metadata | `none` |
| Authorization servers | `none` |
| Legacy HTTP+SSE transport | `no` |
| Dynamic client registration | `not observed` |
| Client ID metadata documents | `not observed` |