# AESO MCP (pypi · aeso-mcp)

Typed Alberta electricity market data and analytics via official AESO APIs.

- Trust score: 33/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- pypi · `aeso-mcp`: 33/100 (this document), [markdown](https://verifymcp.io/servers/bchoi-qwe-aeso-mcp/aeso-mcp.md), [page](https://verifymcp.io/servers/bchoi-qwe-aeso-mcp/aeso-mcp)

## Channel facts

- Registry: `pypi`
- Package: `aeso-mcp`
- Version: `0.3.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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.

- **Supply Chain Security**: 85/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects cryptography 46.0.7, reached via gridstatus > cryptography. A fixed version is available.
  - Runs a script at install time (build_backend) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does.
  - 4 of 68 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 35/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 24 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### How do I install the AESO MCP server?

AESO MCP runs locally as a PyPI package, launched with uvx aeso-mcp. 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 bchoi-qwe-aeso-mcp -- uvx aeso-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "bchoi-qwe-aeso-mcp": {
      "command": "uvx",
      "args": [
        "aeso-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "bchoi-qwe-aeso-mcp": {
      "command": "uvx",
      "args": [
        "aeso-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add bchoi-qwe-aeso-mcp -- uvx aeso-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bchoi-qwe-aeso-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "aeso-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add bchoi-qwe-aeso-mcp --command uvx --arg aeso-mcp
```

### Hermes

```yaml
mcp_servers:
  bchoi-qwe-aeso-mcp:
    command: "uvx"
    args: ["aeso-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "bchoi-qwe-aeso-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "aeso-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add bchoi-qwe-aeso-mcp -t stdio -c uvx -a aeso-mcp
```

### Other

```json
{
  "mcpServers": {
    "bchoi-qwe-aeso-mcp": {
      "command": "uvx",
      "args": [
        "aeso-mcp"
      ]
    }
  }
}
```

## 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-08-27 (score 33, 0)

- [functional] Package version: 0.2.0 → 0.3.0

### 2026-08-26 (score 33, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-23 (score 33)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/bchoi-qwe-aeso-mcp/aeso-mcp#diagnostics

## Score history

- 2026-09-21: 33
- 2026-09-20: 33
- 2026-09-19: 33
- 2026-09-18: 33
- 2026-09-17: 33
- 2026-09-16: 33
- 2026-09-15: 33
- 2026-09-14: 33
- 2026-09-13: 33
- 2026-09-12: 33
- 2026-09-11: 33
- 2026-09-10: 33
- 2026-09-09: 33
- 2026-09-08: 33
- 2026-09-07: 33
- 2026-09-06: 33
- 2026-09-05: 33
- 2026-09-04: 33
- 2026-09-03: 33
- 2026-09-02: 33
- 2026-09-01: 33
- 2026-08-31: 33
- 2026-08-30: 33
- 2026-08-29: 33
- 2026-08-28: 33
- 2026-08-27: 33
- 2026-08-26: 33
- 2026-08-25: 33
- 2026-08-24: 33
- 2026-08-23: 33

## Common questions

### What is the AESO MCP server?

AESO MCP is listed in the public MCP registry as io.github.bchoi-qwe/aeso-mcp. Typed Alberta electricity market data and analytics via official AESO APIs. This page covers its PyPI package (aeso-mcp).

### Is the AESO MCP server safe to use?

AESO MCP scores 33 out of 100 on VerifyMCP. We recorded 15 known advisories against it as of 21 September 2026. 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.

### Is the AESO MCP server still maintained?

AESO MCP 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

- PyPI project: https://pypi.org/project/aeso-mcp/
- Socket report: https://socket.dev/pypi/package/aeso-mcp
- Repository: https://github.com/bchoi-qwe/aeso-mcp
- Changelog RSS feed: https://verifymcp.io/servers/bchoi-qwe-aeso-mcp/aeso-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/bchoi-qwe-aeso-mcp/aeso-mcp.json
- HTML version of this page: https://verifymcp.io/servers/bchoi-qwe-aeso-mcp/aeso-mcp