# Tern EV-Charging Analytics (dev) (remote · tern-mcp-dev-537572042041.europe-west4.run.app)

EV-charging site analytics: utilization, demand, peak saturation and corridor benchmarks.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `tern-mcp-dev-537572042041.europe-west4.run.app`: 71/100 (this document), [markdown](https://verifymcp.io/servers/useternai-usetern-dev/tern-mcp-dev-537572042041.md), [page](https://verifymcp.io/servers/useternai-usetern-dev/tern-mcp-dev-537572042041)

## Channel facts

- Endpoint: `https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 50/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 3184 tokens (~122/item across 26 items; 26 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 81/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 34% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 26 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Tern EV-Charging Analytics (dev) MCP server?

Tern EV-Charging Analytics (dev) is a hosted endpoint at https://tern-mcp-dev-537572042041.europe-west4.run.app/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.

### Claude

```bash
claude mcp add --transport http useternai-usetern-dev 'https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "useternai-usetern-dev": {
      "url": "https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "useternai-usetern-dev": {
      "type": "http",
      "url": "https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.useternai-usetern-dev]
url = "https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "useternai-usetern-dev": {
      "type": "remote",
      "url": "https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add useternai-usetern-dev --url 'https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  useternai-usetern-dev:
    url: "https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "useternai-usetern-dev": {
      "Transport": "http",
      "Url": "https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add useternai-usetern-dev -t streamable-http -u 'https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "useternai-usetern-dev": {
      "type": "http",
      "url": "https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 71, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-20 (score 70, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-19 (score 70, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-18 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-17 (score 69)

First indexed and scored.

## MCP tools (26)

### `search_charging_stations` (~114 tokens)

Find charging stations in one country by structured filter — id, title, address, operator. The reply is the API payload inline: station ids, titles, addresses and operators, which is what the claim tools take as site_id and station_id.

Input parameters:

- `address`
- `country_iso3` (string, required): ISO-3166 alpha-3 scope, e.g. NOR.
- `id`: One 32-char hex station id.
- `limit`
- `operator`
- `title`

Output parameters:

- `result` (string)

### `nearby_charging_stations` (~117 tokens)

List the charging stations within a radius of a point, nearest first. The radius is in kilometres and at most 10; the reply is the API payload inline. This is how a site's competitors are found before any claim is read.

Input parameters:

- `country_iso3` (string, required): ISO-3166 alpha-3 scope, e.g. NOR.
- `lat` (number, required)
- `limit`
- `lng` (number, required)
- `radius_km` (number, required): km, > 0 and <= 10.

Output parameters:

- `result` (string)

### `list_evses` (~88 tokens)

List the individual EVSEs (connectors) of up to 20 stations, with their capacity in kW. Stall counts and capacity bands come from here rather than from a station record.

Input parameters:

- `country_iso3` (string, required): ISO-3166 alpha-3 scope, e.g. NOR.
- `station_ids` (required): 1-20 station ids (array or comma-separated).

Output parameters:

- `result` (string)

### `aggregate_charging_utilization` (~180 tokens)

Station-level utilization aggregated over a GeoJSON area and a date window of at most 92 days, optionally filtered to a capacity band (default 150 kW = HPC; pass 100 for fast charging). The reply is one row per station, so it reads an area without pulling any station's daily rows.

Input parameters:

- `country_iso3` (string, required): ISO-3166 alpha-3 scope, e.g. NOR.
- `date_from` (string, required): YYYY-MM-DD (required).
- `date_to` (string, required): YYYY-MM-DD (required; window <= 92 days, >= date_from).
- `geometry` (string, required): GeoJSON Polygon/MultiPolygon as a JSON string.
- `max_capacity_kw`
- `min_capacity_kw`: kW floor (default 150 = HPC; pass 100 for fast-charging).

Output parameters:

- `result` (string)

### `aggregate_evse_utilization` (~157 tokens)

EVSE-level utilization aggregated over a GeoJSON area and a date window of at most 92 days, optionally filtered to a capacity band. The per-connector counterpart of aggregate_charging_utilization.

Input parameters:

- `country_iso3` (string, required): ISO-3166 alpha-3 scope, e.g. NOR.
- `date_from` (string, required): YYYY-MM-DD (required).
- `date_to` (string, required): YYYY-MM-DD (required; window <= 92 days, >= date_from).
- `geometry` (string, required): GeoJSON Polygon/MultiPolygon as a JSON string.
- `max_capacity_kw`
- `min_capacity_kw`: kW floor (default 150 = HPC; pass 100 for fast-charging).

Output parameters:

- `result` (string)

### `area_benchmark` (~117 tokens)

How hard is each EVSE at this site working compared with the area around it?

Reads the area_benchmark claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `avg_session_minutes` (~111 tokens)

How long does a session at this site actually last?

Reads the avg_session_minutes claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `busy_evse_hours` (~134 tokens)

How many EVSE-hours at this station carried charging on the drilled day, and how many of its EVSEs were charging at once in the busiest hour?

Reads the busy_evse_hours claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `corridor_benchmark` (~117 tokens)

How does this site's demand per EVSE-day compare with the corridor drawn around it?

Reads the corridor_benchmark claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `corridor_comparison` (~130 tokens)

How does this site compare with the named stations around it — distance, EVSE count, max kW, and sessions per EVSE-day each?

Reads the corridor_comparison claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `daily_spike` (~114 tokens)

Which days ran far above this site's normal, and by how much?

Reads the daily_spike claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `day_vs_similar` (~116 tokens)

Was one particular day unusual for the day of week it fell on?

Reads the day_vs_similar claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `demand_share_multiple` (~121 tokens)

How much of the area's demand does this one site take, said as a multiple of the mean station?

Reads the demand_share_multiple claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `estate_coverage` (~127 tokens)

Which estate sites reported on every day of the window, which are partial or young, and how full is the window's final day?

Reads the estate_coverage claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `estate_monthly_series` (~124 tokens)

Did demand per EVSE across the estate move month over month, and did each focus site move with it?

Reads the estate_monthly_series claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `hourly_spike` (~111 tokens)

When in the day does demand at this site peak?

Reads the hourly_spike claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `monthly_sessions_per_stall_day` (~118 tokens)

Is demand per EVSE rising or falling month over month?

Reads the monthly_sessions_per_stall_day claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `peak_hour_co_saturation` (~130 tokens)

When the site reaches its busiest hour of the day, do the stations around it reach their own busiest hours at the same time?

Reads the peak_hour_co_saturation claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `poi_context` (~135 tokens)

What kind of place is this site sitting in?

Reads the poi_context claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

places carries the rows this claim reads, because they are transcribed by the caller rather than fetched.

Input parameters:

- `params` (required)
- `places` (array, required)

Output parameters:

- `result` (string)

### `rank_gap` (~123 tokens)

Where does this site sit in its estate's ranking, and how far is it from the estate median and the estate leader?

Reads the rank_gap claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `road_context` (~112 tokens)

What road does this site sit on, and what class is it?

Reads the road_context claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `sessions_per_stall_day` (~117 tokens)

How hard is each EVSE at this site working per day?

Reads the sessions_per_stall_day claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `site_profile` (~117 tokens)

What is this site — how many EVSEs, and how close is the nearest station?

Reads the site_profile claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `site_ranking` (~128 tokens)

How do the estate's sites rank on sessions per EVSE-day over one window, and how far is the leader above the estate median?

Reads the site_ranking claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `total_charging_minutes` (~116 tokens)

How many minutes of charging did this site actually deliver over the window?

Reads the total_charging_minutes claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `total_sessions` (~110 tokens)

How much charging demand did this site see over the window?

Reads the total_sessions claim for one site and returns only its result: the status the claim decided from its own observations (computed or insufficient), the typed result, and the display a deliverable would print. The observations behind it are pulled into a scratch directory that is deleted before the call returns, so the rows never enter the conversation and nothing is left on the server to read back later — this call is the whole reading.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/useternai-usetern-dev/tern-mcp-dev-537572042041#diagnostics

## Score history

- 2026-09-21: 71
- 2026-09-20: 70
- 2026-09-19: 70
- 2026-09-18: 69
- 2026-09-17: 69

## Common questions

### What is the Tern EV-Charging Analytics (dev) MCP server?

Tern EV-Charging Analytics (dev) is an MCP server listed in the public MCP registry as io.github.useternai/usetern-dev. EV-charging site analytics: utilization, demand, peak saturation and corridor benchmarks. This page covers its hosted endpoint (https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp).

### Is the Tern EV-Charging Analytics (dev) MCP server safe to use?

Tern EV-Charging Analytics (dev) scores 71 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 Tern EV-Charging Analytics (dev) MCP server expose?

Tern EV-Charging Analytics (dev) exposes 26 tools: search_charging_stations, nearby_charging_stations, list_evses, aggregate_charging_utilization, aggregate_evse_utilization, and 21 more. Their descriptions and schemas cost roughly 3,184 tokens of context every time the server is loaded.

### Does the Tern EV-Charging Analytics (dev) MCP server require authentication?

Yes. Tern EV-Charging Analytics (dev) asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Tern EV-Charging Analytics (dev) MCP server still maintained?

Tern EV-Charging Analytics (dev) is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp
- Authorisation metadata: https://tern-mcp-dev-537572042041.europe-west4.run.app/.well-known/oauth-protected-resource/mcp
- Website: https://usetern.ai/
- Changelog RSS feed: https://verifymcp.io/servers/useternai-usetern-dev/tern-mcp-dev-537572042041.xml
- Changelog JSON feed: https://verifymcp.io/servers/useternai-usetern-dev/tern-mcp-dev-537572042041.json
- HTML version of this page: https://verifymcp.io/servers/useternai-usetern-dev/tern-mcp-dev-537572042041