Ladepunktdaten
REMOTE · WWW.LADEPUNKTDATEN.DE
Ladesäulenregister der Bundesnetzagentur: Suche, Regionalstatistik, Änderungen, Export je Region.
Available components
Last scanned (3 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 26 Oct 26 +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.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://www.ladepunktdaten.de/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.ladepunktdaten.de | CN=YE2,O=Let's Encrypt,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5619d2750ef7bfe4e562ee2b9a67348418c |
| SANs: www.ladepunktdaten.de | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.ladepunktdaten.de. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| de. | present | 26755 | 8 | Verified |
| ladepunktdaten.de. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.ladepunktdaten.de/mcp | Verified | 200 | |
| http (plaintext) | http://www.ladepunktdaten.de/mcp | HTTPS enforced | 308 | https://www.ladepunktdaten.de/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
dataset_info Datensatz-Information ~82
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
region_statistics Regionalstatistik ~208
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ebene | string | yes | Ebene der Region / Level |
| name | string | yes | Name bzw. PLZ(-Präfix), z. B. 'Sachsen', 'Landkreis Leipzig', 'Leipzig', '04109' / Name or postal code (prefix) |
No output schema declared.
No examples provided.
register_changes Registeränderungen 01.09. bis 30.09.2026 ~415
Ä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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
search_charging_stations Ladeeinrichtungen suchen ~484
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
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.
remote · www.ladepunktdaten.de
claude mcp add --transport http de-ladepunktdaten-ladesaeulen 'https://www.ladepunktdaten.de/mcp'
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.