Tern EV-Charging Analytics (dev)

io.github.useternaiPublished by GitHub account useternaiv0.1.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Remote MCP endpoint for Tern EV-charging site analytics: utilization, demand, peak saturation and corridor benchmarks.

What you can do
  • Query EV-charging site analytics through a hosted Tern endpoint.
  • Review utilization and demand figures for charging sites.
  • Check peak saturation and corridor benchmarks.
  • Compare sites against corridor-level reference data.
When to use it
Useful when you need EV-charging market or site performance data — utilization, demand, peak saturation or corridor benchmarks — inside an assistant, for example when evaluating charging locations or comparing sites.
Requirements
A remote streamable HTTP endpoint hosted by Tern; no local package. An OAuth sign-in is required, plus a Tern API key (sk_...) sent in the X-API-Key header for every analytics tool; the handshake itself works without the key.
Before you install
The server asks for a Tern API key in the X-API-Key header; treat it as a secret and check how it is stored and transmitted. Analytics queries are sent to Tern's hosted service, so site and corridor data leaves your machine. The manifest lists no tools, so confirm the exact operations before relying on it.

Installation

In SourceWeft

  1. Open Tern EV-Charging Analytics (dev) in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.useternai%2Fusetern-dev/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "tern-ev-charging-analytics-dev": {
      "type": "http",
      "url": "https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 17, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.