io.github.cyanheads/openchargemap-mcp-server
REMOTE · OPENCHARGEMAP.CASEYJHAND.COM · 2 COMPONENTS · SCANNED SEP 20
Find EV charging stations, detail, and reliability check-ins via the global Open Charge Map.
Available components
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1841 tokens (~460/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.cyanheads/openchargemap-mcp-server server?
io.github.cyanheads/openchargemap-mcp-server is a hosted endpoint at https://openchargemap.caseyjhand.com/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 · openchargemap.caseyjhand.com
claude mcp add --transport http cyanheads-openchargemap-mcp-server 'https://openchargemap.caseyjhand.com/mcp'
{
"mcpServers": {
"cyanheads-openchargemap-mcp-server": {
"url": "https://openchargemap.caseyjhand.com/mcp"
}
}
} {
"servers": {
"cyanheads-openchargemap-mcp-server": {
"type": "http",
"url": "https://openchargemap.caseyjhand.com/mcp"
}
}
} [mcp_servers.cyanheads-openchargemap-mcp-server] url = "https://openchargemap.caseyjhand.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cyanheads-openchargemap-mcp-server": {
"type": "remote",
"url": "https://openchargemap.caseyjhand.com/mcp",
"enabled": true
}
}
} openclaw mcp add cyanheads-openchargemap-mcp-server --url 'https://openchargemap.caseyjhand.com/mcp' --transport streamable-http
mcp_servers:
cyanheads-openchargemap-mcp-server:
url: "https://openchargemap.caseyjhand.com/mcp" {
"McpServers": {
"cyanheads-openchargemap-mcp-server": {
"Transport": "http",
"Url": "https://openchargemap.caseyjhand.com/mcp"
}
}
} assistant mcp add cyanheads-openchargemap-mcp-server -t streamable-http -u 'https://openchargemap.caseyjhand.com/mcp'
{
"mcpServers": {
"cyanheads-openchargemap-mcp-server": {
"type": "http",
"url": "https://openchargemap.caseyjhand.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 9 Sept 26 0
- Stability: 0.97 → pass security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 −1
- Stability: pass → 0.93 functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 0.1.7 → 0.1.8 functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 0
- Transport: fail → pass ▲ security
- HSTS header: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Stability: unverified → 0.50 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
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 20 Sept 2026 · Probed https://openchargemap.caseyjhand.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=caseyjhand.com | CN=WE1,O=Google Trust Services,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a6985204ed51ae050e7738aa6be668e9 |
| SANs: caseyjhand.com, *.caseyjhand.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of openchargemap.caseyjhand.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| caseyjhand.com. | present | 2371 | 13 | Verified |
| openchargemap.caseyjhand.com. | Verified address RRset verified with the apex keys |
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=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://openchargemap.caseyjhand.com/mcp | Verified | 200 | |
| http (plaintext) | http://openchargemap.caseyjhand.com/mcp | HTTPS enforced | 301 | https://openchargemap.caseyjhand.com/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 →
openchargemap_find_stations openchargemap-mcp-server: find stations ~973
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.
| Name | Type | Req | Description |
|---|---|---|---|
| boundingbox | object | – | 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… |
| connectiontypeid | – | – | 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. |
| countrycode | string | – | 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. |
| distance | number | – | 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. |
| distanceUnit | string | – | Unit for the distance parameter and the returned distance values. |
| latitude | number | – | Center latitude (WGS84 decimal degrees). Use with longitude + distance for a radius search. Resolve place names via openstreetmap_geocode first. |
| levelid | – | – | 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. |
| longitude | number | – | Center longitude (WGS84 decimal degrees). Use with latitude + distance for a radius search. |
| maxresults | integer | – | Maximum stations to return, ordered by distance from the search point. Max 200. |
| minchargepoints | integer | – | 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. |
| minpowerkw | number | – | 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. |
| offset | integer | – | 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 st… |
| operatorid | – | – | Operator/network ID, or array of IDs (OR-matched). Resolve a network name with openchargemap_lookup_reference (category "operators") — e.g. "Tesla", "ChargePoint". |
| statustypeid | – | – | 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… |
| usagetypeid | – | – | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | Required attribution to Open Charge Map contributors under CC BY 4.0. |
| cap | number | – | The maxresults cap that was applied. |
| error | object | – | Present when the call failed. Absent on success. |
| nextOffset | number | – | The offset to pass on an otherwise identical call to read the next page. Absent when nothing further was retrieved. |
| notice | string | – | How to reach the stations this page left out, or why it came back empty. |
| searchSummary | string | – | Human-readable echo of the resolved search: location mode, scope, and active filters as the server applied them. |
| shown | number | – | Stations in the returned page. |
| stations | array | – | Matching stations, ordered by distance from the search point. |
| totalCount | number | – | 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… |
| truncated | boolean | – | True when matching stations were left out of the returned page. |
No examples provided.
openchargemap_get_station openchargemap-mcp-server: get station ~195
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Numeric OCM station ID (e.g. 145452). |
| includeComments | boolean | – | 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, un… |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | Required CC BY 4.0 attribution to Open Charge Map contributors. |
| error | object | – | Present when the call failed. Absent on success. |
| reliabilityNote | string | – | 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. |
| station | object | – | The full station record. |
No examples provided.
openchargemap_get_station_comments openchargemap-mcp-server: get station comments ~225
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Numeric OCM station ID. |
| maxresults | integer | – | Maximum comments to return, newest first. Max 100. |
| offset | integer | – | 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 ch… |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | Required CC BY 4.0 attribution to Open Charge Map contributors. |
| cap | number | – | The maxresults cap that was applied. |
| comments | array | – | 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 char… |
| dateLastVerified | – | – | ISO 8601 date the listing was last verified. null when never verified. |
| error | object | – | Present when the call failed. Absent on success. |
| isOperational | boolean | – | 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. |
| nextOffset | number | – | The offset to pass on an otherwise identical call to read the next page. Absent on the last page. |
| notice | string | – | How to reach the comments this page left out, or why the station has none on record. |
| registryStatus | string | – | Current registry operational status (operator-reported). |
| registryStatusId | number | – | Registry status ID — the value the openchargemap_find_stations statustypeid filter takes. Absent when OCM has no status on record. |
| reliabilityNote | string | – | 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. |
| shown | number | – | Comments in the returned page. |
| stationId | number | – | OCM station ID the comments belong to. |
| stationTitle | string | – | Station name, for context. |
| totalComments | number | – | 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. |
| totalCount | number | – | Comments this station has on record, before the offset/maxresults page was taken — the complete count, not the page size. |
| truncated | boolean | – | True when comments were left out of the returned page. |
No examples provided.
openchargemap_lookup_reference openchargemap-mcp-server: lookup reference ~344
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Which reference set to query. connectiontypes -> connectiontypeid; operators -> operatorid; usagetypes -> usagetypeid; statustypes -> statustypeid; currenttypes -> current type; levels -> charge leve… |
| limit | integer | – | Maximum entries to return when browsing or when a query matches several. Max 100. |
| offset | integer | – | 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 m… |
| query | string | – | 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 catego… |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | Required CC BY 4.0 attribution to Open Charge Map contributors. |
| cap | number | – | The limit that was applied. |
| category | string | – | The reference category queried. |
| error | object | – | Present when the call failed. Absent on success. |
| filterParam | string | – | The find_stations input parameter these IDs feed (e.g. "connectiontypeid"). Omitted for categories with no direct filter (currenttypes; countries use countrycode). |
| matches | array | – | Matching reference entries, best/exact match first. |
| nextOffset | number | – | The offset to pass on an otherwise identical call to read the next page. Absent on the last page. |
| notice | string | – | How to reach the entries this page left out. |
| shown | number | – | Entries in the returned page. |
| snapshotDate | string | – | 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 "bundle… |
| source | string | – | 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, e… |
| totalCount | number | – | Entries matching before the offset/limit page was taken — the whole category when browsing, every match when a query was given. |
| truncated | boolean | – | True when matching entries were left out of the returned page. |
No examples provided.
What is the io.github.cyanheads/openchargemap-mcp-server server?
io.github.cyanheads/openchargemap-mcp-server is listed in the public MCP registry as io.github.cyanheads/openchargemap-mcp-server. Find EV charging stations, detail, and reliability check-ins via the global Open Charge Map. This page covers its hosted endpoint (https://openchargemap.caseyjhand.com/mcp).
Is the io.github.cyanheads/openchargemap-mcp-server server safe to use?
io.github.cyanheads/openchargemap-mcp-server scores 79 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 io.github.cyanheads/openchargemap-mcp-server server expose?
io.github.cyanheads/openchargemap-mcp-server exposes 4 tools: openchargemap_find_stations, openchargemap_get_station, openchargemap_lookup_reference, openchargemap_get_station_comments. Their descriptions and schemas cost roughly 1,737 tokens of context every time the server is loaded.
Does the io.github.cyanheads/openchargemap-mcp-server server require authentication?
No. We connected to io.github.cyanheads/openchargemap-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.cyanheads/openchargemap-mcp-server server still maintained?
io.github.cyanheads/openchargemap-mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.