ChargerDojo

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as com.chargerdojo/ocpi and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 22 Sept 2026. Not supplied by the maker.

• chargerdojo_describe_access

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

• chargerdojo_list_ocpi_versions

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

• chargerdojo_get_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.

• chargerdojo_compare_ocpi_versions

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

• chargerdojo_list_journey_templates

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

• chargerdojo_list_conformance_suites

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

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.