ChargerDojo
REMOTE · MCP.CHARGERDOJO.COM
OCPI versions, what changed between them, and which modules and journeys ChargerDojo tests.
Available components
Last scanned (6 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Testing and QA
Recent critical change
Authorization (3 Nov 2026). See the changelog before you install this server.
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (chargerdojo_cancel_run). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 −6
- Authorization: partial → fail ▼ critical
- 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 security
- 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” functional
- “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 cosmetic
- 31 Oct 26 +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.
- 30 Oct 26 0
- Tool “chargerdojo_list_journey_templates” rewrote its description, which is the text the model reads security
- Server version: 1.3.3 → 1.3.4 functional
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 22 Oct 26 +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.
- 20 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.chargerdojo.com
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chargerdojo.com | CN=YE2,O=Let's Encrypt,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5bfbc813d19cfbc25356fc4c60f1ccbe4b5 |
| SANs: *.chargerdojo.com, chargerdojo.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.chargerdojo.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| chargerdojo.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' data:;form-action 'self';frame-ancestors 'self';img-src 'self' data: https:;object-src 'none';script-src 'self' https://www.googletagmanager.com https://static.cloudflareinsights.com https://analytics.ahrefs.com https://us-assets.i.posthog.com https://*.clarity.ms;script-src-attr 'none';style-src 'self' 'unsafe-inline';upgrade-insecure-requests;connect-src 'self' https://synergyboat.us.auth0.com https://*.google-analytics.com https://www.googletagmanager.com https://cloudflareinsights.com https://analytics.ahrefs.com https://us.i.posthog.com https://us-assets.i.posthog.com https://*.clarity.ms https://c.bing.com;frame-src 'self' https://synergyboat.us.auth0.com;worker-src 'self' blob: |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.chargerdojo.com | Verified | 200 | |
| http (plaintext) | http://mcp.chargerdojo.com | HTTPS enforced | 301 | https://mcp.chargerdojo.com/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
chargerdojo_cancel_run Cancel a journey ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| reportId | string | yes | The journey report id. |
No output schema declared.
No examples provided.
chargerdojo_compare_ocpi_versions Compare two OCPI versions ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | The version being moved away from, for example 2.1.1. |
| to | string | yes | The version being moved to, for example 2.2.1. |
No output schema declared.
No examples provided.
chargerdojo_compare_run What changed since the last run ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| reportId | string | yes | Report id from chargerdojo_list_runs or a start tool. |
No output schema declared.
No examples provided.
chargerdojo_describe_access What this server offers ~67
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
chargerdojo_get_journey_events Journey events ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | – | Cursor from a previous call. Omit to start at the beginning. |
| reportId | string | yes | The journey report id. |
No output schema declared.
No examples provided.
chargerdojo_get_ocpi_version One OCPI version ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| version | string | yes | OCPI version, for example 2.2.1. |
No output schema declared.
No examples provided.
chargerdojo_get_run_checks Failed checks and their clauses ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The report id, as returned by chargerdojo_list_runs. |
No output schema declared.
No examples provided.
chargerdojo_get_run_verdict Run verdict ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| reportId | string | yes | The report id, as returned when the run started or by chargerdojo_list_runs. |
No output schema declared.
No examples provided.
chargerdojo_get_schedule Schedule for one endpoint ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| targetId | string | yes | Target id from chargerdojo_list_targets. |
No output schema declared.
No examples provided.
chargerdojo_get_usage Plan and usage ~57
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
chargerdojo_list_checks Checks for one module ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | – | Cursor from a previous call. Omit to start at the first check. |
| module | string | yes | The module, as chargerdojo_list_conformance_suites names it. |
| version | string | yes | The OCPI version, for example 2.2.1. |
No output schema declared.
No examples provided.
chargerdojo_list_conformance_suites Conformance suites ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| version | string | – | Optional OCPI version to narrow to, for example 2.2.1. |
No output schema declared.
No examples provided.
chargerdojo_list_journey_templates Charging journeys ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| role | string | – | Only journeys that test an endpoint playing this OCPI role. |
| version | string | – | Only journeys graded at this OCPI version. |
No output schema declared.
No examples provided.
chargerdojo_list_ocpi_versions OCPI versions ~45
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
chargerdojo_list_runnable_journeys Journeys for one endpoint ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| targetId | string | yes | Target id from chargerdojo_list_targets. |
No output schema declared.
No examples provided.
chargerdojo_list_runs Recent runs ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
chargerdojo_list_targets Endpoints on this account ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
chargerdojo_run_journey Run a journey on an endpoint ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
chargerdojo_run_sandbox_journey Run a sandbox journey ~115
Run an OCPI charging journey against a sandbox endpoint. Answers: how do I try a journey without an endpoint of my own.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
chargerdojo_start_conformance_run Start a conformance run ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The registered endpoint to run against, from chargerdojo_list_targets. |
No output schema declared.
No examples provided.
chargerdojo_validate_payload Validate an OCPI object ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| json | string | yes | The object itself as JSON text, without the response envelope. |
| object | string | yes | Which OCPI object the JSON is, for example token or session. |
| version | string | yes | The OCPI version, for example 2.2.1. |
No output schema declared.
No examples provided.
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.
remote · mcp.chargerdojo.com
claude mcp add --transport http com-chargerdojo-ocpi 'https://mcp.chargerdojo.com/'
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.