ChargerDojo

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

• Verbindung: Läuft in der Cloud
• Transport: Streamable HTTP
• Kategorie: Sonstiges

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Du brauchst

• Läuft in der CloudNichts zu installieren; die Verbindung läuft übers Internet

Welche App nutzt du?

https://mcp.chargerdojo.com

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

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

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

https://mcp.chargerdojo.com

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Tool-Namen und -Beschreibungen genau so, wie der Server sie am 6. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.

• chargerdojo_describe_access

  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

  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

  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.

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

• chargerdojo_list_journey_templates

  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 vers

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

  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.

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

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

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

• chargerdojo_list_checks

  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, an

• chargerdojo_validate_payload

  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. Answe

• chargerdojo_get_run_checks

  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.

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

• chargerdojo_get_schedule

  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.

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

• chargerdojo_cancel_run

  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.

• chargerdojo_list_runnable_journeys

  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.

• chargerdojo_run_sandbox_journey

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

• chargerdojo_run_journey

  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: do

• chargerdojo_start_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. Ans

• chargerdojo_send_feedback

  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.

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026

• ! Vorsicht

  Entwickler passt zum Repo

  Die Registry nennt kein Quell-Repo, deshalb können wir den Herausgeber (chargerdojo.com) nicht dem Code zuordnen

• … Noch nicht geprüft

  Wird noch gepflegt

  Dieses Repo haben wir noch nicht von GitHub gelesen

• … Noch nicht geprüft

  Hat eine Lizenz

  Dieses Repo haben wir noch nicht von GitHub gelesen

• ✓ Bestanden

  Endpunkt antwortet

  Antwort in 801 ms (HTTP 200)

• – Nicht zutreffend

  Anmeldung mit OAuth

  Keine Anmeldung nötig

• ✓ Bestanden

  Keine versteckten Anweisungen in Tool-Beschreibungen

  Wir haben 22 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Im Vergleich mit anderen in Sonstigesi

• Mehr Sterne als 0 % der anderen 32623 Server in dieser Kategorie
• Neuer in der Registry veröffentlicht als 97 % der anderen 32623 Server in dieser Kategorie
• Basischecks gleich gut wie oder besser als bei 37 % der anderen 32623 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

README vom Entwickler

Keine README im Repo gefunden