Model Context Protocol (MCP) server for freee API integration
Nothing to run from here
Nempulse is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
11
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Australian NEM battery (BESS) data for AI agents: revenue, dispatch, FCAS, events. Free, no auth.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http nempulse-mcp https://nempulse.com.au/mcp
# 2 — ask your agent for something these tools do
# list_bess_units, get_fleet_summary, get_battery_detail and 8 more
Nempulse costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
NEAll 1 server
nempulse1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http nempulse-mcp https://nempulse.com.au/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Reference list of every NEM-registered grid-scale battery. Call this first to turn a station name into the DUID the other tools need. Returns the whole fleet in one response (no filters): DUID, station, region, MW/MWh, MLF, coordinates, is_commissioning, commercial_context, unit_class, peer_comparable, rev_per_mw_yr. Caveats on the fields follow. rev_per_mw_yr is trailing 365-day energy + FCAS rev
No parameter schema on file.
Fleet-wide snapshot for the NEM battery fleet: unit_count, active_unit_count, total_mw, total_mwh, fleet_rev_mtd, avg_efficiency_pct, last_interval and spot_prices (latest price per region, $/MWh). Covers month-to-date unless date_from and date_to are given. fleet_rev_mtd is gross spot revenue (energy + FCAS + FPP) over that window, whatever its length, despite the name. avg_efficiency_pct is doll
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date_from | string | no | Optional. Start date YYYY-MM-DD (requires date_to). Omit both for month-to-date. |
| date_to | string | no | Optional. End date YYYY-MM-DD (requires date_from). |
| include_commissioning | boolean | no | Include units still commissioning in the efficiency figure (default false). |
Deep-dive metrics for one battery by DUID (e.g. HPR1 = Hornsdale): revenue, dispatch, SOC, FCAS. WARNING: rev_today, energy_rev_today, fcas_rev_today and contingency_fcas_rev_today are MONTH-TO-DATE by default, not daily (matching the rev_mtd keys in fcas_breakdown) — do not report them as 'today's revenue'. throughput_cycles, throughput_mwh, avg_dispatch_price, avg_charge_price and efficiency_pct
| Parameter | Type | Required | Notes |
|---|---|---|---|
| duid | string | yes | Battery DUID, e.g. HPR1. Use list_bess_units to find it from a station name. |
| date_from | string | no | Optional start date YYYY-MM-DD (scopes revenue/throughput stats; requires date_to too). Omit both for the month-to-date default. |
| date_to | string | no | Optional end date YYYY-MM-DD (requires date_from too). |
Last resort for ad hoc questions the other tools cannot answer. Takes a plain-English question, generates SQL over NEMPulse's tables, and returns the SQL, the result rows and a short explanation. It is the slowest tool (can take close to a minute) and it is AI-generated, so check the returned SQL before relying on a number. Scope each question to about one region-month or less: wider aggregates (a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | Plain-English question, max 500 characters. Name the region and date range, e.g. 'Which SA1 battery earned the most FCAS revenue in August 2026?' |
Daily gross-spot revenue by market (energy + FCAS) for one battery (DUID) over a date range. Daily grain only. This is the tool for total revenue questions — use get_battery_optimal only for the actual-vs-perfect-foresight benchmark, not as a revenue source (its 'actual' figure is MLF-adjusted and solved-days-only, so it will not match this tool's totals). Each day also carries energy_rev_mlf_adju
| Parameter | Type | Required | Notes |
|---|---|---|---|
| duid | string | yes | Battery DUID, e.g. HPR1. Use list_bess_units to find it from a station name. |
| date_from | string | yes | Start date, YYYY-MM-DD (inclusive). |
| date_to | string | yes | End date, YYYY-MM-DD (inclusive). |
Actual vs LP-optimal dispatch revenue, per-DUID summary, over a date range (energy-only, perfect-foresight benchmark). NOT a revenue-total source — use get_battery_revenue for that. Both the 'actual' AND the 'optimal' figures here are MLF-adjusted (get_battery_revenue's is gross) — the LP's objective is solved on MLF-adjusted prices, not just settled at them afterward — and both cover solved LP da
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date_from | string | yes | Start date, YYYY-MM-DD (inclusive). |
| date_to | string | yes | End date, YYYY-MM-DD (inclusive). |
| duid | string | no | Battery DUID, e.g. HPR1 (optional — omit for all DUIDs) |
List NEM spot-price events, newest first. An event is a run of 5-minute intervals in one region where the price stays above $500/MWh or below -$200/MWh (short gaps are bridged), typed by its peak price: negative (below -$200), elevated (peak $500 to $1,000), spike ($1,000 to $5,000) or extreme ($5,000 and above). Each event has event_id, region, event_type, started_at, ended_at, duration_min, peak
| Parameter | Type | Required | Notes |
|---|---|---|---|
| region | string | no | NEM region code: NSW1, QLD1, SA1 (South Australia), TAS1 or VIC1. |
| event_type | string | no | Optional event type filter. |
| date_from | string | no | Optional. Only events starting on or after this date, YYYY-MM-DD. |
| date_to | string | no | Optional. Only events starting on or before this date, YYYY-MM-DD. |
| limit | integer | no | Max events to return (default 10, max 500). |
| offset | integer | no | Skip this many events, for paging (default 0). |
| include_responses | boolean | no | Also return per-battery responses for each event (default false). |
One price event by event_id (take the id from list_events), with the response of every battery that was online, ranked by est_revenue. Event fields are as in list_events. Each battery row has duid, station, region, response (DISCH = discharging, CHRG = charging, IDLE, OFFLINE = no availability), avg_mw (positive is discharge), peak_mw, est_revenue (energy only, sum of MW times price over the event
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Event id, as returned in event_id by list_events. |
Daily minimum, maximum and mean regional reference price (RRP, $/MWh) for one NEM region over a date range. Daily summary only: the raw 5-minute price series is not exposed (it is published by AEMO on NEMWEB). Use it for price context around revenue or events. For individual price spikes use list_events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| region | string | yes | NEM region code: NSW1, QLD1, SA1 (South Australia), TAS1 or VIC1. |
| date_from | string | yes | Start date, YYYY-MM-DD (inclusive). |
| date_to | string | yes | End date, YYYY-MM-DD (inclusive). |
Modelled revenue for a hypothetical 1 MW battery of a given duration in one region (not a real unit), from NEMPulse's optimal-dispatch model on real prices. Returns P10/P50/P90 revenue for three tiers: realistic (forecast-informed result scaled by the capture ratio real batteries achieve, the only tier to use as a project case), forecast_informed (idealised execution on AEMO's public price forecas
| Parameter | Type | Required | Notes |
|---|---|---|---|
| region | string | yes | NEM region code: NSW1, QLD1, SA1 (South Australia), TAS1 or VIC1. |
| duration | number | yes | Battery duration in hours: 1, 2 or 4. |
League table of merchant NEM batteries over a date range, ranked by capture rate by default (actual revenue as a share of the forecast-informed benchmark; capture_perfect_pct is the share of the perfect-foresight ceiling). Each row has rank, duid, station, region, capacity, duration_band, capture_fc_pct, capture_perfect_pct, rev_per_mw_day, rev_per_mwh_day, total_rev, cycles_per_day and movement a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date_from | string | yes | Start date, YYYY-MM-DD (inclusive). |
| date_to | string | yes | End date, YYYY-MM-DD (inclusive). |
| region | string | no | NEM region code: NSW1, QLD1, SA1 (South Australia), TAS1 or VIC1. |
| duration_band | string | no | Optional. Under 2 hours, 2 to 4 hours, or over 4 hours. |
| sort_by | string | no | Ranking metric (default capture_fc). |
| include_arrangement | boolean | no | Rank CONTRACTED and TOLLED units too (default false). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Nempulse or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.1.
1.1.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Nempulse can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.