openchargemap-mcp-server
io.github.cyanheads/openchargemap-mcp-servercyanheadsstreamable-httpv0.2.1Scanned
Find EV charging stations, detail, and reliability check-ins via the global Open Charge Map.
4 tools: 4 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the openchargemap-mcp-server can do
The openchargemap-mcp-server is published by the GitHub account cyanheads. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
3 tools bring in text other people can write (openchargemap_find_stations, openchargemap_get_station and openchargemap_get_station_comments).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 19, 2026, version 0.2.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Only reads 4Show 4 read-only tools
openchargemap_find_stationsFind EV charging stations from the global Open Charge Map registry near a point, within a bounding box, or along a route.Reads text others writeNo findings
Why it is in this group
- The name "openchargemap_find_stations" says "find": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Find EV charging stations from the global Open Charge Map registry near a point, within a bounding box, or along a route. Provide one location: a center (latitude + longitude + distance), a boundingbox, or a route (its points in travel order, with distance as the corridor half-width); optionally scope to a country with countrycode. This tool is coordinate-native and does not geocode place names — resolve a place like "Ballard, Seattle" to coordinates with openstreetmap_search_places first, then pass them here. Filter by connector type, minimum power (kW), operator/network, usage type (public, membership required, pay at location, private; price is not a usage type), charge level, operational status, and minimum charge points. Filter IDs are integers — resolve a connector or network name to its IDs with openchargemap_lookup_reference and pass every returned ID (e.g. "CCS" -> [32, 33]; Open Charge Map distinguishes CCS Type 1 (32, common in North America) and Type 2 (33, common in Europe); 33 alone can miss Type 1 stations). Each result includes title, address, distance from the search point (along a route: routeDistance along it and offRouteDistance off it), connections (type, power, count), operator, access rules, usage type ID, usage cost when on record, registry operational status, the last-verified date, and the data provider with its ID; the text output lists the license terms of each provider once per page, after the stations. 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
openchargemap_get_stationGet the full record for one Open Charge Map station by its numeric OCM ID.Reads text others writeNo findings
Why it is in this group
- The name "openchargemap_get_station" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 site and operator contact details on record (site phone and web page, operator website, phone, and fault-report email; never returned for a private residence), the data provider with its license terms, media, the date the listing was created, and verification recency. Set includeComments to also return community check-ins inline.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
openchargemap_get_station_commentsRead community check-ins and comments for one Open Charge Map station — the real-world reliability signal beyond the operator-reported registry status.Reads text others writeNo findings
Why it is in this group
- The name "openchargemap_get_station_comments" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe name "openchargemap_get_station_comments" says "get" and "comment": it reads comments, which other people can write.
- untrusted-inputThe description's first sentence says "read" and "comment": it reads comments, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
openchargemap_lookup_referenceResolve Open Charge Map reference data to the integer IDs that openchargemap_find_stations filters require.No findings
Why it is in this group
- The name "openchargemap_lookup_reference" says "lookup": a word for reading.
Description, as the server wrote it 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. A connector name can resolve to several regional variants ("CCS" matches CCS Type 2 = 33 and CCS Type 1 = 32, the North American form) — pass every returned ID to find_stations as an array, not just the first. 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:33 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools4 changed.~4 changedView diff
- Changed:openchargemap_find_stationsOnly readsdescriptioninputSchema
- Changed:openchargemap_get_stationOnly readsdescription
- Changed:openchargemap_get_station_commentsOnly readsinputSchema
- Changed:openchargemap_lookup_referenceOnly readsinputSchema
Tools3 changed.~3 changedView diff
- Changed:openchargemap_find_stationsOnly readsdescriptioninputSchema
- Changed:openchargemap_get_station_commentsOnly readsinputSchema
- Changed:openchargemap_lookup_referenceOnly readsdescriptioninputSchema
Install
Pinned to version 0.2.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http openchargemap https://openchargemap.caseyjhand.com/mcpclaude mcp add --transport http openchargemap https://openchargemap.caseyjhand.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__openchargemap__openchargemap_find_stations",
"mcp__openchargemap__openchargemap_get_station",
"mcp__openchargemap__openchargemap_lookup_reference",
"mcp__openchargemap__openchargemap_get_station_comments"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as openchargemap. Review it before you use it.
Capability tags behind 3 rules
- mcp__openchargemap__openchargemap_find_stations untrusted-input
- mcp__openchargemap__openchargemap_get_station untrusted-input
- mcp__openchargemap__openchargemap_get_station_comments untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.cyanheads/openchargemap-mcp-server/verify?hash=200789fab9367451e141aff48933028a130f730cedb879ac563d44c978e76db8" | jq -e '.changed == false'Pinned hash 200789fab936, from Nov 19, 2026, 16:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.cyanheads/openchargemap-mcp-server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.cyanheads/openchargemap-mcp-server)Source: MCP Registry · repository. Synced Nov 19, 2026, 16:18 UTC.
openchargemap-mcp-server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the openchargemap-mcp-server safe?
- No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the openchargemap-mcp-server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the openchargemap-mcp-server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the openchargemap-mcp-server have?
- 4 tools: 4 read. openchargemap_find_stations, openchargemap_get_station, openchargemap_lookup_reference and openchargemap_get_station_comments.
Does the openchargemap-mcp-server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the openchargemap-mcp-server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the openchargemap-mcp-server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.