# Ladepunktdaten (remote · www.ladepunktdaten.de)

Ladesäulenregister der Bundesnetzagentur: Suche, Regionalstatistik, Änderungen, Export je Region.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.ladepunktdaten.de`: 74/100 (this document), [markdown](https://verifymcp.io/servers/de-ladepunktdaten-ladesaeulen/www.md), [page](https://verifymcp.io/servers/de-ladepunktdaten-ladesaeulen/www)

## Channel facts

- Endpoint: `https://www.ladepunktdaten.de/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1326 tokens (~331/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Ladepunktdaten MCP server?

Ladepunktdaten is a hosted endpoint at https://www.ladepunktdaten.de/mcp, 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.

### Claude

```bash
claude mcp add --transport http de-ladepunktdaten-ladesaeulen 'https://www.ladepunktdaten.de/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "de-ladepunktdaten-ladesaeulen": {
      "url": "https://www.ladepunktdaten.de/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "de-ladepunktdaten-ladesaeulen": {
      "type": "http",
      "url": "https://www.ladepunktdaten.de/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.de-ladepunktdaten-ladesaeulen]
url = "https://www.ladepunktdaten.de/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "de-ladepunktdaten-ladesaeulen": {
      "type": "remote",
      "url": "https://www.ladepunktdaten.de/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add de-ladepunktdaten-ladesaeulen --url 'https://www.ladepunktdaten.de/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  de-ladepunktdaten-ladesaeulen:
    url: "https://www.ladepunktdaten.de/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "de-ladepunktdaten-ladesaeulen": {
      "Transport": "http",
      "Url": "https://www.ladepunktdaten.de/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add de-ladepunktdaten-ladesaeulen -t streamable-http -u 'https://www.ladepunktdaten.de/mcp'
```

### Other

```json
{
  "mcpServers": {
    "de-ladepunktdaten-ladesaeulen": {
      "type": "http",
      "url": "https://www.ladepunktdaten.de/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 71, +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.

### 2026-10-26 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 69)

First indexed and scored.

## MCP tools (4)

### `search_charging_stations` (~484 tokens)

Ladeeinrichtungen suchen

Sucht Ladeeinrichtungen im Ladesäulenregister der Bundesnetzagentur (Stand 30.09.2026). Mindestens ein Ortsfilter (plz, ort, kreis, bundesland) oder betreiber ist nötig. Liefert die Gesamtzahl der Treffer und bis zu 'limit' Einrichtungen (id, betreiber, adresse, plz, ort, kreis, bundesland, lat, lon, inbetriebnahme, ladepunkte, ladepunkt_leistungen_kw, summe_kw, max_kw, schnellladepunkte, steckertypen), sortiert nach Summe der Nennleistungen der Ladepunkte. Betreiber ohne erkennbare Rechtsform erscheinen nicht namentlich, Adresse und Koordinaten sind dort vergröbert.
Searches charging stations in the German federal charging register (as of 2026-09-30). At least one location filter or 'betreiber' is required. Returns total hit count and up to 'limit' stations, sorted by power.

Input parameters:

- `betreiber` (string): Teilstring des Betreibernamens (nur Betreiber mit erkennbarer Rechtsform), z. B. 'EnBW' / Operator name substring (legal entities only)
- `bundesland` (string): Bundesland, z. B. 'Sachsen' / Federal state
- `kreis` (string): Kreis oder kreisfreie Stadt, z. B. 'Leipzig' oder 'Landkreis Leipzig' / District
- `limit` (integer): Maximale Zahl Treffer in der Liste (Standard 20, max. 50) / Max results
- `min_kw` (number): Mindestens ein Ladepunkt der Einrichtung hat diese Nennleistung in kW / At least one charge point has this rated power (kW) or more
- `nur_schnellladen` (boolean): Nur Einrichtungen mit mindestens einem Schnellladepunkt (Ladepunkt über 22 kW, § 2 LSV) / Only stations with at least one fast charging point (above 22 kW)
- `ort` (string): Ortsname, z. B. 'Leipzig' / Town or city name
- `plz` (string): Postleitzahl oder Präfix, z. B. '04' oder '04109' / Postal code or prefix

### `region_statistics` (~208 tokens)

Regionalstatistik

Kennzahlen für eine Region: Einrichtungen, Ladepunkte, Summe der Nennleistungen je Ladepunkt (kW), Schnellladepunkte (über 22 kW) und ihr Anteil, Verteilung der Ladepunkte auf kW-Klassen, Top-10-Betreiber (nur mit erkennbarer Rechtsform, Rest als Sammelposten) und Inbetriebnahmen der letzten 5 Jahre. Bei mehrdeutigen oder unbekannten Namen kommen Vorschläge zurück.
Key figures for a region: stations, charge points, total kW, fast-charging share, kW classes, top-10 operators, commissioning per year (last 5 years). Ambiguous or unknown names return suggestions.

Input parameters:

- `ebene` (string, required): Ebene der Region / Level
- `name` (string, required): Name bzw. PLZ(-Präfix), z. B. 'Sachsen', 'Landkreis Leipzig', 'Leipzig', '04109' / Name or postal code (prefix)

### `register_changes` (~415 tokens)

Registeränderungen 01.09. bis 30.09.2026

Änderungen im Ladesäulenregister zwischen den Registerständen 01.09.2026 und 30.09.2026: neu gemeldet, aus dem Register entfernt (Ursache unbekannt, nicht gleich stillgelegt), Felder geändert. Filter wie bei der Suche, alle optional. Zählungen sind immer vollständig; Einzeldatensätze nur als Probe (max. 10, ohne Alt-/Neuwerte, nur Namen der geänderten Felder).
Changes in the register between the 2026-09-01 and 2026-09-30 snapshots. Counts are complete; individual records are a sample of at most 10 (field names only, no old/new values).

Input parameters:

- `art` (string): Art der Änderung für die Probe / Kind of change for the sample
- `betreiber` (string): Teilstring des Betreibernamens (nur Betreiber mit erkennbarer Rechtsform), z. B. 'EnBW' / Operator name substring (legal entities only)
- `bundesland` (string): Bundesland, z. B. 'Sachsen' / Federal state
- `kreis` (string): Kreis oder kreisfreie Stadt, z. B. 'Leipzig' oder 'Landkreis Leipzig' / District
- `min_kw` (number): Mindestens ein Ladepunkt der Einrichtung hat diese Nennleistung in kW / At least one charge point has this rated power (kW) or more
- `nur_schnellladen` (boolean): Nur Einrichtungen mit mindestens einem Schnellladepunkt (Ladepunkt über 22 kW, § 2 LSV) / Only stations with at least one fast charging point (above 22 kW)
- `ort` (string): Ortsname, z. B. 'Leipzig' / Town or city name
- `plz` (string): Postleitzahl oder Präfix, z. B. '04' oder '04109' / Postal code or prefix

### `dataset_info` (~82 tokens)

Datensatz-Information

Verfügbare Stichtage, Zeilenzahl, Lizenz, Aktualisierungsrhythmus und Meldeverzug (Median der Tage zwischen Inbetriebnahme und Erscheinen im Register, berechnet aus den Neumeldungen).
Available snapshot dates, row counts, license, update cadence and reporting lag (median days from commissioning to appearing in the register).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/de-ladepunktdaten-ladesaeulen/www#diagnostics

## Score history

- 2026-11-05: 74
- 2026-11-04: 74
- 2026-11-03: 73
- 2026-11-02: 73
- 2026-11-01: 72
- 2026-10-31: 72
- 2026-10-30: 71
- 2026-10-29: 71
- 2026-10-28: 70
- 2026-10-27: 70
- 2026-10-26: 70
- 2026-10-25: 69
- 2026-10-24: 69

## Common questions

### What is the Ladepunktdaten MCP server?

Ladepunktdaten is an MCP server listed in the public MCP registry as de.ladepunktdaten/ladesaeulen. Ladesäulenregister der Bundesnetzagentur: Suche, Regionalstatistik, Änderungen, Export je Region. This page covers its hosted endpoint (https://www.ladepunktdaten.de/mcp).

### Is the Ladepunktdaten MCP server safe to use?

Ladepunktdaten scores 74 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 Ladepunktdaten MCP server expose?

Ladepunktdaten exposes 4 tools: search_charging_stations, region_statistics, register_changes, dataset_info. Their descriptions and schemas cost roughly 1,189 tokens of context every time the server is loaded.

### Does the Ladepunktdaten MCP server require authentication?

No. We connected to Ladepunktdaten without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Ladepunktdaten MCP server still maintained?

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

### What did VerifyMCP test on the Ladepunktdaten MCP server?

VerifyMCP ran 13 checks on Ladepunktdaten, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://www.ladepunktdaten.de/mcp
- Website: https://www.ladepunktdaten.de/ladeinfrastruktur/mcp
- Changelog RSS feed: https://verifymcp.io/servers/de-ladepunktdaten-ladesaeulen/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/de-ladepunktdaten-ladesaeulen/www/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/de-ladepunktdaten-ladesaeulen/www.json
- HTML version of this page: https://verifymcp.io/servers/de-ladepunktdaten-ladesaeulen/www