Skip to main content
Glama

ChargerDojo

Server Details

OCPI versions, checks and payload validation, plus your own test runs and run starts with a key.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 22 tools

Disambiguation4/5

Most tools map to a distinct resource+action pair (get_run_verdict vs get_run_checks vs compare_run, list_ocpi_versions vs get_ocpi_version vs compare_ocpi_versions), and descriptions reinforce the boundaries. The main overlap is chargerdojo_run_sandbox_journey versus chargerdojo_run_journey, whose description already covers the sandbox, and list_journey_templates vs list_runnable_journeys requires reading carefully to separate the catalog from the target-filtered view.

Naming Consistency5/5

Every tool uses the chargerdojo_ prefix followed by a consistent verb_noun pattern (list_runs, get_run_verdict, compare_ocpi_versions, run_journey, validate_payload). No camelCase or stale verbs mixed in, so a predictable family emerges: list/get/compare/run/cancel/send/describe.

Tool Count4/5

22 tools is on the heavy side, but the domain genuinely spans targets, conformance suites, checks, journeys, runs, schedules, usage and payload validation. Only marginal redundancy exists (the sandbox journey runner duplicating run_journey's sandbox option), otherwise each tool answers a distinct question.

Completeness3/5

Read paths and the run lifecycle (list targets, start/conformance/journey runs, verdict, checks, compare, cancel) are well covered, but management operations are missing: no way to register or remove a target endpoint, no API key handling, no way to create or pause a schedule despite get_schedule existing, and no cancel for conformance runs. These gaps push agents back to the web app for core setup workflows.

Available Tools

22 tools
chargerdojo_cancel_runCancel a journeyA
Destructive
Inspect

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.

Inputs: reportId (required).

chargerdojo_compare_ocpi_versionsCompare two OCPI versionsA
Read-only
Inspect

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.

Inputs: to (required), from (required).

chargerdojo_compare_runWhat changed since the last runA
Read-only
Inspect

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.

Inputs: reportId (required).

chargerdojo_describe_accessWhat this server offersA
Read-only
Inspect

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.

Inputs: no named parameters.

chargerdojo_get_journey_eventsJourney eventsA
Read-only
Inspect

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.

Inputs: reportId (required), after.

chargerdojo_get_ocpi_versionOne OCPI versionA
Read-only
Inspect

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.

Inputs: version (required).

chargerdojo_get_run_checksConformance check evidenceA
Read-only
Inspect

Read the checks of one conformance run on this account that failed, could not be graded or carried a warning. Quotes recorded OCPI clauses and identifies rules without one. Answers: why did this run fail, and what does the spec say.

Inputs: reportId (required), after, outcome.

chargerdojo_get_run_verdictRun verdictA
Read-only
Inspect

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. Production read-only runs name withheld writes as not tested with their reason. Answers: did this run pass.

Inputs: reportId (required).

chargerdojo_get_scheduleSchedule for one endpointA
Read-only
Inspect

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.

Inputs: targetId (required).

chargerdojo_get_usagePlan and usageA
Read-only
Inspect

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.

Inputs: no named parameters.

chargerdojo_list_checksChecks for one moduleA
Read-only
Inspect

List the checks a conformance run of one OCPI module grades at one version, what they send and which rules are required or optional. Quotes recorded OCPI clauses and identifies rules without one. Answers: what will ChargerDojo hold my module to, and what does the spec say.

Inputs: module (required), version (required), after.

chargerdojo_list_conformance_suitesConformance suitesA
Read-only
Inspect

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.

Inputs: version.

chargerdojo_list_journey_templatesCharging journeysA
Read-only
Inspect

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.

Inputs: role, version.

chargerdojo_list_ocpi_versionsOCPI versionsA
Read-only
Inspect

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.

Inputs: no named parameters.

chargerdojo_list_runnable_journeysJourneys for one endpointA
Read-only
Inspect

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.

Inputs: targetId (required).

chargerdojo_list_runsRecent runsA
Read-only
Inspect

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.

Inputs: cursor, status, version, targetId.

chargerdojo_list_targetsEndpoints on this accountA
Read-only
Inspect

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.

Inputs: cursor, targetId.

chargerdojo_run_journeyRun a journey on an endpointAInspect

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.

Inputs: targetId (required), retryKey, templateId.

chargerdojo_run_sandbox_journeyRun a sandbox journeyBInspect

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

Inputs: retryKey, templateId.

chargerdojo_send_feedbackSend feedbackAInspect

Send a message to the people who build ChargerDojo: something missing, a bug, a question, or a verdict the person believes is wrong. Returns a reference.

Inputs: kind (required), message (required), tool, checkId, +1 more.

chargerdojo_start_conformance_runStart a conformance runAInspect

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.

Inputs: targetId (required), module, retryKey.

chargerdojo_validate_payloadValidate an OCPI objectA
Read-only
Inspect

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.

Inputs: json (required), object (required), version (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources