accueil / serveurs / Géo & Temps / io.github.cyanheads/openchargemap-mcp-server
io.github.cyanheads/openchargemap-mcp-server
serveur MCP (Model Context Protocol) · openchargemap-mcp-server 0.1.10
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.cyanheads/openchargemap-mcp-server est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.cyanheads/openchargemap-mcp-server » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 4 outils
- openchargemap_find_stations≈ 3860 tokens
Find EV charging stations from the global Open Charge Map registry near a point or within a bounding box. Provide either a center (latitude + longitude + distance) or a boundingbox; optionally scope to a country with countrycode. This tool is coordinate-native and does not geocode place names — resolve a place like "Ballard, Seattle" to coordinates with openstreetmap_search_places first, then pass them here. Filter by connector type, minimum power (kW), operator/network, usage type (public/free/membership), charge level, operational status, and minimum charge points. Filter IDs are integers — resolve a connector or network name to its ID with openchargemap_lookup_reference (e.g. "CCS" -> 33). Each result includes title, address, distance from the search point, connections (type, power, count), operator, access rules, registry operational status, and the last-verified date. Results come back one page at a time: when a page reports truncated, repeat the same search with the reported nextOffset to read the next one.
Paramètres, retour & exemple (15)
Paramètresoffset· integer · optionnel
Matching stations to skip before the returned page, for reading past a truncated result. Repeat the same search with the nextOffset value the previous call reported. One search reaches at most 500 stations, so 499 is the deepest offset that can return one — narrow the area or add filters to reach stations beyond that. Ordering is by distance and stable, but Open Charge Map is edited continuously, so a station added or removed between pages can shift what a later offset lands on.levelid· ? · optionnel
Charge level ID (1=Low <2kW, 2=Medium >2kW, 3=High >40kW/fast). Array OR-matched. Use 3 as a coarse "fast charging only" filter when a specific connector is not required.distance· number · optionnel
Search radius from the center point, in the unit given by distanceUnit (default km). Max 500. Keep small (5-25) for dense urban areas; widen for rural coverage.latitude· number · optionnel
Center latitude (WGS84 decimal degrees). Use with longitude + distance for a radius search. Resolve place names via openstreetmap_search_places first.longitude· number · optionnel
Center longitude (WGS84 decimal degrees). Use with latitude + distance for a radius search.maxresults· integer · optionnel
Maximum stations to return, ordered by distance from the search point. Max 200.minpowerkw· number · optionnel
Minimum charging power in kW across any connection at the station. Use ~50 for DC fast charging, ~150 for high-power DC. Stations whose fastest connection is below this are excluded.operatorid· ? · optionnel
Operator/network ID, or array of IDs (OR-matched). Resolve a network name with openchargemap_lookup_reference (category "operators") — e.g. "Tesla", "ChargePoint".boundingbox· object · optionnel
Bounding-box search as an alternative to a center+radius. Mutually exclusive with latitude/longitude/distance — sending a boundingbox alongside a latitude or a longitude is rejected, not resolved in favour of one of them.countrycode· string · optionnel
Restrict to one country by ISO 3166-1 alpha-2 code (e.g. "US", "FR", "GB"). Omit for a global search. The server is global by default — there is no implicit country.usagetypeid· ? · optionnel
Usage/access type ID, or array (OR-matched). Resolve via openchargemap_lookup_reference (category "usagetypes") — e.g. Public=1, Public-Pay At Location=5, Public-Membership Required=4.distanceUnit· string · optionnel · KM | Miles
Unit for the distance parameter and the returned distance values.statustypeid· ? · optionnel
Registry operational-status ID, or array (OR-matched). Resolve via openchargemap_lookup_reference (category "statustypes"). NOTE: registry status is operator-reported and can be stale — combine with dateLastVerified and openchargemap_get_station_comments to judge real-world reliability, do not treat it as ground truth.minchargepoints· integer · optionnel
Minimum number of charge points (stalls) at the station. Filters out single-point locations when you need a station likely to have an open stall.connectiontypeid· ? · optionnel
Connector type ID, or an array of IDs (OR-matched). Resolve names with openchargemap_lookup_reference — e.g. CCS (Type 2)=33, CHAdeMO=2, NACS/Tesla Supercharger=27, Type 2 socket=25, Type 1/J1772=1.
Exemple d'appel{"name": "openchargemap_find_stations", "arguments": {"offset": 1, "levelid": "texte", "distance": 1, "latitude": 1, "longitude": 1, "maxresults": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"cap": 1, "error": {}, "shown": 1, "notice": "texte", "stations": [], "truncated": true, "nextOffset": 1, "totalCount": 1, "attribution": "texte", "searchSummary": "texte"}} - openchargemap_get_station≈ 2588 tokens
Get the full record for one Open Charge Map station by its numeric OCM ID. Returns every connection (type, level, power, current, quantity, per-connection status), the operator and network, usage and access restrictions (pay-at-location, membership, access key), the number of charge points, general comments, usage cost, the data provider, media, and verification recency. Set includeComments to also return community check-ins inline.
Paramètres, retour & exemple (2)
Paramètresid· integer · requis
Numeric OCM station ID (e.g. 145452).includeComments· boolean · optionnel
Include community check-ins and comments inline in the response. Adds payload but gives the real-world reliability signal alongside the registry status. Every comment on record comes back at once, unpaged — on a station with hundreds of check-ins that is a large response, so prefer openchargemap_get_station_comments, which returns them a page at a time.
Exemple d'appel{"name": "openchargemap_get_station", "arguments": {"id": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "station": {}, "attribution": "texte", "reliabilityNote": "texte"}} - openchargemap_get_station_comments≈ 1758 tokens
Read community check-ins and comments for one Open Charge Map station — the real-world reliability signal beyond the operator-reported registry status. Returns user comments and fault reports with ratings, dates, and the outcome the driver recorded ("Charged Successfully", "Failed to Charge (Equipment Not Operational)", …), alongside the station's current registry status and last-verified date, surfacing mismatches like "listed operational, but the last few check-ins report a fault." A busy station's check-ins come back one page at a time: when a page reports truncated, repeat the call with the reported nextOffset to read the next one.
Paramètres, retour & exemple (3)
Paramètresid· integer · requis
Numeric OCM station ID.offset· integer · optionnel
Comments to skip before the returned page, for reading past a truncated result. Repeat the same call with the nextOffset value the previous one reported. Ordering is newest-first and stable, but a check-in posted between pages shifts what a later offset lands on.maxresults· integer · optionnel
Maximum comments to return, newest first. Max 100.
Exemple d'appel{"name": "openchargemap_get_station_comments", "arguments": {"id": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"cap": 1, "error": {}, "shown": 1, "notice": "texte", "comments": [], "stationId": 1, "truncated": true, "nextOffset": 1, "totalCount": 1, "attribution": "texte", "stationTitle": "texte", "isOperational": true}} - openchargemap_lookup_reference≈ 1529 tokens
Resolve Open Charge Map reference data to the integer IDs that openchargemap_find_stations filters require. Pick a category and pass a name or code to resolve — "CCS" or "Tesla Supercharger" -> a connectiontypeid, "ChargePoint" -> an operatorid, "Public - Pay At Location" -> a usagetypeid, "France" or "FR" -> a country. Omit the query to browse the whole category. Large categories come back one page at a time: when a page reports truncated, repeat the call with the reported nextOffset to read the next one.
Paramètres, retour & exemple (4)
Paramètreslimit· integer · optionnel
Maximum entries to return when browsing or when a query matches several. Max 100.query· string · optionnel
Name, title, code, or alias to resolve (e.g. "CCS", "CHAdeMO", "Tesla", "Public", "France", "FR"). Case-insensitive, matches on title, formal name, and known aliases. Omit to browse the entire category.offset· integer · optionnel
Entries to skip before the returned page, for reading past a truncated result. Repeat the same call with the nextOffset value the previous one reported. Applies to browsing and to a query with many matches alike; the order is stable, so every entry is reachable by paging.category· string · requis · connectiontypes | operators | usagetypes | statustypes | currenttypes | levels | countries
Which reference set to query. connectiontypes -> connectiontypeid; operators -> operatorid; usagetypes -> usagetypeid; statustypes -> statustypeid; currenttypes -> current type; levels -> charge level (1/2/3); countries -> ISO country.
Exemple d'appel{"name": "openchargemap_lookup_reference", "arguments": {"category": "connectiontypes"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"cap": 1, "error": {}, "shown": 1, "notice": "texte", "source": "live", "matches": [], "category": "texte", "truncated": true, "nextOffset": 1, "totalCount": 1, "attribution": "texte", "filterParam": "texte"}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».