io.github.cyanheads/openchargemap-mcp-server
REMOTE · OPENCHARGEMAP.CASEYJHAND.COM · 2 COMPONENTS · SCANNED AUG 4
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 →
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 Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1453 tokens (~363/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 Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · openchargemap.caseyjhand.com
claude mcp add --transport http cyanheads-openchargemap-mcp-server 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": {
"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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 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
- 30 Jul 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
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 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
- 26 Jul 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Aug 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 | 7 Jul 2026 | 5 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 5aad900eb2055a0b0ea55912ec19680c |
| 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 |
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 |
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.
openchargemap_find_stations openchargemap-mcp-server: find stations ~820
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.
| Name | Type | Req | Description |
|---|---|---|---|
| boundingbox | object | — | Bounding-box search as an alternative to a center+radius. Mutually exclusive with latitude/longitude/distance. |
| 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. |
| 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 | yes | Required attribution to Open Charge Map contributors under CC BY 4.0. |
| cap | number | — | The maxresults cap that was applied. |
| searchSummary | string | yes | Human-readable echo of the resolved search: location mode, scope, and active filters as the server applied them. |
| shown | number | — | Number of stations returned when the cap was hit. |
| stations | array | yes | Matching stations, ordered by distance from the search point. |
| totalCount | number | yes | Number of stations returned. |
| truncated | boolean | — | True when results were capped at maxresults. |
No examples provided.
openchargemap_get_station openchargemap-mcp-server: get station ~163
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. For comments alone, use openchargemap_get_stat… |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | yes | Required CC BY 4.0 attribution to Open Charge Map contributors. |
| 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 | yes | The full station record. |
No examples provided.
openchargemap_get_station_comments openchargemap-mcp-server: get station comments ~112
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 and dates, 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."
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Numeric OCM station ID. |
| maxresults | integer | — | Maximum comments to return, newest first. Max 100. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | yes | Required CC BY 4.0 attribution to Open Charge Map contributors. |
| cap | number | — | The maxresults cap that was applied. |
| comments | array | yes | Community comments, newest first. Empty array means OCM has no check-ins for this station — absence of reports is not evidence the charger works. |
| dateLastVerified | — | — | ISO 8601 date the listing was last verified. null when never verified. |
| 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. |
| notice | string | — | Guidance when the station has no check-ins on record. |
| registryStatus | string | — | Current registry operational status (operator-reported). |
| 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 | — | Number of comments returned when the cap was hit. |
| stationId | number | yes | OCM station ID the comments belong to. |
| stationTitle | string | yes | Station name, for context. |
| totalCount | number | yes | Number of comments returned. |
| truncated | boolean | — | True when comments were capped at maxresults. |
No examples provided.
openchargemap_lookup_reference openchargemap-mcp-server: lookup reference ~254
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.
| 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. |
| 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 | yes | Required CC BY 4.0 attribution to Open Charge Map contributors. |
| cap | number | — | The limit that was applied. |
| category | string | yes | The reference category queried. |
| 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 | yes | Matching reference entries, best/exact match first. |
| notice | string | — | Guidance when a query matched nothing. |
| shown | number | — | Number of entries returned when the cap was hit. |
| snapshotDate | string | yes | Date the bundled reference snapshot was captured, so callers know the data vintage. |
| totalCount | number | yes | Number of entries returned. |
| truncated | boolean | — | True when a browse was capped at limit. |
No examples provided.