# ChargerDojo (remote · mcp.chargerdojo.com)

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

- Trust score: 75/100 (medium)
- Change this week: −5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

> **Recent critical change**: Authorization (2026-11-03). See the changelog below before you install this server.

## Components

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

## Channel facts

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

## 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-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (chargerdojo_cancel_run).
  - 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**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2563 tokens (~122/item across 21 items; 21 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 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 21 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 22 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://mcp.chargerdojo.com/, 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://mcp.chargerdojo.com/'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

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-11-03 (score 75, −6)

- [critical regression] Authorization: partial → fail
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] New tool “chargerdojo_cancel_run”, which the server declares destructive
- [security] Tool “chargerdojo_compare_ocpi_versions” rewrote its description, which is the text the model reads
- [security] Tool “chargerdojo_describe_access” rewrote its description, which is the text the model reads
- [security] Tool “chargerdojo_get_ocpi_version” rewrote its description, which is the text the model reads
- [security] Tool “chargerdojo_list_conformance_suites” rewrote its description, which is the text the model reads
- [security] Tool “chargerdojo_list_journey_templates” rewrote its description, which is the text the model reads
- [security] Tool “chargerdojo_list_ocpi_versions” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional] Server version: 1.3.4 → 1.8.0
- [functional] New tool “chargerdojo_validate_payload”
- [functional] New tool “chargerdojo_start_conformance_run”
- [functional] New tool “chargerdojo_run_sandbox_journey”
- [functional] New tool “chargerdojo_run_journey”
- [functional] New tool “chargerdojo_list_targets”
- [functional] New tool “chargerdojo_list_runs”
- [functional] New tool “chargerdojo_list_runnable_journeys”
- [functional] New tool “chargerdojo_list_checks”
- [functional] New tool “chargerdojo_get_usage”
- [functional] New tool “chargerdojo_get_schedule”
- [functional] New tool “chargerdojo_get_run_verdict”
- [functional] New tool “chargerdojo_get_run_checks”
- [functional] New tool “chargerdojo_get_journey_events”
- [functional] New tool “chargerdojo_compare_run”
- [cosmetic] “chargerdojo_list_journey_templates” added an optional parameter “role”
- [cosmetic] “chargerdojo_list_journey_templates” added an optional parameter “version”
- [cosmetic] Tool “chargerdojo_list_ocpi_versions” changed its title: OCPI versions
- [cosmetic] Tool “chargerdojo_compare_ocpi_versions” changed its title: Compare two OCPI versions
- [cosmetic] Tool “chargerdojo_describe_access” changed its title: What this server offers
- [cosmetic] Tool “chargerdojo_get_ocpi_version” changed its title: One OCPI version
- [cosmetic] Tool “chargerdojo_list_conformance_suites” changed its title: Conformance suites
- [cosmetic] Tool “chargerdojo_list_journey_templates” changed its title: Charging journeys

### 2026-10-31 (score 81, +1)

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

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

- [security] Tool “chargerdojo_list_journey_templates” rewrote its description, which is the text the model reads
- [functional] Server version: 1.3.3 → 1.3.4

### 2026-10-29 (score 80, +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-10-27 (score 79, +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-10-25 (score 78, +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-10-22 (score 77, +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-10-20 (score 76, +1)

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

## MCP tools (21)

### `chargerdojo_describe_access` (~67 tokens)

What this server offers

Explain what this server can do, which tools are open to anyone, which need your ChargerDojo account, and each plan with its price and what it unlocks. Answers: what can I do here, what does my plan include, and how do I connect my account.

### `chargerdojo_list_ocpi_versions` (~45 tokens)

OCPI versions

List the OCPI versions ChargerDojo covers, with what each one is for and which modules are implemented. Answers: which OCPI versions can I test against.

### `chargerdojo_get_ocpi_version` (~77 tokens)

One OCPI version

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. Answers: how does this OCPI version work on the wire.

Input parameters:

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

### `chargerdojo_compare_ocpi_versions` (~92 tokens)

Compare two OCPI versions

Compare two OCPI versions: what changed in the protocol between them, and which modules ChargerDojo gained. Answers: what changes when I move from one OCPI version to another.

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` (~108 tokens)

Charging journeys

List the OCPI charging journeys, each with the role it tests, its OCPI versions, the modules the endpoint must offer, the plan it needs against your own endpoint, and how long it runs on the sandbox. Filter by version and role. Answers: which journeys test my role at my OCPI version.

Input parameters:

- `role` (string): Only journeys that test an endpoint playing this OCPI role.
- `version` (string): Only journeys graded at this OCPI version.

### `chargerdojo_get_usage` (~57 tokens)

Plan and usage

Report the plan on this account and how much of each ceiling is left: targets, API keys, runs in flight, run rate and report retention. Answers: which plan am I on, and how close am I to its limits.

### `chargerdojo_list_targets` (~93 tokens)

Endpoints on this account

List the OCPI endpoints registered on this account, 25 a page, with each one's OCPI version, roles and registration status, or read one by id. Answers: which endpoints can I run against.

Input parameters:

- `cursor` (string): Cursor from a previous call. Omit to start at the first target.
- `targetId` (string): Read only this target, by the id a previous list gave.

### `chargerdojo_list_runs` (~127 tokens)

Recent runs

List the conformance runs and charging journeys on this account, newest first and 25 a page, with their status and pass and fail counts, narrowed by target, status or OCPI version. Answers: what ran recently, and how did it go.

Input parameters:

- `cursor` (string): Cursor from a previous call. Omit to start at the newest run.
- `status` (string): Only runs in this status.
- `targetId` (string): Only runs against this target, from chargerdojo_list_targets.
- `version` (string): Only runs at this OCPI version.

### `chargerdojo_list_conformance_suites` (~76 tokens)

Conformance suites

List the OCPI conformance suites that can be run, grouped by version and module, with how many checks each carries. Answers: what does a conformance run check at my OCPI version.

Input parameters:

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

### `chargerdojo_get_run_verdict` (~74 tokens)

Run verdict

Read the verdict of one conformance run or charging journey on this account: how many checks passed, failed and warned, and whether anything graded at all. Answers: did this run pass.

Input parameters:

- `reportId` (string, required): The report id, as returned when the run started or by chargerdojo_list_runs.

### `chargerdojo_list_checks` (~142 tokens)

Checks for one module

List the checks a conformance run of one OCPI module grades at one version: each check id, what it sends, each rule as required or optional with its strength, and the clause of the OCPI spec each rule is graded against, quoted. Answers: what will ChargerDojo hold my module to, and where does the spec say so.

Input parameters:

- `after` (integer): Cursor from a previous call. Omit to start at the first check.
- `module` (string, required): The module, as chargerdojo_list_conformance_suites names it.
- `version` (string, required): The OCPI version, for example 2.2.1.

### `chargerdojo_validate_payload` (~148 tokens)

Validate an OCPI object

Check one OCPI object, sent as JSON text, against the schema ChargerDojo grades that object with at one OCPI version, and list each field that breaks it. The JSON leaves your machine and is sent to chargerdojo.com; it is not stored or logged. Up to 64 KB, 30 calls a minute. Answers: is this a valid OCPI object at my version.

Input parameters:

- `json` (string, required): The object itself as JSON text, without the response envelope.
- `object` (string, required): Which OCPI object the JSON is, for example token or session.
- `version` (string, required): The OCPI version, for example 2.2.1.

### `chargerdojo_get_run_checks` (~132 tokens)

Failed checks and their clauses

Read the checks of one conformance run on this account that failed, could not be graded or carried a warning, each with the rule it broke and the clause of the OCPI spec it was graded against, quoted. Answers: why did this run fail, and what does the spec say.

Input parameters:

- `after` (integer): Cursor from a previous call. Omit to start at the first check.
- `outcome` (string): Only checks with this outcome. Omit for failed, unobservable and warned.
- `reportId` (string, required): The report id, as returned by chargerdojo_list_runs.

### `chargerdojo_compare_run` (~73 tokens)

What changed since the last run

Compare one conformance run with the previous comparable run against the same endpoint, OCPI version and module: which checks newly fail, which recovered, and which stopped being graded. Answers: what changed since my last run.

Input parameters:

- `reportId` (string, required): Report id from chargerdojo_list_runs or a start tool.

### `chargerdojo_get_schedule` (~89 tokens)

Schedule for one endpoint

Read the recurring run set on one target: its cadence, whether it is on or paused and why, when it runs next, and what its last run found. Schedules are set in the app, on the Automate plan. Answers: is my endpoint tested on a schedule, and did its last run pass.

Input parameters:

- `targetId` (string, required): Target id from chargerdojo_list_targets.

### `chargerdojo_get_journey_events` (~78 tokens)

Journey events

Read what happened during a charging journey on this account, step by step, with which assertions passed at each step. Answers: what happened at each step of this journey.

Input parameters:

- `after` (integer): Cursor from a previous call. Omit to start at the beginning.
- `reportId` (string, required): The journey report id.

### `chargerdojo_cancel_run` (~61 tokens)

Cancel a journey

Stop a charging journey that is still running on this account. It stops at the next safe point and keeps whatever it already graded. Answers: how do I stop a journey that is still running.

Input parameters:

- `reportId` (string, required): The journey report id.

### `chargerdojo_list_runnable_journeys` (~79 tokens)

Journeys for one endpoint

List the charging journeys that can run against one target on this account, say why the target supports them, and name the plan any of them needs that this account does not have. Answers: which journeys fit this endpoint, by its role and version.

Input parameters:

- `targetId` (string, required): Target id from chargerdojo_list_targets.

### `chargerdojo_run_sandbox_journey` (~115 tokens)

Run a sandbox journey

Run an OCPI charging journey against a sandbox endpoint. Answers: how do I try a journey without an endpoint of my own.

Input parameters:

- `retryKey` (string): A key of your choosing for this run. Calling again with the same key returns the run it started instead of starting another. Omit it to start a new run on every call.
- `templateId` (string): Journey to run, from chargerdojo_list_journey_templates. Omit to run the shortest one that fits a sandbox endpoint.

### `chargerdojo_run_journey` (~172 tokens)

Run a journey on an endpoint

Run an OCPI charging journey against an endpoint registered on this account, the sandbox or your own, and return its report id. Against your own endpoint it needs the Integrate plan, and a few journeys need a higher one, which chargerdojo_list_journey_templates names. Answers: does my endpoint pass this journey.

Input parameters:

- `retryKey` (string): A key of your choosing for this run. Calling again with the same key returns the run it started instead of starting another. Omit it to start a new run on every call.
- `targetId` (string, required): The registered endpoint to run against, from chargerdojo_list_targets.
- `templateId` (string): Journey to run, from chargerdojo_list_runnable_journeys. Omit to run the shortest one that fits the endpoint.

### `chargerdojo_start_conformance_run` (~181 tokens)

Start a conformance run

Start a conformance run against an endpoint registered on this account, the sandbox or your own: one module, or every module the endpoint offers. Returns the report id at once. Against your own endpoint it needs the Integrate plan, and a module sold on a higher plan names it. Answers: does my endpoint conform to OCPI.

Input parameters:

- `module` (string): One module to grade, at the endpoint's OCPI version; chargerdojo_list_checks lists its checks. Omit to grade every module the endpoint offers.
- `retryKey` (string): A key of your choosing for this run. Calling again with the same key returns the run it started instead of starting another. Omit it to start a new run on every call.
- `targetId` (string, required): The registered endpoint to run against, from chargerdojo_list_targets.

## Diagnostics

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

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 80
- 2026-10-29: 80
- 2026-10-28: 79
- 2026-10-27: 79
- 2026-10-26: 78
- 2026-10-25: 78
- 2026-10-24: 77
- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 76
- 2026-10-20: 76
- 2026-10-19: 75
- 2026-10-18: 75
- 2026-10-17: 74

## 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://mcp.chargerdojo.com).

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

ChargerDojo scores 75 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 21 tools: chargerdojo_describe_access, chargerdojo_list_ocpi_versions, chargerdojo_get_ocpi_version, chargerdojo_compare_ocpi_versions, chargerdojo_list_journey_templates, and 16 more. Their descriptions and schemas cost roughly 2,086 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 5 November 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://mcp.chargerdojo.com/
- Website: https://chargerdojo.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-chargerdojo-ocpi/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-chargerdojo-ocpi/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-chargerdojo-ocpi/mcp