# ChargerDojo (remote · chargerdojo.com)

OCPI versions, what changed between them, and which modules and journeys ChargerDojo tests.

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

## Components

- remote · `chargerdojo.com`: 81/100 (this document), [markdown](https://verifymcp.io/servers/com-chargerdojo-ocpi/api-mcp.md), [page](https://verifymcp.io/servers/com-chargerdojo-ocpi/api-mcp)

## Channel facts

- Endpoint: `https://chargerdojo.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-09-22.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 355 tokens (~59/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

ChargerDojo is a hosted endpoint at https://chargerdojo.com/api/mcp, so there is nothing to install locally. 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 --transport http com-chargerdojo-ocpi 'https://chargerdojo.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-chargerdojo-ocpi": {
      "url": "https://chargerdojo.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-chargerdojo-ocpi": {
      "type": "http",
      "url": "https://chargerdojo.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-chargerdojo-ocpi]
url = "https://chargerdojo.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-chargerdojo-ocpi": {
      "type": "remote",
      "url": "https://chargerdojo.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-chargerdojo-ocpi --url 'https://chargerdojo.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-chargerdojo-ocpi:
    url: "https://chargerdojo.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-chargerdojo-ocpi": {
      "Transport": "http",
      "Url": "https://chargerdojo.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-chargerdojo-ocpi -t streamable-http -u 'https://chargerdojo.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-chargerdojo-ocpi": {
      "type": "http",
      "url": "https://chargerdojo.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-22 (score 81, 0)

- [security] Stability: 0.97 → pass

### 2026-09-21 (score 81, +1)

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

### 2026-09-18 (score 80, +1)

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

### 2026-09-16 (score 79, +1)

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

### 2026-09-14 (score 78, +1)

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

### 2026-09-12 (score 77, +1)

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

### 2026-09-10 (score 76, +1)

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

### 2026-09-08 (score 75, +1)

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

## MCP tools (6)

### `chargerdojo_describe_access` (~35 tokens)

Explain what this server can do, which tools are open to anyone, and which need a ChargerDojo API key.

### `chargerdojo_list_ocpi_versions` (~34 tokens)

List the OCPI versions ChargerDojo covers, with what each one is for and which modules are implemented.

### `chargerdojo_get_ocpi_version` (~64 tokens)

Describe one OCPI version: how the credentials token is encoded, whether endpoints split into sender and receiver, which modules are implemented, and what the known limits are.

Input parameters:

- `version` (string, required): OCPI version, for example 2.2.1.

### `chargerdojo_compare_ocpi_versions` (~77 tokens)

Compare two OCPI versions: what changed in the protocol between them, and which modules ChargerDojo gained.

Input parameters:

- `from` (string, required): The version being moved away from, for example 2.1.1.
- `to` (string, required): The version being moved to, for example 2.2.1.

### `chargerdojo_list_journey_templates` (~34 tokens)

List the OCPI charging journeys that can be run against the built-in sandbox, with how long each takes.

### `chargerdojo_list_conformance_suites` (~59 tokens)

List the OCPI conformance suites that can be run, grouped by module, with how many checks each carries.

Input parameters:

- `version` (string): Optional OCPI version to narrow to, for example 2.2.1.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-chargerdojo-ocpi/api-mcp#diagnostics

## Score history

- 2026-09-22: 81
- 2026-09-21: 81
- 2026-09-20: 80
- 2026-09-19: 80
- 2026-09-18: 80
- 2026-09-17: 79
- 2026-09-16: 79
- 2026-09-15: 78
- 2026-09-14: 78
- 2026-09-13: 77
- 2026-09-12: 77
- 2026-09-11: 76
- 2026-09-10: 76
- 2026-09-09: 75
- 2026-09-08: 75
- 2026-09-07: 74
- 2026-09-06: 74
- 2026-09-05: 73
- 2026-09-04: 73
- 2026-09-03: 73
- 2026-09-02: 72
- 2026-09-01: 72
- 2026-08-31: 71
- 2026-08-30: 71
- 2026-08-29: 70
- 2026-08-28: 70
- 2026-08-27: 69
- 2026-08-26: 69
- 2026-08-25: 67
- 2026-08-24: 66

## Common questions

### What is the ChargerDojo MCP server?

ChargerDojo is an MCP server listed in the public MCP registry as com.chargerdojo/ocpi. OCPI versions, what changed between them, and which modules and journeys ChargerDojo tests. This page covers its hosted endpoint (https://chargerdojo.com/api/mcp).

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

ChargerDojo scores 81 out of 100 on VerifyMCP. 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 ChargerDojo MCP server expose?

ChargerDojo exposes 6 tools: chargerdojo_describe_access, chargerdojo_list_ocpi_versions, chargerdojo_get_ocpi_version, chargerdojo_compare_ocpi_versions, chargerdojo_list_journey_templates, chargerdojo_list_conformance_suites. Their descriptions and schemas cost roughly 303 tokens of context every time the server is loaded.

### Does the ChargerDojo MCP server require authentication?

No. We connected to ChargerDojo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ChargerDojo MCP server still maintained?

ChargerDojo is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://chargerdojo.com/api/mcp
- Repository: https://github.com/chargerdojo/dojo
- Website: https://chargerdojo.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-chargerdojo-ocpi/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-chargerdojo-ocpi/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-chargerdojo-ocpi/api-mcp