io.ausdata/aemo-mcp
PYPI · AEMO-MCP
Query the AEMO NEM in plain English — 5-min prices, demand, generation, rooftop PV.
Available components
Last scanned (9 hours ago)
Scores higher than 91% of PyPI servers
Category Data and Analytics
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 24 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency71
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to Bigred97/aemo-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 100 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1379 tokens (~275/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.93 functional
- 31 Oct 26 0
- Package version: 0.4.15 → 0.4.20 functional
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
- 23 Oct 26 −5
- Source repository: pass → fail ▼ security
- 19 Oct 26 +1
- Stability: 0.97 → pass security
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/aemo-mcp@0.4.20
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Bigred97/aemo-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Bigred97/aemo-mcp/.github/workflows/release.yml@refs/tags/v0.4.20 |
| Rekor log index | 2257320032 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:68955a686b5791d0bbe8f21949c813b6f2a2d4bf58720c90562e8fca710042e8 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 24 packages
| Packages resolved | 24 |
|---|---|
| Stale | 1 |
| 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 →
describe_dataset ~152
Describe one NEM dataset — schema, filters, cadence, source URL. Examples: detail = await describe_dataset("dispatch_price") # → filters: [{key: "region", values: ["NSW1", "QLD1", ...]}] # → metrics: {rrp: "$/MWh"} # → cadence: "5 min" Returns: DatasetDetail with id, name, description, filters, units, source URL, and example invocation strings.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | Dataset ID like 'dispatch_price', 'generation_scada'. Use the search endpoint or search tool to discover, or the list-curated endpoint/tool to enumerate. Case-insensitive. |
| Name | Type | Req | Description |
|---|---|---|---|
| cadence | – | – | – |
| description | string | yes | – |
| examples | array | – | – |
| filters | array | – | – |
| id | string | yes | – |
| is_curated | boolean | yes | – |
| name | string | yes | – |
| source_url | string | yes | – |
| units | object | – | – |
No examples provided.
get_data ~468
Query an AEMO NEM dataset and return observations. Examples: # Latest NSW dispatch price (preferred over latest() if you want # a window) resp = await get_data("dispatch_price", filters={"region": "NSW1"}) # Whole-day NSW dispatch price for a specific day resp = await get_data( "dispatch_price", filters={"region": "NSW1"}, start_period="2026-05-13", end_period="2026-05-13" ) # Generation by fuel for QLD, current resp = await get_data("generation_scada", filters={"region": "QLD1"}) # All 6 interconnectors right now resp = await get_data("interconnector_flows") Returns: DataResponse with records, units, period bounds, NEMWEB source URL, and AEMO attribution.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | Dataset ID like 'dispatch_price'. Use the search endpoint or search tool to discover. |
| end_period | – | – | Inclusive end. Same format as start_period. |
| filters | – | – | Dict of filter key → value(s). Common filters: 'region' (NSW1/QLD1/SA1/TAS1/VIC1), 'interconnector' (V-SA/Basslink/...), 'duid' (unit ID), 'fuel' (black_coal/gas/wind/solar/battery/...). Each dataset… |
| format | string | – | Response shape. 'records' (default): flat list of observations. 'series': observations grouped by dimensions. 'csv': returns the result as a CSV string in the `csv` field. |
| start_period | – | – | Inclusive start of the period window in AEMO market time (UTC+10). Accepts 'YYYY', 'YYYY-MM', 'YYYY-MM-DD', or 'YYYY-MM-DD HH:MM'. Defaults to None which fetches just the most recent NEMWEB file for… |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | – |
| csv | – | – | – |
| dataset_id | string | yes | – |
| dataset_name | string | yes | – |
| interval_end | – | – | – |
| interval_start | – | – | – |
| period | object | – | Canonical {start, end} period bounds for cross-sister consumers. Populated alongside aemo-specific interval_start/interval_end. |
| query | object | – | – |
| records | – | – | – |
| retrieved_at | string | yes | – |
| row_count | integer | – | Number of observation rows in records. |
| server_version | string | – | – |
| source | string | – | – |
| source_url | string | yes | – |
| stale | boolean | – | – |
| stale_reason | – | – | – |
| truncated_at | – | – | – |
| unit | – | – | – |
No examples provided.
latest ~316
Return the most recent interval(s) for a NEM dataset. For 5-min feeds (dispatch_price, dispatch_region, interconnector_flows, generation_scada): returns the most recent 5-minute interval, typically 1-2 minutes after the interval close. For 30-min feeds (rooftop_pv, predispatch_30min): the most recent half-hour. For daily feeds (daily_summary): yesterday's data. Examples: # Current NSW spot price resp = await latest("dispatch_price", filters={"region": "NSW1"}) # Current generation mix in QLD resp = await latest("generation_scada", filters={"region": "QLD1"}) # Current flow across Heywood resp = await latest("interconnector_flows", filters={"interconnector": "V-SA"}) Returns: DataResponse with one observation per filtered (dimension, metric) tuple at the most recent interval. `stale=True` flag indicates the most recent interval is older than 2× the feed cadence (NEMWEB delay).
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | Dataset ID like 'dispatch_price'. Use the search endpoint or search tool to discover. |
| filters | – | – | Optional filter dict. Same shape as get_data — narrow to a region, interconnector, fuel, etc. Also accepts a JSON-encoded string (e.g. '{"region": "NSW1"}') for MCP clients that serialize object argu… |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | – |
| csv | – | – | – |
| dataset_id | string | yes | – |
| dataset_name | string | yes | – |
| interval_end | – | – | – |
| interval_start | – | – | – |
| period | object | – | Canonical {start, end} period bounds for cross-sister consumers. Populated alongside aemo-specific interval_start/interval_end. |
| query | object | – | – |
| records | – | – | – |
| retrieved_at | string | yes | – |
| row_count | integer | – | Number of observation rows in records. |
| server_version | string | – | – |
| source | string | – | – |
| source_url | string | yes | – |
| stale | boolean | – | – |
| stale_reason | – | – | – |
| truncated_at | – | – | – |
| unit | – | – | – |
No examples provided.
list_curated ~223
List every curated AEMO NEM dataset ID. These cover the great majority of typical NEM analytic queries: spot prices, regional demand and generation, interconnector flows, unit-level SCADA, rooftop PV (actual + forecast), 30-min predispatch forecasts, dispatch constraints, FCAS ancillary-service prices, trading (settlement) prices, and daily-settled summaries. Call this tool to get the live list rather than assuming a fixed count — the registry grows over time as new curated datasets are added. Example: ids = list_curated() # → ['daily_summary', 'dispatch_constraints', 'dispatch_price', # 'dispatch_region', 'fcas_prices', 'generation_scada', # 'interconnector_flows', 'predispatch_30min', 'rooftop_pv', # 'trading_price'] Returns: Sorted list of dataset IDs. Do not hardcode the count in calling code — query this tool live, since the registry grows.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
search_datasets ~220
Fuzzy-search the 7 curated AEMO NEM datasets. Use this when you don't know the exact dataset_id. The 7 curated datasets cover ~95% of typical NEM analytic queries — spot prices, demand, generation, rooftop PV, interconnector flows, forecasts. Examples: # Find the dataset that publishes the spot price results = await search_datasets("spot price") # → [{id: 'dispatch_price', name: 'NEM Dispatch Price ...', ...}] # Discover what's available on rooftop solar results = await search_datasets("rooftop pv", limit=5) Returns: List of DatasetSummary (id, name, description, cadence), ranked by relevance. All v0 datasets are curated.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results to return, ranked by relevance. |
| query | string | yes | Free-text search query. Matches against dataset IDs, names, descriptions, filter keys, region values, and search keywords. Case-insensitive. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
How do I install the io.ausdata/aemo-mcp server?
io.ausdata/aemo-mcp runs locally as a PyPI package, launched with uvx aemo-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 · aemo-mcp
claude mcp add io-ausdata-aemo-mcp -- uvx aemo-mcp
What is the io.ausdata/aemo-mcp server?
io.ausdata/aemo-mcp is listed in the public MCP registry as io.ausdata/aemo-mcp. Query the AEMO NEM in plain English, 5-min prices, demand, generation, rooftop PV. This page covers its PyPI package (aemo-mcp).
Is the io.ausdata/aemo-mcp server safe to use?
io.ausdata/aemo-mcp scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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.
What tools does the io.ausdata/aemo-mcp server expose?
io.ausdata/aemo-mcp exposes 5 tools: search_datasets, describe_dataset, get_data, latest, list_curated. Their descriptions and schemas cost roughly 1,379 tokens of context every time the server is loaded.
Is the io.ausdata/aemo-mcp server still maintained?
io.ausdata/aemo-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 io.ausdata/aemo-mcp server under?
io.ausdata/aemo-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.