Is the Cyanheads Openchargemap MCP server down?

mcp-registry/io.github.cyanheads/openchargemap-mcp-server · v0.1.10

Also listed as glama/cyanheads/-cyanheads/openchargemap-mcp-server

healthy
Last checked 2026-10-19 09:48 UTC · handshake 99ms

As of 2026-10-19 09:48 UTC, the Cyanheads Openchargemap MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 18 outages in 90 days, with a median recovery of 3 minutes.

uptime (30d checks)
99.8%
checks observed
3,804
outages (90d)
18
tools
4

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

Install Cyanheads Openchargemap MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http cyanheads-openchargemap-mcp-server https://openchargemap.caseyjhand.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "cyanheads-openchargemap-mcp-server": {
      "type": "http",
      "url": "https://openchargemap.caseyjhand.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: A (97/100)

A (97/100): 0 error(s), 1 warning(s) across 4 tool(s); ~3,069 tokens of tool definitions.
Scores higher than 92% of 15,345 MCP servers Glimind has audited.
Its tool list costs an agent ~3,069 tokens per session — more than 55% of servers.
97 → 97 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints100
Token cost78
Client compatibility100
Protocol100
Reliability100
Stability96

What to fix (2)

1 tool definition(s) exceed ~1,200 tokens each (largest: openchargemap_find_stations, ~1,837).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~1,237 tokens every session. How to fix →

Tools: openchargemap_find_stations · saves ~1,237 tokens/session

In the last 30 days: 0 tool(s) removed and 1 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.cyanheads/openchargemap-mcp-server"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.cyanheads/openchargemap-mcp-server"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.cyanheads%2Fopenchargemap-mcp-server.svg)](https://glimind.com/server/mcp-registry%2Fio.github.cyanheads%2Fopenchargemap-mcp-server?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.cyanheads%2Fopenchargemap-mcp-server?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.cyanheads%2Fopenchargemap-mcp-server.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.cyanheads%2Fopenchargemap-mcp-server.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.cyanheads%2Fopenchargemap-mcp-server?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:edf3ecde94668482…, first seen 2026-10-17, included at leaf 6058 of 26,015. Version history · verify what your client received.

Tools (4)

Compare: most reliable search servers · most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Cyanheads Openchargemap MCP server down right now?

As of 2026-10-19 09:48 UTC, the Cyanheads Openchargemap MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 18 outages in 90 days, with a median recovery of 3 minutes.

How many tools does Cyanheads Openchargemap MCP server provide?

Cyanheads Openchargemap MCP server advertises 4 tools, including openchargemap_find_stations, openchargemap_get_station, openchargemap_get_station_comments, openchargemap_lookup_reference.

How do I install Cyanheads Openchargemap MCP server?

Point your MCP client at this streamable-http endpoint: https://openchargemap.caseyjhand.com/mcp

Is the Cyanheads Openchargemap MCP server safe to connect to an AI agent?

Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Cyanheads Openchargemap MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve