mocop
Browse · Docs · Guide · Analyze

NEMPulse MCP

MCP server by NEMPulse · mcp

NEMPulse: Australian NEM grid-scale battery (BESS) data, derived from AEMO public reports. Read-only, no auth. Workflow: batteries are identified by DUID (e.g. HPR1 = Hornsdale). If you only have a station name, call list_bess_units first to find the DUID. Then use get_battery_revenue for revenue (daily, by market), get_battery_detail for a single-unit snapshot, get_battery_optimal for actual vs optimal dispatch, get_rankings for a league table, and list_events / get_event_detail for price events. get_network_access / get_battery_network_access show how often binding network constraints limited each battery's discharge or charging (exposure, not lost revenue), and get_battery_mlf its loss factors by year. query_nem_data answers ad hoc questions the other tools cannot, but it is slow and the least reliable, so prefer the structured tools. It does not return live or current 5-minute prices: NEMPulse publishes daily price summaries only (get_regional_prices); AEMO NEMWEB DISPATCHPRICE h…

Endpoint: https://nempulse.com.au/mcp

Verification: observed. Source: crawl.

Capabilities (14)

  • list_bess_units
  • get_fleet_summary
  • get_battery_detail
  • query_nem_data
  • get_battery_revenue
  • get_battery_optimal
  • list_events
  • get_event_detail
  • get_regional_prices
  • get_simulator_revenue
  • get_rankings
  • get_network_access
  • get_battery_network_access
  • get_battery_mlf
About · Contact · Privacy