MCP.Market

AESO MCP server

by bchoi-qwe·io.github.bchoi-qwe/aeso-mcp·v0.3.0

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

B78/100grade B
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
New

0 stars35 downloads/wk

Reviews

Write one

Nobody has reviewed AESO MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

AESO MCP tools (57, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • analyze_asset_dispatch
  • analyze_forecast_error
  • analyze_generation_mix
  • analyze_intertie_utilization
  • analyze_market_event
  • analyze_net_load
  • analyze_outage_impact
  • analyze_ramps
  • analyze_supply_stack
  • analyze_supply_surplus_events
  • assess_supply_tightness
  • calculate_asset_energy_revenue
  • calculate_capture_prices
  • compare_csd_to_metered
  • compare_forecast_to_actual
  • compare_market_periods
  • explain_market_conditions
  • find_price_events
  • get_approved_transmission_outages
  • get_assets
  • get_dispatch_down_service
  • get_energy_merit_orderwrite action
  • get_ffr_net_schedule
  • get_forecast
  • get_generation
  • get_generation_capacity
  • get_historical_generation
  • get_historical_store_status
  • get_interchange
  • get_intertie_capability
  • get_intertie_outages
  • get_load
  • get_load_outage_forecast
  • get_long_range_transmission_outages
  • get_market_snapshot
  • get_metered_volumes
  • get_monthly_cumulative_net_revenue
  • get_operating_reserve_activations
  • get_operating_reserve_forecast
  • get_operating_reserve_offer_control
  • get_operating_reserve_prices
  • get_outages
  • get_pool_prices
  • get_price_duration_curve
  • get_price_statistics
  • get_reserves
  • get_secondary_offer_price_limit
  • get_supply_adequacy
  • get_supply_surplus
  • get_system_events
  • get_system_marginal_prices
  • get_tmr_reference_price
  • get_uc_settlement_summary
  • get_unit_commitments
  • summarize_market_history
  • summarize_operating_reserve_market
  • sync_historical_store

Public scan report

scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it

no findings
  • Code scan76 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 32 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How AESO MCP compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 57% of 48,255 servers
Tools
57
the typical server has 7
Tools that change things
2%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
35
more than 25% of 12,191 servers with a package

What its tools let an agent do: 55 read · 2 change

Install AESO MCP in Claude Code, Cursor or VS Code

claude mcp add aeso-mcp -- uvx aeso-mcp
Add to Cursor

What the publisher says

From the AESO MCP repository's README, as published. We do not edit it. Read it on GitHub

aeso-mcp

<!-- mcp-name: io.github.bchoi-qwe/aeso-mcp -->

Agent-native, strongly typed access and analytics for Alberta's electricity market using official AESO data.

Independent open-source project. Not affiliated with or endorsed by the Alberta Electric System Operator (AESO).

What it is

aeso-mcp is a Model Context Protocol (MCP) server that exposes Alberta electricity-market observations and deterministic analytics to AI clients. It is designed for energy analysts, researchers, developers, journalists, market participants, and AI agents that need reliable, structured AESO data—not a thin REST decorator layer.

Features

one typed getforecast contract, with persisted publication vintages and point-in-time asof selection that excludes unknown publication chronology

  • Typed MCP tools with Pydantic inputs/outputs and structured results
  • Current market snapshot combining price, load, generation, interchange, and reserves
  • Paginated historical Pool Price, System Marginal Price, load, and generation retrieval
  • Official individual-asset Historical CSD Generation Data at hourly and five-minute resolution
  • Optional incremental DuckDB index and partitioned Parquet snapshots for repeatable research
  • Official AIL, Pool Price, wind, solar, and combined wind/solar forecast publications through

reference-price, and AIES system-event reports

  • Official supply-adequacy, supply-surplus, FFR Net Schedule, Dispatch Down Service, TMR

load/generation, constrained volume, EEA events, operating-reserve directives, and the current Pool Participant registry through one typed research-archive contract

  • Official historical adequacy/cushion web codes, transmission outages, planning-area hourly

metered volumes, and operating-reserve offer control

  • Authenticated APIM reports for merit order, commitments, capability/outages, interties,

condition evidence, price distributions, capture price, net load, supply stack, generation, outage association, generalized forecast accuracy, asset gross energy revenue, CSD-versus- metered comparisons, ramps, supply-surplus associations, and transparent supply-tightness indicators, plus participant concentration, regional, constrained-volume, scarcity, and compact system-frequency analysis

  • Deterministic analytics: compact history summaries, period comparison, event detection,

completeness, and degradation warnings for multi-source market-event analysis

  • Deterministic research manifests identify exact input publications, parameters, methodology,

reduced credential-free server mode

  • Public operating-reserve active/standby prices, seven-day forecasts, activations, and summaries
  • One complete server package and startup path: AESOAPIKEY is always required; there is no

secret-safe machine-readable errors

  • Query bounds, cache provenance, completeness metadata, upstream Retry-After handling, and

non-loopback binds by default, rate/concurrency limits, request-size bounds, probes, and correlation IDs

  • Hardened HTTP transport with Host/Origin validation, bearer authentication required for
  • Reusable MCP prompts plus glossary, capability, dataset, and methodology resources

Implemented datasets

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

AESO MCP: common questions

Is AESO MCP server safe?
Mostly: it is graded B (78/100). Read the AESO MCP safety report
How do I install AESO MCP?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does AESO MCP need an API key?
Yes. The registry entry asks for AESO_API_KEY.
Is AESO MCP maintained?
The last commit was 36 days ago (2026-09-29). The latest release is v0.3.0.
How does AESO MCP compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,255 servers); tools 57 (the typical server has 7); tools that change things 2% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.