openchargemap-mcp-server

Name: openchargemap-mcp-server
Author: cyanheads

Server Details

Find EV charging stations, detail, and reliability check-ins via the global Open Charge Map.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 99.9% over 42 days
Last Tested: 2026-09-28 01:34
Transport: Streamable HTTP · MCP 2025-11-25
URL
Repository: cyanheads/openchargemap-mcp-server
GitHub Stars: 1
Server Listing: @cyanheads/openchargemap-mcp-server

TDQS

A4.7/5.0

Scored 2026-09-20 19:51 across 4 tools

Disambiguation5/5

Each tool targets a distinct operation: searching stations, retrieving a single station record, reading community comments, and resolving reference-data IDs. The only slight overlap is get_station optionally including comments, but the dedicated comments tool is clearly differentiated by its purpose and richer check-in details.

Naming Consistency5/5

All tool names use the consistent openchargemap_ verb_noun pattern in snake_case. The verbs find, get, and lookup are predictable and match the object being acted on.

Tool Count5/5

Four tools form a compact, well-scoped read-only surface for the Open Charge Map registry. Each tool serves a clear purpose without redundancy or excessive fragmentation.

Completeness5/5

The set covers the full read-only lifecycle: find stations, get detailed station records, read community reliability comments, and resolve filter reference data. Pagination is handled consistently, and the explicit dependency on external geocoding is clearly documented rather than a hidden gap.

Available Tools

4 tools

openchargemap_find_stationsopenchargemap-mcp-server: find stationsA

Read-only

Inspect

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

ParametersJSON Schema

Name	Required	Description	Default
`offset`	No	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`	No	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`	No	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`	No	Center latitude (WGS84 decimal degrees). Use with longitude + distance for a radius search. Resolve place names via openstreetmap_geocode first.
`longitude`	No	Center longitude (WGS84 decimal degrees). Use with latitude + distance for a radius search.
`maxresults`	No	Maximum stations to return, ordered by distance from the search point. Max 200.
`minpowerkw`	No	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`	No	Operator/network ID, or array of IDs (OR-matched). Resolve a network name with openchargemap_lookup_reference (category "operators") — e.g. "Tesla", "ChargePoint".
`boundingbox`	No	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`	No	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`	No	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`	No	Unit for the distance parameter and the returned distance values.	KM
`statustypeid`	No	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`	No	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`	No	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.

Output Schema

ParametersJSON Schema

Name	Required	Description
`cap`	No	The maxresults cap that was applied.
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Stations in the returned page.
`notice`	No	How to reach the stations this page left out, or why it came back empty.
`stations`	No	Matching stations, ordered by distance from the search point.
`truncated`	No	True when matching stations were left out of the returned page.
`nextOffset`	No	The offset to pass on an otherwise identical call to read the next page. Absent when nothing further was retrieved.
`totalCount`	No	Matching stations this search retrieved, before the offset/maxresults page was taken. Open Charge Map publishes no match total and one search can only retrieve so deep, so this is exact only when the search reached the end of what Open Charge Map holds for the area — otherwise it is a floor that rises as deeper pages are read. The notice says which of the two applies.
`attribution`	No	Required attribution to Open Charge Map contributors under CC BY 4.0.
`searchSummary`	No	Human-readable echo of the resolved search: location mode, scope, and active filters as the server applied them.

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint and openWorldHint, and the description richly substantiates both: it warns that 'registry status is operator-reported and can be stale' and that 'Open Charge Map is edited continuously, so a station added or removed between pages can shift what a later offset lands on.' It also discloses pagination truncation, mutual-exclusion rejection, and global-by-default behavior beyond what annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but every sentence earns its place: scope, search modes, geocoding caveat, filter categories, ID resolution, result contents, and pagination. It is front-loaded with the primary purpose and avoids filler or repetition of schema field names.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex 15-parameter tool with an output schema, the description is complete: it covers coordinate prerequisites, filter workflows, result fields, stale-status caveats, and pagination. Since an output schema exists, return-value details do not need to be spelled out, and the description still summarizes them.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so per-parameter details are already documented (baseline 3). The description adds meaningful cross-parameter guidance: the two mutually exclusive search modes (center+radius vs boundingbox), the integer-ID resolution workflow via openchargemap_lookup_reference, and a coarse 'fast charging only' hint via levelid 3. It stops short of explaining every parameter, but supplements the schema usefully.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a precise verb+resource+scope: 'Find EV charging stations from the global Open Charge Map registry near a point or within a bounding box.' It also distinguishes itself from siblings by emphasizing coordinate-native search and explicitly stating it 'does not geocode place names', which separates it from lookup/station-detail tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit routing: geocode places with openstreetmap_geocode first, resolve filter IDs with openchargemap_lookup_reference (including the 'CCS' -> 33 example), and use pagination with nextOffset when a page is truncated. It also states when not to use it in a certain way (don't pass place names; don't mix boundingbox with latitude/longitude as it is rejected).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

openchargemap_get_stationopenchargemap-mcp-server: get stationA

Read-onlyIdempotent

Inspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	Numeric OCM station ID (e.g. 145452).
`includeComments`	No	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.

Output Schema

ParametersJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`station`	No	The full station record.
`attribution`	No	Required CC BY 4.0 attribution to Open Charge Map contributors.
`reliabilityNote`	No	A caveat when the registry status, verification age, coordinates, or comments suggest the listing may not reflect reality. Omitted when there is nothing to flag.

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnly/idempotent/openWorld annotations, the description discloses key behavioral traits: includeComments returns every unpaged comment at once, potentially producing a large payload, and the comments are described as a reliability signal alongside registry status. No contradictions with annotations are present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences with no filler. The core purpose is front-loaded, followed by the return contents and the single behavioral caveat. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a full output schema, complete input schema, annotations for safety/idempotency, and a description covering the large-response caveat and sibling alternative, the agent has everything needed to decide when and how to call this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds real value by explaining the trade-off of includeComments (inline reliability signal vs. large unpaged response) and explicitly recommending the sibling for paged access, going beyond the schema's default/boolean description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb and resource: 'Get the full record for one Open Charge Map station by its numeric OCM ID.' It clearly distinguishes this from discovering stations (find_stations) and from paged comment retrieval (get_station_comments).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description tells the agent to prefer openchargemap_get_station_comments when community comments should be returned one page at a time, an explicit alternative. It could more explicitly contrast with openchargemap_find_stations for cases where the ID is unknown, but the ID-based phrasing implies the boundary.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

openchargemap_get_station_commentsopenchargemap-mcp-server: get station commentsA

Read-onlyIdempotent

Inspect

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.

ParametersJSON Schema

Name	Required	Description
`id`	Yes	Numeric OCM station ID.
`offset`	No	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`	No	Maximum comments to return, newest first. Max 100.

Output Schema

ParametersJSON Schema

Name	Required	Description
`cap`	No	The maxresults cap that was applied.
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Comments in the returned page.
`notice`	No	How to reach the comments this page left out, or why the station has none on record.
`comments`	No	The requested page of community comments, newest first — offset/maxresults applied. Empty with totalComments 0 means OCM has no check-ins for this station (absence of reports is not evidence the charger works); empty with a non-zero totalComments means the offset is past the last comment.
`stationId`	No	OCM station ID the comments belong to.
`truncated`	No	True when comments were left out of the returned page.
`nextOffset`	No	The offset to pass on an otherwise identical call to read the next page. Absent on the last page.
`totalCount`	No	Comments this station has on record, before the offset/maxresults page was taken — the complete count, not the page size.
`attribution`	No	Required CC BY 4.0 attribution to Open Charge Map contributors.
`stationTitle`	No	Station name, for context.
`isOperational`	No	Whether the registry marks the station operational. Absent when the operational state is unknown. Compare against the comments below — they are the real-world check.
`totalComments`	No	Comments this station has on record — the whole set, before offset/maxresults selected the page in comments. reliabilityNote counts its fault ratio over this population, not over the page.
`registryStatus`	No	Current registry operational status (operator-reported).
`reliabilityNote`	No	A caveat when the registry status, verification age, coordinates, or comments suggest the listing may not reflect reality. Omitted when there is nothing to flag.
`dateLastVerified`	No	ISO 8601 date the listing was last verified. null when never verified.
`registryStatusId`	No	Registry status ID — the value the openchargemap_find_stations statustypeid filter takes. Absent when OCM has no status on record.

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and idempotentHint=true, so the base safety profile is known. The description adds meaningful nuance: it discloses what the tool returns (comments, fault reports, ratings, outcome labels, registry status, last-verified date), the pagination/truncation behavior, and the mismatch-surfacing purpose. This is valuable beyond the annotations, so a score of 4 is warranted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences: the first front-loads purpose and value, the second details returns and pagination. Every clause carries useful information with no filler. It is longer than a terse definition but remains dense and well-ordered. The opening hook efficiently sets context before diving into mechanics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (pagination, multiple return elements, mismatch detection) and that an output schema exists, the description covers the essential call-time knowledge: what the tool returns, how to paginate, and what unique signal it provides. It doesn't restate schema details, which is appropriate. Minor gap: it doesn't explicitly say what 'truncated' looks like, but the schema and output schema likely cover that. Overall it is complete enough for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so each parameter (id, offset, maxresults) is already documented. The description adds context: it explains the offset as "the nextOffset value the previous one reported" and emphasizes ordering (newest-first) and the 100-result cap. This goes slightly beyond the schema's bare descriptions, raising it from baseline 3 to 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb-resource pair: "Read community check-ins and comments for one Open Charge Map station." It immediately distances itself from the siblings by framing this as "the real-world reliability signal beyond the operator-reported registry status," which distinguishes it from openchargemap_get_station (registry status) and the other siblings. The tool's identity is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use it: "beyond the operator-reported registry status" suggests choosing this over get_station when seeking user-driven reliability data. It also includes a concrete pagination workflow ("when a page reports truncated, repeat the call with the reported nextOffset"), which is direct usage guidance. It does not explicitly state alternatives or 'when not to use,' but the context is clear enough for an agent to reason about selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

openchargemap_lookup_referenceopenchargemap-mcp-server: lookup referenceA

Read-onlyIdempotent

Inspect

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.

ParametersJSON Schema

Name	Required	Description
`limit`	No	Maximum entries to return when browsing or when a query matches several. Max 100.
`query`	No	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`	No	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`	Yes	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.

Output Schema

ParametersJSON Schema

Name	Required	Description
`cap`	No	The limit that was applied.
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Entries in the returned page.
`notice`	No	How to reach the entries this page left out.
`source`	No	Where these entries came from. "live" — a startup refresh from Open Charge Map returned a complete set and is what is being served. "bundled" — the snapshot shipped with the server is being served, either because the refresh is switched off or because it failed and the server fell back to the bundle.
`matches`	No	Matching reference entries, best/exact match first.
`category`	No	The reference category queried.
`truncated`	No	True when matching entries were left out of the returned page.
`nextOffset`	No	The offset to pass on an otherwise identical call to read the next page. Absent on the last page.
`totalCount`	No	Entries matching before the offset/limit page was taken — the whole category when browsing, every match when a query was given.
`attribution`	No	Required CC BY 4.0 attribution to Open Charge Map contributors.
`filterParam`	No	The find_stations input parameter these IDs feed (e.g. "connectiontypeid"). Omitted for categories with no direct filter (currenttypes; countries use countrycode).
`snapshotDate`	No	Date the reference data in this response was captured, so callers know its vintage — the day the live refresh ran when source is "live", the bundled snapshot's own capture date when source is "bundled". Read it together with source: the same date can mean either a fresh fetch or a freshly cut bundle.

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint and idempotentHint, so safety is covered. The description adds meaningful behavioral context beyond annotations: pagination behavior for large categories, truncation reporting, repeat-with-nextOffset semantics, and the ability to browse by omitting the query. This is valuable operational detail not present in the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded with the core purpose, then gives useful examples and paging instructions. Every sentence earns its place; there is no filler or repetition of schema details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description, combined with a fully described input schema, detailed annotations, and an output schema, covers all the operational knowledge needed: what to pass, how browsing works, how paging works, and how the results relate to the sibling find_stations tool. Nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantic value: it gives concrete examples tying categories to ID fields, clarifies that query is case-insensitive and matches aliases, and explains how offset interacts with truncated pages. This goes beyond the schema's structural descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it resolves Open Charge Map reference data into the integer IDs required by openchargemap_find_stations filters. Concrete examples like 'CCS' -> connectiontypeid and 'France' -> country make the purpose unmistakable and clearly distinguish it from the station-related sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly ties the tool to a prerequisite step for openchargemap_find_stations and explains how to browse or resolve values. It does not explicitly state when not to use this tool versus siblings, but the examples and explicit mention of find_stations provide strong contextual guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

4 tool updatesSep 20, 2026
- Changedopenchargemap_find_stations10 fields changed
  - removedOutput schema / properties / stations / items / properties / connections / items / properties / amps / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
  - addedOutput schema / properties / stations / items / properties / connections / items / properties / amps / type
```
Added value: +[
+  "number",
+  "null"
+]
```
  - removedOutput schema / properties / stations / items / properties / connections / items / properties / powerKW / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
  - addedOutput schema / properties / stations / items / properties / connections / items / properties / powerKW / type
```
Added value: +[
+  "number",
+  "null"
+]
```
  - removedOutput schema / properties / stations / items / properties / connections / items / properties / quantity / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
  - addedOutput schema / properties / stations / items / properties / connections / items / properties / quantity / type
```
Added value: +[
+  "number",
+  "null"
+]
```
  - removedOutput schema / properties / stations / items / properties / connections / items / properties / voltage / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
  - addedOutput schema / properties / stations / items / properties / connections / items / properties / voltage / type
```
Added value: +[
+  "number",
+  "null"
+]
```
  - removedOutput schema / properties / stations / items / properties / dateLastVerified / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
  - addedOutput schema / properties / stations / items / properties / dateLastVerified / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- Changedopenchargemap_get_station14 fields changed
  - removedOutput schema / properties / station / properties / comments / items / properties / rating / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
  - addedOutput schema / properties / station / properties / comments / items / properties / rating / type
```
Added value: +[
+  "number",
+  "null"
+]
```
  - removedOutput schema / properties / station / properties / connections / items / properties / amps / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
  - addedOutput schema / properties / station / properties / connections / items / properties / amps / type
```
Added value: +[
+  "number",
+  "null"
+]
```
  - removedOutput schema / properties / station / properties / connections / items / properties / powerKW / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
  - addedOutput schema / properties / station / properties / connections / items / properties / powerKW / type
```
Added value: +[
+  "number",
+  "null"
+]
```
  - removedOutput schema / properties / station / properties / connections / items / properties / quantity / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
  - addedOutput schema / properties / station / properties / connections / items / properties / quantity / type
```
Added value: +[
+  "number",
+  "null"
+]
```
  - removedOutput schema / properties / station / properties / connections / items / properties / voltage / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
  - addedOutput schema / properties / station / properties / connections / items / properties / voltage / type
```
Added value: +[
+  "number",
+  "null"
+]
```
  - removedOutput schema / properties / station / properties / dateLastStatusUpdate / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
  - addedOutput schema / properties / station / properties / dateLastStatusUpdate / type
```
Added value: +[
+  "string",
+  "null"
+]
```
  - removedOutput schema / properties / station / properties / dateLastVerified / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
  - addedOutput schema / properties / station / properties / dateLastVerified / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- Changedopenchargemap_get_station_comments4 fields changed
  - removedOutput schema / properties / comments / items / properties / rating / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
  - addedOutput schema / properties / comments / items / properties / rating / type
```
Added value: +[
+  "number",
+  "null"
+]
```
  - removedOutput schema / properties / dateLastVerified / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
  - addedOutput schema / properties / dateLastVerified / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- Changedopenchargemap_lookup_reference2 fields changed
  - removedOutput schema / properties / matches / items / properties / formalName / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
  - addedOutput schema / properties / matches / items / properties / formalName / type
```
Added value: +[
+  "string",
+  "null"
+]
```

4 tool updatesAug 25, 2026

Changedopenchargemap_find_stations6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "stations",
+      "searchSummary",
+      "attribution",
+      "totalCount"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `invalid_location`: No search area was provided; or only one half of a center arrived; or a boundingbox arrived alongside a latitude or a longitude. `no_stations`: Open Charge Map holds no station for the search area and filters — either it returned nothing at all, or every station it returned was ruled out and there were no further candidates. `upstream_unavailable`: OCM returned a non-2xx response or timed out. `auth_failed`: OCM returned HTTP 401 or 403 — the API key is missing or invalid. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "invalid_location",
+            "no_stations",
+            "upstream_unavailable",
+            "auth_failed"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "stations",
-  "searchSummary",
-  "attribution",
-  "totalCount"
-]

Changedopenchargemap_get_station6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "station",
+      "attribution"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `not_found`: OCM returned an empty result for the given numeric ID (HTTP 200 with []) — no such station. `upstream_unavailable`: OCM returned a non-2xx response or timed out. `auth_failed`: OCM returned HTTP 401 or 403 — the API key is missing or invalid. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "not_found",
+            "upstream_unavailable",
+            "auth_failed"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "station",
-  "attribution"
-]

Changedopenchargemap_get_station_comments6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "stationId",
+      "stationTitle",
+      "comments",
+      "totalComments",
+      "attribution",
+      "totalCount"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `not_found`: OCM returned an empty result for the given numeric ID (HTTP 200 with []) — no such station. `upstream_unavailable`: OCM returned a non-2xx response or timed out. `auth_failed`: OCM returned HTTP 401 or 403 — the API key is missing or invalid. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "not_found",
+            "upstream_unavailable",
+            "auth_failed"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "stationId",
-  "stationTitle",
-  "comments",
-  "totalComments",
-  "attribution",
-  "totalCount"
-]

Changedopenchargemap_lookup_reference6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "category",
+      "matches",
+      "snapshotDate",
+      "source",
+      "attribution",
+      "totalCount"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `no_match`: No reference entry in the category matched the query. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "no_match"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "category",
-  "matches",
-  "snapshotDate",
-  "source",
-  "attribution",
-  "totalCount"
-]

4 tool updatesAug 6, 2026

Changedopenchargemap_find_stations7 fields changed

changedInput schema / properties / boundingbox / description

Previous value: -"Bounding-box search as an alternative to a center+radius. Mutually exclusive with latitude/longitude/distance."New value: +"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."

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "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.",
+  "maximum": 499,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / nextOffset

Added value: +{
+  "description": "The offset to pass on an otherwise identical call to read the next page. Absent when nothing further was retrieved.",
+  "type": "number"
+}

addedOutput schema / properties / notice

Added value: +{
+  "description": "How to reach the stations this page left out, or why it came back empty.",
+  "type": "string"
+}

changedOutput schema / properties / shown / description

Previous value: -"Number of stations returned when the cap was hit."New value: +"Stations in the returned page."

changedOutput schema / properties / totalCount / description

Previous value: -"Number of stations returned."New value: +"Matching stations this search retrieved, before the offset/maxresults page was taken. Open Charge Map publishes no match total and one search can only retrieve so deep, so this is exact only when the search reached the end of what Open Charge Map holds for the area — otherwise it is a floor that rises as deeper pages are read. The notice says which of the two applies."

changedOutput schema / properties / truncated / description

Previous value: -"True when results were capped at maxresults."New value: +"True when matching stations were left out of the returned page."

Changedopenchargemap_get_station1 field changed

changedInput schema / properties / includeComments / description

Previous value: -"Include community check-ins and comments inline in the response. Adds payload but gives the real-world reliability signal alongside the registry status. For comments alone, use openchargemap_get_station_comments."New value: +"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."

Changedopenchargemap_get_station_comments9 fields changed

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "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.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

changedOutput schema / properties / comments / description

Previous value: -"Community comments, newest first. Empty array means OCM has no check-ins for this station — absence of reports is not evidence the charger works."New value: +"The requested page of community comments, newest first — offset/maxresults applied. Empty with totalComments 0 means OCM has no check-ins for this station (absence of reports is not evidence the charger works); empty with a non-zero totalComments means the offset is past the last comment."

addedOutput schema / properties / nextOffset

Added value: +{
+  "description": "The offset to pass on an otherwise identical call to read the next page. Absent on the last page.",
+  "type": "number"
+}

changedOutput schema / properties / notice / description

Previous value: -"Guidance when the station has no check-ins on record."New value: +"How to reach the comments this page left out, or why the station has none on record."

changedOutput schema / properties / shown / description

Previous value: -"Number of comments returned when the cap was hit."New value: +"Comments in the returned page."

addedOutput schema / properties / totalComments

Added value: +{
+  "description": "Comments this station has on record — the whole set, before offset/maxresults selected the page in comments. reliabilityNote counts its fault ratio over this population, not over the page.",
+  "type": "number"
+}

changedOutput schema / properties / totalCount / description

Previous value: -"Number of comments returned."New value: +"Comments this station has on record, before the offset/maxresults page was taken — the complete count, not the page size."

changedOutput schema / properties / truncated / description

Previous value: -"True when comments were capped at maxresults."New value: +"True when comments were left out of the returned page."

changedOutput schema / required

Previous value: -[
-  "stationId",
-  "stationTitle",
-  "comments",
-  "attribution",
-  "totalCount"
-]New value: +[
+  "stationId",
+  "stationTitle",
+  "comments",
+  "totalComments",
+  "attribution",
+  "totalCount"
+]

Changedopenchargemap_lookup_reference9 fields changed

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "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.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / nextOffset

Added value: +{
+  "description": "The offset to pass on an otherwise identical call to read the next page. Absent on the last page.",
+  "type": "number"
+}

changedOutput schema / properties / notice / description

Previous value: -"How to reach the entries beyond the cap when a browse was capped."New value: +"How to reach the entries this page left out."

changedOutput schema / properties / shown / description

Previous value: -"Number of entries returned when the cap was hit."New value: +"Entries in the returned page."

changedOutput schema / properties / snapshotDate / description

Previous value: -"Date the bundled reference snapshot was captured, so callers know the data vintage."New value: +"Date the reference data in this response was captured, so callers know its vintage — the day the live refresh ran when source is \"live\", the bundled snapshot's own capture date when source is \"bundled\". Read it together with source: the same date can mean either a fresh fetch or a freshly cut bundle."

addedOutput schema / properties / source

Added value: +{
+  "description": "Where these entries came from. \"live\" — a startup refresh from Open Charge Map returned a complete set and is what is being served. \"bundled\" — the snapshot shipped with the server is being served, either because the refresh is switched off or because it failed and the server fell back to the bundle.",
+  "enum": [
+    "live",
+    "bundled"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / totalCount / description

Previous value: -"Number of entries returned."New value: +"Entries matching before the offset/limit page was taken — the whole category when browsing, every match when a query was given."

changedOutput schema / properties / truncated / description

Previous value: -"True when a browse was capped at limit."New value: +"True when matching entries were left out of the returned page."

changedOutput schema / required

Previous value: -[
-  "category",
-  "matches",
-  "snapshotDate",
-  "attribution",
-  "totalCount"
-]New value: +[
+  "category",
+  "matches",
+  "snapshotDate",
+  "source",
+  "attribution",
+  "totalCount"
+]

4 tool updatesAug 6, 2026

Changedopenchargemap_find_stations6 fields changed

changedInput schema / properties / connectiontypeid / anyOf

Previous value: -[
-  {
-    "description": "A single reference ID.",
-    "exclusiveMinimum": 0,
-    "maximum": 9007199254740991,
-    "type": "integer"
-  },
-  {
-    "description": "Several reference IDs, OR-matched.",
-    "items": {
-      "description": "A reference ID.",
-      "exclusiveMinimum": 0,
-      "maximum": 9007199254740991,
-      "type": "integer"
-    },
-    "maxItems": 10,
-    "type": "array"
-  }
-]New value: +[
+  {
+    "description": "A single reference ID.",
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "description": "Several reference IDs, OR-matched. At least one.",
+    "items": {
+      "description": "A reference ID.",
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991,
+      "type": "integer"
+    },
+    "maxItems": 10,
+    "minItems": 1,
+    "type": "array"
+  }
+]

changedInput schema / properties / levelid / anyOf

Previous value: -[
-  {
-    "description": "A single reference ID.",
-    "exclusiveMinimum": 0,
-    "maximum": 9007199254740991,
-    "type": "integer"
-  },
-  {
-    "description": "Several reference IDs, OR-matched.",
-    "items": {
-      "description": "A reference ID.",
-      "exclusiveMinimum": 0,
-      "maximum": 9007199254740991,
-      "type": "integer"
-    },
-    "maxItems": 3,
-    "type": "array"
-  }
-]New value: +[
+  {
+    "description": "A single reference ID.",
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "description": "Several reference IDs, OR-matched. At least one.",
+    "items": {
+      "description": "A reference ID.",
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991,
+      "type": "integer"
+    },
+    "maxItems": 3,
+    "minItems": 1,
+    "type": "array"
+  }
+]

changedInput schema / properties / operatorid / anyOf

Previous value: -[
-  {
-    "description": "A single reference ID.",
-    "exclusiveMinimum": 0,
-    "maximum": 9007199254740991,
-    "type": "integer"
-  },
-  {
-    "description": "Several reference IDs, OR-matched.",
-    "items": {
-      "description": "A reference ID.",
-      "exclusiveMinimum": 0,
-      "maximum": 9007199254740991,
-      "type": "integer"
-    },
-    "maxItems": 10,
-    "type": "array"
-  }
-]New value: +[
+  {
+    "description": "A single reference ID.",
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "description": "Several reference IDs, OR-matched. At least one.",
+    "items": {
+      "description": "A reference ID.",
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991,
+      "type": "integer"
+    },
+    "maxItems": 10,
+    "minItems": 1,
+    "type": "array"
+  }
+]

changedInput schema / properties / statustypeid / anyOf

Previous value: -[
-  {
-    "description": "A single reference ID.",
-    "exclusiveMinimum": 0,
-    "maximum": 9007199254740991,
-    "type": "integer"
-  },
-  {
-    "description": "Several reference IDs, OR-matched.",
-    "items": {
-      "description": "A reference ID.",
-      "exclusiveMinimum": 0,
-      "maximum": 9007199254740991,
-      "type": "integer"
-    },
-    "maxItems": 10,
-    "type": "array"
-  }
-]New value: +[
+  {
+    "description": "A single reference ID.",
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "description": "Several reference IDs, OR-matched. At least one.",
+    "items": {
+      "description": "A reference ID.",
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991,
+      "type": "integer"
+    },
+    "maxItems": 10,
+    "minItems": 1,
+    "type": "array"
+  }
+]

changedInput schema / properties / usagetypeid / anyOf

Previous value: -[
-  {
-    "description": "A single reference ID.",
-    "exclusiveMinimum": 0,
-    "maximum": 9007199254740991,
-    "type": "integer"
-  },
-  {
-    "description": "Several reference IDs, OR-matched.",
-    "items": {
-      "description": "A reference ID.",
-      "exclusiveMinimum": 0,
-      "maximum": 9007199254740991,
-      "type": "integer"
-    },
-    "maxItems": 10,
-    "type": "array"
-  }
-]New value: +[
+  {
+    "description": "A single reference ID.",
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "description": "Several reference IDs, OR-matched. At least one.",
+    "items": {
+      "description": "A reference ID.",
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991,
+      "type": "integer"
+    },
+    "maxItems": 10,
+    "minItems": 1,
+    "type": "array"
+  }
+]

addedOutput schema / properties / stations / items / properties / statusTypeId

Added value: +{
+  "description": "Registry status ID — the value the openchargemap_find_stations statustypeid filter takes. Absent when OCM has no status on record.",
+  "type": "number"
+}

Changedopenchargemap_get_station5 fields changed

addedOutput schema / properties / station / properties / comments / items / properties / checkinStatus

Added value: +{
+  "description": "The visit outcome the driver recorded (e.g. \"Charged Successfully\", \"Failed to Charge (Equipment Not Operational)\"). Carries the result on check-ins that have no comment text. Absent when the visitor recorded no outcome.",
+  "type": "string"
+}

addedOutput schema / properties / station / properties / comments / items / properties / checkinStatusId

Added value: +{
+  "description": "Numeric ID of the check-in outcome, stable across renames of its title.",
+  "type": "number"
+}

addedOutput schema / properties / station / properties / comments / items / properties / checkinStatusIsPositive

Added value: +{
+  "description": "Whether the registry classes this outcome as a good visit. Absent when the outcome carries no verdict either way (e.g. \"Did Not Visit Location\") or when none was recorded.",
+  "type": "boolean"
+}

addedOutput schema / properties / station / properties / comments / items / properties / relatedUrl

Added value: +{
+  "description": "Link the commenter attached. Absent when none was given.",
+  "type": "string"
+}

addedOutput schema / properties / station / properties / statusTypeId

Added value: +{
+  "description": "Registry status ID — the value the openchargemap_find_stations statustypeid filter takes. Absent when OCM has no status on record.",
+  "type": "number"
+}

Changedopenchargemap_get_station_comments5 fields changed

addedOutput schema / properties / comments / items / properties / checkinStatus

Added value: +{
+  "description": "The visit outcome the driver recorded (e.g. \"Charged Successfully\", \"Failed to Charge (Equipment Not Operational)\"). Carries the result on check-ins that have no comment text. Absent when the visitor recorded no outcome.",
+  "type": "string"
+}

addedOutput schema / properties / comments / items / properties / checkinStatusId

Added value: +{
+  "description": "Numeric ID of the check-in outcome, stable across renames of its title.",
+  "type": "number"
+}

addedOutput schema / properties / comments / items / properties / checkinStatusIsPositive

Added value: +{
+  "description": "Whether the registry classes this outcome as a good visit. Absent when the outcome carries no verdict either way (e.g. \"Did Not Visit Location\") or when none was recorded.",
+  "type": "boolean"
+}

addedOutput schema / properties / comments / items / properties / relatedUrl

Added value: +{
+  "description": "Link the commenter attached. Absent when none was given.",
+  "type": "string"
+}

addedOutput schema / properties / registryStatusId

Added value: +{
+  "description": "Registry status ID — the value the openchargemap_find_stations statustypeid filter takes. Absent when OCM has no status on record.",
+  "type": "number"
+}

Changedopenchargemap_lookup_reference3 fields changed
- removedInput schema / properties / query / minLength
```
Removed value: -1
```
- addedInput schema / properties / query / pattern
```
Added value: +"\\S"
```
- changedOutput schema / properties / notice / description
```
Previous value: -"Guidance when a query matched nothing."New value: +"How to reach the entries beyond the cap when a browse was capped."
```

4 tool updatesJul 4, 2026

Changedopenchargemap_find_stations5 fields changed

changedInput schema / properties / maxresults / description

Previous value: -"Maximum stations to return, ordered by distance from the search point. Max 200. Larger values cost more payload and upstream load — prefer tightening filters over raising this."New value: +"Maximum stations to return, ordered by distance from the search point. Max 200."

changedOutput schema / properties / stations / items / properties / distanceUnit / description

Previous value: -"Unit of the distance value (normalized from the OCM integer enum: 1=KM, 2=Miles)."New value: +"Unit of the distance value."

changedOutput schema / properties / stations / items / properties / id / description

Previous value: -"OCM station ID. Pass to openchargemap_get_station or openchargemap_get_station_comments."New value: +"OCM station ID."

changedOutput schema / properties / stations / items / properties / isOperational / description

Previous value: -"Whether the registry marks the status operational. Absent (not null) when StatusType is \"Unknown\" (ID=0) — OCM omits the flag then. A true value can still mask a broken charger — corroborate with comments and dateLastVerified."New value: +"Whether the registry marks the status operational. Absent when the operational state is unknown. A true value can still mask a broken charger — corroborate with comments and dateLastVerified."

changedOutput schema / properties / stations / items / properties / isRecentlyVerified / description

Previous value: -"OCM flag: whether the listing was verified recently."New value: +"Whether the listing was verified recently."

Changedopenchargemap_get_station6 fields changed

changedInput schema / properties / id / description

Previous value: -"Numeric OCM station ID (e.g. 145452). Obtain one from openchargemap_find_stations. Note: UUID lookup is not supported by the OCM API."New value: +"Numeric OCM station ID (e.g. 145452)."

changedOutput schema / properties / reliabilityNote / description

Previous value: -"Server-computed caveat when registry status and recency suggest the listing may not reflect reality (plain prose from observable facts; no synthetic score). Omitted when status is fresh and uncontested."New value: +"A caveat when the registry status, verification age, coordinates, or comments suggest the listing may not reflect reality. Omitted when there is nothing to flag."

changedOutput schema / properties / station / properties / distanceUnit / description

Previous value: -"Unit of the distance value (normalized from the OCM integer enum: 1=KM, 2=Miles)."New value: +"Unit of the distance value."

changedOutput schema / properties / station / properties / id / description

Previous value: -"OCM station ID. Pass to openchargemap_get_station or openchargemap_get_station_comments."New value: +"OCM station ID."

changedOutput schema / properties / station / properties / isOperational / description

Previous value: -"Whether the registry marks the status operational. Absent (not null) when StatusType is \"Unknown\" (ID=0) — OCM omits the flag then. A true value can still mask a broken charger — corroborate with comments and dateLastVerified."New value: +"Whether the registry marks the status operational. Absent when the operational state is unknown. A true value can still mask a broken charger — corroborate with comments and dateLastVerified."

changedOutput schema / properties / station / properties / isRecentlyVerified / description

Previous value: -"OCM flag: whether the listing was verified recently."New value: +"Whether the listing was verified recently."

Changedopenchargemap_get_station_comments4 fields changed

changedInput schema / properties / id / description

Previous value: -"Numeric OCM station ID. Get one from openchargemap_find_stations. Note: UUID lookup is not supported by the OCM API."New value: +"Numeric OCM station ID."

changedInput schema / properties / maxresults / description

Previous value: -"Maximum comments to return (handler trims, newest first). The OCM API returns all embedded comments — this caps what the tool surfaces. Max 100."New value: +"Maximum comments to return, newest first. Max 100."

changedOutput schema / properties / isOperational / description

Previous value: -"Whether the registry marks the station operational. Absent (not null) when status is Unknown — OCM omits the flag then. Compare against the comments below — they are the real-world check."New value: +"Whether the registry marks the station operational. Absent when the operational state is unknown. Compare against the comments below — they are the real-world check."

changedOutput schema / properties / reliabilityNote / description

Previous value: -"Server-computed caveat when status and comments disagree or the listing is stale (plain prose from observable facts; no synthetic score). Omitted when nothing to flag."New value: +"A caveat when the registry status, verification age, coordinates, or comments suggest the listing may not reflect reality. Omitted when there is nothing to flag."

Changedopenchargemap_lookup_reference2 fields changed

changedOutput schema / properties / matches / description

Previous value: -"Matching reference entries, best/exact match first. Use the id in a find_stations filter."New value: +"Matching reference entries, best/exact match first."

changedOutput schema / properties / matches / items / properties / id / description

Previous value: -"The reference ID — pass to the matching openchargemap_find_stations filter (e.g. connectiontypeid)."New value: +"The reference ID for this entry."

4 tool updatesJun 16, 2026
- First observedopenchargemap_find_stations
- First observedopenchargemap_get_station
- First observedopenchargemap_get_station_comments
- First observedopenchargemap_lookup_reference

Related MCP Connectors

Openchargemap A
io.github.pipeworx-io
Open Charge Map MCP — global EV charging station database (openchargemap.io).
Location Services Travel & Transportation Energy
2
Chargt EV Charging
com.chargt
Find EV charging stations, live availability and prices across the Netherlands via NDW data.
Location Services Travel & Transportation Energy
1
askacharge.com — EV charging network A
com.askacharge
Operate a network of EV charge points over OCPP: status, sessions, tariffs, prices, remote commands
Energy
251
openaq-mcp-server A
io.github.cyanheads
Find air-quality stations and read pollutant observations from government monitors via OpenAQ v3.
Government Data Open Data
722

Related MCP Servers

mcp-openchargemap
Location Services Travel & Transportation Open Data
pipeworx-io
A
license
Not graded
quality
B
maintenance
Enables querying global EV charging station data from Open Charge Map through natural language, accessing real-time station information via the Pipeworx gateway.
Updated 3 days ago (2026-09-25 01:25 UTC)
4 npm
MIT
ocm-sdk-mcp
Travel & Transportation Location Services
andreibesleaga
A
license
Not graded
quality
A
maintenance
Enables AI assistants to interact with the Open Charge Map API, allowing exploration of endpoints, test requests, and using documentation to integrate the SDK.
Updated 3 months ago (2026-06-25 14:34 UTC)
Apache 2.0
ev-failure-safe-mcp
Travel & Transportation Energy Location Services
kinorossiuk
A
license
Not graded
quality
C
maintenance
Recommends EV charging stations with low failure risk by considering vehicle type, connector, remaining range, and real-time public data.
Updated 2 months ago (2026-07-31 09:53 UTC)
MIT
OCHP MCP Server
Energy Travel & Transportation
andreibesleaga
A
license
Not graded
quality
D
maintenance
Enables AI assistants to interact with EV charging infrastructure through OCHP (Open Clearing House Protocol) services.
Updated 3 months ago (2026-06-24 13:07 UTC)
Apache 2.0