# Openchargemap (npm · @pipeworx/mcp-openchargemap)

Open Charge Map MCP — global EV charging station database (openchargemap.io).

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-openchargemap/openchargemap-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-openchargemap/openchargemap-mcp)
- npm · `@pipeworx/mcp-openchargemap`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-openchargemap/pipeworx-mcp-openchargemap.md), [page](https://verifymcp.io/servers/pipeworx-io-openchargemap/pipeworx-mcp-openchargemap)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-openchargemap`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-openchargemap).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 529 tokens (~264/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Openchargemap MCP server?

Openchargemap runs locally as an npm package, launched with npx -y @pipeworx/mcp-openchargemap. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-openchargemap -- npx -y @pipeworx/mcp-openchargemap
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-openchargemap": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-openchargemap"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-openchargemap": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-openchargemap"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-openchargemap -- npx -y @pipeworx/mcp-openchargemap
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-openchargemap": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-openchargemap"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-openchargemap --command npx --arg -y --arg @pipeworx/mcp-openchargemap
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-openchargemap:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-openchargemap"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-openchargemap": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-openchargemap"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-openchargemap -t stdio -c npx -a -y @pipeworx/mcp-openchargemap
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-openchargemap": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-openchargemap"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 66, −12)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.17
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 78, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (2)

### `find_stations` (~367 tokens)

Find EV charging stations (electric vehicle chargers) near a place. Pass a `location` name (city/place, e.g. "San Francisco", "Berlin", "Austin TX") and it is geocoded automatically — OR pass explicit latitude+longitude. Returns nearby charging stations with operator, status, available connector types (CCS/CHAdeMO/Tesla connectors), charging speed (kW), and distance. Filter by connector type to find e.g. only CCS or Tesla chargers.

Input parameters:

- `_apiKey` (string): Optional — your own Open Charge Map API key for higher limits; works without one.
- `connection_type` (string): Optional connector type name to filter by, e.g. "CCS", "CHAdeMO", "Tesla". Case-insensitive substring match against each station's connector titles.
- `country` (string): Optional ISO country code (e.g. "US", "FR") to disambiguate an ambiguous `location` like "Paris" or "Springfield".
- `distance` (number): Search radius around the location (default 10).
- `distance_unit` (string): Unit for the search radius (default "KM").
- `latitude` (number): Latitude of the search center, e.g. 37.7749. Optional if `location` is given.
- `location` (string): Place/city name to search near, e.g. "San Francisco", "Berlin", "Austin TX". Geocoded automatically. Provide THIS or latitude+longitude.
- `longitude` (number): Longitude of the search center, e.g. -122.4194. Optional if `location` is given.
- `max_results` (number): Maximum number of stations to return (default 20, max 100).

### `get_station` (~108 tokens)

Get full detail for a single EV charging station by its Open Charge Map POI ID. Returns the connector types (CCS/CHAdeMO/Tesla connectors), charging speed (kW), operator, status, plus user comments and last-verified date.

Input parameters:

- `_apiKey` (string): Optional — your own Open Charge Map API key for higher limits; works without one.
- `id` (number, required): Open Charge Map POI ID (e.g. from find_stations results).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-openchargemap/pipeworx-mcp-openchargemap#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 66
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the Openchargemap MCP server?

Openchargemap is an MCP server listed in the public MCP registry as io.github.pipeworx-io/openchargemap. Open Charge Map MCP, global EV charging station database (openchargemap.io). This page covers its npm package (@pipeworx/mcp-openchargemap).

### Is the Openchargemap MCP server safe to use?

Openchargemap scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Openchargemap MCP server expose?

Openchargemap exposes 2 tools: find_stations, get_station. Their descriptions and schemas cost roughly 475 tokens of context every time the server is loaded.

### Is the Openchargemap MCP server still maintained?

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

### What licence is the Openchargemap MCP server under?

Openchargemap declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-openchargemap
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-openchargemap
- Repository: https://github.com/pipeworx-io/mcp-openchargemap
- Website: https://pipeworx.io/packs/openchargemap
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-openchargemap/pipeworx-mcp-openchargemap.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-openchargemap/pipeworx-mcp-openchargemap.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-openchargemap/pipeworx-mcp-openchargemap