AESO MCP
PYPI · AESO-MCP · SCANNED SEP 20
Typed Alberta electricity market data and analytics via official AESO APIs.
Available components
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 Security85
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects cryptography 46.0.7, reached via gridstatus > cryptography. A fixed version is available. View diagnostics → Fail
- 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. View diagnostics → Partial
- 4 of 68 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 23 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) that our sandbox does not supply, 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) that our sandbox does not supply, 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) that our sandbox does not supply, 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) that our sandbox does not supply, 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) that our sandbox does not supply, so we never saw its MCP handshake.Unverified
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. How we score packages →
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
{
"mcpServers": {
"bchoi-qwe-aeso-mcp": {
"command": "uvx",
"args": [
"aeso-mcp"
]
}
}
} {
"servers": {
"bchoi-qwe-aeso-mcp": {
"command": "uvx",
"args": [
"aeso-mcp"
]
}
}
} codex mcp add bchoi-qwe-aeso-mcp -- uvx aeso-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bchoi-qwe-aeso-mcp": {
"type": "local",
"command": [
"uvx",
"aeso-mcp"
],
"enabled": true
}
}
} openclaw mcp add bchoi-qwe-aeso-mcp --command uvx --arg aeso-mcp
mcp_servers:
bchoi-qwe-aeso-mcp:
command: "uvx"
args: ["aeso-mcp"] {
"McpServers": {
"bchoi-qwe-aeso-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"aeso-mcp"
]
}
}
} assistant mcp add bchoi-qwe-aeso-mcp -t stdio -c uvx -a aeso-mcp
{
"mcpServers": {
"bchoi-qwe-aeso-mcp": {
"command": "uvx",
"args": [
"aeso-mcp"
]
}
}
} 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.
- 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 33
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 20 Sept 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 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | unreviewed | uv_build |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 15 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| 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-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-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 |
| 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 |
Background: What a vulnerability scan can and cannot prove →
Dependencies 68 packages
| Packages resolved | 68 |
|---|---|
| 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.
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 20 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.