# io.github.mrfentmen/edrv-mcp (npm · edrv-mcp)

MCP server for eDRV: charging stations, conne MCP: real tools for real work.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `edrv-mcp`: 68/100 (this document), [markdown](https://verifymcp.io/servers/mrfentmen-edrv-mcp/edrv-mcp.md), [page](https://verifymcp.io/servers/mrfentmen-edrv-mcp/edrv-mcp)

## Channel facts

- Registry: `npm`
- Package: `edrv-mcp`
- Version: `1.0.0`
- 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-21.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 31 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 19 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1115 tokens (~34/item across 32 items; 32 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_chargestation" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 32 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 io.github.mrfentmen/edrv-mcp server?

io.github.mrfentmen/edrv-mcp runs locally as an npm package, launched with npx -y edrv-mcp. 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 mrfentmen-edrv-mcp -- npx -y edrv-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "mrfentmen-edrv-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "edrv-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mrfentmen-edrv-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "edrv-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mrfentmen-edrv-mcp -- npx -y edrv-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add mrfentmen-edrv-mcp --command npx --arg -y --arg edrv-mcp
```

### Hermes

```yaml
mcp_servers:
  mrfentmen-edrv-mcp:
    command: "npx"
    args: ["-y", "edrv-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "mrfentmen-edrv-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "edrv-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mrfentmen-edrv-mcp -t stdio -c npx -a -y edrv-mcp
```

### Other

```json
{
  "mcpServers": {
    "mrfentmen-edrv-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "edrv-mcp"
      ]
    }
  }
}
```

## 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-20 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 64, +2)

- [functional improvement] Stability: unverified → 0.13

### 2026-11-08 (score 62)

First indexed and scored.

## MCP tools (32)

### `list_chargestations` (~29 tokens)

List every charge station on the eDRV account with its status, serial number and connector count.

### `create_chargestation` (~44 tokens)

Register a new charge station. The body is an eDRV charge-station object and is sent unchanged.

Input parameters:

- `body` (object, required): eDRV charge station JSON body

### `get_chargestation` (~37 tokens)

Fetch one charge station by id, including its status and last-seen timestamp.

Input parameters:

- `id` (string, required): eDRV resource id

### `update_chargestation` (~50 tokens)

Patch a charge station. Only the fields present in the body are changed.

Input parameters:

- `body` (object, required): Fields to patch on the charge station
- `id` (string, required): eDRV resource id

### `delete_chargestation` (~38 tokens)

Permanently delete a charge station from the account. Destructive and cannot be undone.

Input parameters:

- `id` (string, required): eDRV resource id

### `list_chargestation_connectors` (~39 tokens)

List the connectors attached to one charge station, with status, type and power.

Input parameters:

- `id` (string, required): eDRV resource id

### `list_connectors` (~25 tokens)

List every connector across the account with its charge station, status and power rating.

### `get_connector` (~37 tokens)

Fetch a single connector by id with its type, status, power, current and voltage.

Input parameters:

- `id` (string, required): eDRV resource id

### `update_connector` (~48 tokens)

Patch a connector's configuration. Only the fields present in the body are changed.

Input parameters:

- `body` (object, required): Fields to patch on the connector
- `id` (string, required): eDRV resource id

### `remote_start` (~54 tokens)

Start a charging session on physical hardware. This sends a real OCPP command to the charger.

Input parameters:

- `id` (string, required): eDRV resource id
- `payload` (object): Protocol-specific command fields forwarded to eDRV unchanged

### `remote_stop` (~55 tokens)

Stop an active charging session on physical hardware. This sends a real OCPP command to the charger.

Input parameters:

- `id` (string, required): eDRV resource id
- `payload` (object): Protocol-specific command fields forwarded to eDRV unchanged

### `reset_charger` (~54 tokens)

Reset a charge station. This interrupts any session on the hardware, so use it deliberately.

Input parameters:

- `id` (string, required): eDRV resource id
- `payload` (object): Protocol-specific command fields forwarded to eDRV unchanged

### `unlock_connector` (~51 tokens)

Unlock a connector's cable lock so the plug can be removed from the vehicle.

Input parameters:

- `id` (string, required): eDRV resource id
- `payload` (object): Protocol-specific command fields forwarded to eDRV unchanged

### `reserve_connector` (~51 tokens)

Reserve a connector for a driver so nobody else can start a session on it.

Input parameters:

- `id` (string, required): eDRV resource id
- `payload` (object): Protocol-specific command fields forwarded to eDRV unchanged

### `cancel_reservation` (~49 tokens)

Cancel an existing connector reservation and release it back to the pool.

Input parameters:

- `id` (string, required): eDRV resource id
- `payload` (object): Protocol-specific command fields forwarded to eDRV unchanged

### `list_commands` (~22 tokens)

List command history with each command's type, status and target charger.

### `list_transactions` (~21 tokens)

List charging transactions with energy delivered, cost, status and timestamps.

### `get_transaction` (~34 tokens)

Fetch one charging transaction by id with its energy, cost and session window.

Input parameters:

- `id` (string, required): eDRV resource id

### `get_transaction_cost` (~29 tokens)

Fetch the computed cost breakdown for one transaction.

Input parameters:

- `id` (string, required): eDRV resource id

### `list_reservations` (~23 tokens)

List connector reservations with their status, window, charger and driver.

### `list_locations` (~17 tokens)

List charging locations with their address and coordinates.

### `get_location` (~34 tokens)

Fetch one charging location by id with its address, coordinates and time zone.

Input parameters:

- `id` (string, required): eDRV resource id

### `create_location` (~38 tokens)

Create a charging location. The body is an eDRV location object and is sent unchanged.

Input parameters:

- `body` (object, required): eDRV location JSON body

### `delete_location` (~33 tokens)

Permanently delete a charging location. Destructive and cannot be undone.

Input parameters:

- `id` (string, required): eDRV resource id

### `list_drivers` (~22 tokens)

List drivers registered on the account with their contact details and status.

### `list_vehicles` (~25 tokens)

List connected vehicles with make, model, battery level, range and odometer.

### `get_vehicle_battery` (~33 tokens)

Read one vehicle's live battery state of charge and range.

Input parameters:

- `id` (string, required): eDRV resource id

### `start_vehicle_charge` (~32 tokens)

Ask a connected vehicle to begin charging at its current location.

Input parameters:

- `id` (string, required): eDRV resource id

### `get_vehicle_location` (~28 tokens)

Read one vehicle's last known location.

Input parameters:

- `id` (string, required): eDRV resource id

### `list_organizations` (~18 tokens)

List the organizations the current token can see.

### `list_tokens` (~23 tokens)

List RFID and app tokens issued on the account with their type and expiry.

### `get_realtime` (~22 tokens)

Read the live realtime snapshot: current charging activity across the account.

## Diagnostics

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

## Score history

- 2026-11-21: 68
- 2026-11-20: 68
- 2026-11-19: 67
- 2026-11-18: 67
- 2026-11-17: 66
- 2026-11-16: 66
- 2026-11-15: 65
- 2026-11-14: 65
- 2026-11-13: 65
- 2026-11-12: 64
- 2026-11-11: 62
- 2026-11-10: 62
- 2026-11-09: 62
- 2026-11-08: 62

## Common questions

### What is the io.github.mrfentmen/edrv-mcp server?

io.github.mrfentmen/edrv-mcp is listed in the public MCP registry as io.github.mrfentmen/edrv-mcp. MCP server for eDRV: charging stations, conne MCP: real tools for real work. This page covers its npm package (edrv-mcp).

### Is the io.github.mrfentmen/edrv-mcp server safe to use?

io.github.mrfentmen/edrv-mcp scores 68 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.mrfentmen/edrv-mcp server expose?

io.github.mrfentmen/edrv-mcp exposes 32 tools: list_chargestations, create_chargestation, get_chargestation, update_chargestation, delete_chargestation, and 27 more. Their descriptions and schemas cost roughly 1,115 tokens of context every time the server is loaded.

### Is the io.github.mrfentmen/edrv-mcp server still maintained?

io.github.mrfentmen/edrv-mcp is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.mrfentmen/edrv-mcp server under?

io.github.mrfentmen/edrv-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.mrfentmen/edrv-mcp server?

VerifyMCP ran 16 checks on io.github.mrfentmen/edrv-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/edrv-mcp
- Socket report: https://socket.dev/npm/package/edrv-mcp
- Repository: https://github.com/mrfentmen/awesome-servers
- Changelog RSS feed: https://verifymcp.io/servers/mrfentmen-edrv-mcp/edrv-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mrfentmen-edrv-mcp/edrv-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mrfentmen-edrv-mcp/edrv-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mrfentmen-edrv-mcp/edrv-mcp
