Skip to content

ChargerDojo

by chargerdojo.com · remote · no sign-in to list tools · v1.3.3 · published by com.chargerdojo

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

Read only

6 tools: 6 only read.

Scanned Oct 21, 2026

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http ocpi https://mcp.chargerdojo.com

Findings

Matches of fixed checks, with the text they matched.

1 info

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

6 tools

Only reads 6Claude Code: allow
  • chargerdojo_compare_ocpi_versionsCompare two OCPI versions: what changed in the protocol between them, and which modules ChargerDojo gained.No findings

    Why it is in this group

    • The name "chargerdojo_compare_ocpi_versions" says "compare": a word for reading.
    Description, as the server wrote it
    Compare two OCPI versions: what changed in the protocol between them, and which modules ChargerDojo gained.

    Annotations the server declares

    • readOnlyHint: true
  • chargerdojo_describe_accessExplain what this server can do, which tools are open to anyone, and which need a ChargerDojo API key.No findings

    Why it is in this group

    • The name "chargerdojo_describe_access" says "describe": a word for reading.
    Description, as the server wrote it
    Explain what this server can do, which tools are open to anyone, and which need a ChargerDojo API key.

    Annotations the server declares

    • readOnlyHint: true
  • chargerdojo_get_ocpi_versionDescribe 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.1 finding

    Why it is in this group

    • The name "chargerdojo_get_ocpi_version" says "get": a word for reading.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "Describe one OCPI version: how the credentials token is encoded, whether endpoints spl..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • chargerdojo_list_conformance_suitesList the OCPI conformance suites that can be run, grouped by module, with how many checks each carries.No findings

    Why it is in this group

    • The name "chargerdojo_list_conformance_suites" says "list": a word for reading.
    Description, as the server wrote it
    List the OCPI conformance suites that can be run, grouped by module, with how many checks each carries.

    Annotations the server declares

    • readOnlyHint: true
  • chargerdojo_list_journey_templatesList the OCPI charging journeys that can be run against the built-in sandbox, with how long each takes.No findings

    Why it is in this group

    • The name "chargerdojo_list_journey_templates" says "list": a word for reading.
    Description, as the server wrote it
    List the OCPI charging journeys that can be run against the built-in sandbox, with how long each takes.

    Annotations the server declares

    • readOnlyHint: true
  • chargerdojo_list_ocpi_versionsList the OCPI versions ChargerDojo covers, with what each one is for and which modules are implemented.No findings

    Why it is in this group

    • The name "chargerdojo_list_ocpi_versions" says "list": a word for reading.
    Description, as the server wrote it
    List the OCPI versions ChargerDojo covers, with what each one is for and which modules are implemented.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.3.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http ocpi https://mcp.chargerdojo.com

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ocpi__chargerdojo_describe_access",
      "mcp__ocpi__chargerdojo_list_ocpi_versions",
      "mcp__ocpi__chargerdojo_get_ocpi_version",
      "mcp__ocpi__chargerdojo_compare_ocpi_versions",
      "mcp__ocpi__chargerdojo_list_journey_templates",
      "mcp__ocpi__chargerdojo_list_conformance_suites"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as ocpi. Review it before you use it.