AESO MCP
PYPI · AESO-MCP
Typed Alberta electricity market data and analytics via official AESO APIs.
Available components
Last scanned (3 hours ago)
Scores higher than 0% of PyPI servers
Category Finance and Payments
Recent critical change
GHSA-6q48-6c7w-9gw2 affects this package (21 Oct 2026). See the changelog before you install this server.
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. How we score → Why this is hard to score →
Supply Chain Security75
- No malware found by supply-chain analysis.Pass
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- Runs uv_build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 4 of 65 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 69 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox 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. How we score packages →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Oct 26 −37
- GHSA-6q48-6c7w-9gw2 affects this package: none ▼ critical
- Score status: scored → failed ▼ critical
- Known CVEs: CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. critical
- CVE-2026-69247 no longer affects this package ▲ security
- GHSA-537c-gmf6-5ccf no longer affects this package ▲ security
- CVE-2026-102938 no longer affects this package ▲ security
- CVE-2026-69248 no longer affects this package ▲ security
- CVE-2025-68146 no longer affects this package ▲ security
- CVE-2026-102937 no longer affects this package ▲ security
- CVE-2026-22701 no longer affects this package ▲ security
- CVE-2026-59890 no longer affects this package ▲ security
- CVE-2026-102930 no longer affects this package ▲ security
- CVE-2026-69249 no longer affects this package ▲ security
- CVE-2026-102925 no longer affects this package ▲ security
- CVE-2026-41066 no longer affects this package ▲ security
- 1 Oct 26 37
- CVE-2026-102925 affects this package: high ▼ security
- CVE-2026-102938 affects this package: high ▼ security
- CVE-2026-102937 affects this package: high ▼ security
- CVE-2026-102930 affects this package: high ▼ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- License: fail → pass ▲ functional
- Licence: MIT functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Aug 26 0
- Package version: 0.2.0 → 0.3.0 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/aeso-mcp@0.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | uv_build |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 55 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-6q48-6c7w-9gw2 | critical | yes | ||
| PYSEC-2026-4320 | none | yes | ||
| GHSA-537c-gmf6-5ccf | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-g6cj-pr64-35w5 | CVE-2026-69247 | high | yes | |
| GHSA-jwv3-5hgf-82ww | CVE-2026-69249 | high | yes | |
| GHSA-m2h6-j472-rp4c | CVE-2026-69248 | medium | yes | |
| PYSEC-2026-3552 | CVE-2026-69247 | none | yes | |
| PYSEC-2026-3553 | CVE-2026-69249 | none | yes | |
| PYSEC-2026-3554 | CVE-2026-69248 | none | yes | |
| GHSA-vqqp-x5qm-5qp4 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N | yes | |
| GHSA-69hj-f68j-2879 | CVE-2026-112909 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N | yes |
| GHSA-8mx5-7m5m-r77g | CVE-2026-112910 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L | yes |
| GHSA-qmgc-5h2g-mvrw | CVE-2026-22701 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H | yes |
| GHSA-w853-jp5j-5j7f | CVE-2025-68146 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H | yes |
| PYSEC-2026-1374 | CVE-2026-22701 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H | yes |
| PYSEC-2026-1375 | CVE-2025-68146 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H | yes |
| GHSA-567q-5qvw-pf92 | CVE-2026-112907 | low | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-6627-m3xw-93mp | CVE-2026-112908 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L | yes |
| GHSA-9c4x-gm8v-wgc4 | CVE-2026-112911 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H | yes |
| GHSA-9j6q-wvj5-jgjg | CVE-2026-112912 | low | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-9vhv-jxww-xfm5 | CVE-2026-112913 | low | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-cwqr-hh33-gh44 | CVE-2026-112915 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-fq56-3cx3-fjxp | CVE-2026-112935 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-j8f7-rjxc-mr56 | CVE-2026-112936 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L | yes |
| GHSA-m462-7rxw-wvpg | CVE-2026-112938 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H | yes |
| GHSA-rfpc-qcw5-3pc4 | CVE-2026-112939 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-v4x8-3wr5-3wq8 | CVE-2026-112940 | high | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H | yes |
| GHSA-vfmq-68hx-4jfw | CVE-2026-41066 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| PYSEC-2026-87 | CVE-2026-41066 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-h35f-9h28-mq5c | CVE-2026-59890 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N | yes |
| GHSA-xmj3-9gf7-h52w | low | yes | ||
| PYSEC-2026-3447 | CVE-2026-59890 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N | yes |
| GHSA-394h-qwmc-48pf | CVE-2026-113718 | high | yes | |
| GHSA-43mp-35q3-x3fq | CVE-2026-113724 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L | yes |
| GHSA-494p-63j8-28p3 | CVE-2026-113714 | low | yes | |
| GHSA-558c-9hv2-4prj | CVE-2026-113721 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L | yes |
| GHSA-5vjq-rrrf-7h2q | CVE-2026-113726 | high | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H | yes |
| GHSA-6w3r-xr62-4xcp | CVE-2026-113723 | high | yes | |
| GHSA-8rjx-v5ww-45pp | CVE-2026-113776 | high | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H | yes |
| GHSA-94p9-xgh2-xp45 | CVE-2026-102930 | high | yes | |
| GHSA-9h9j-4vrj-gf7g | CVE-2026-102938 | medium | yes | |
| GHSA-c947-3pg5-gm8q | CVE-2026-113732 | high | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H | yes |
| GHSA-c978-59m8-c77v | CVE-2026-113722 | high | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H | yes |
| GHSA-cw65-gx24-rc82 | CVE-2026-113716 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L | yes |
| GHSA-cx28-75q4-x26q | CVE-2026-113717 | low | yes | |
| GHSA-fc2g-4w5p-6whm | CVE-2026-113720 | medium | yes | |
| GHSA-hhxq-47xx-j5xx | CVE-2026-113719 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L | yes |
| GHSA-p58f-9548-mpm2 | CVE-2026-102925 | high | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H | yes |
| GHSA-qmx5-4p3x-wvqf | CVE-2026-113715 | low | yes | |
| GHSA-vxj4-q4g9-crj7 | CVE-2026-113725 | high | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H | yes |
Showing 50 of 55 vulnerabilities.
Background: What a vulnerability scan can and cannot prove →
Dependencies 65 packages
| Packages resolved | 65 |
|---|---|
| Stale | 4 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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.
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.
pypi · aeso-mcp
claude mcp add bchoi-qwe-aeso-mcp -- uvx aeso-mcp
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 still maintained?
AESO MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the AESO MCP server under?
AESO MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.