Remote MCP · Endpoint

au.com.nempulse/nempulse MCP server

No. au.com.nempulse/nempulse answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://nempulse.com.au/mcp

The last check completed an MCP handshake.

Registry name
au.com.nempulse/nempulse
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
2.73 s
Tools exposed
11 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Australian NEM battery (BESS) data for AI agents: revenue, dispatch, FCAS, events. Free, no auth.
Website
https://nempulse.com.au/
Repository
https://github.com/FDSchaefer/bessPerformance
Listing
From the official MCP registry (active).
Recent checks of au.com.nempulse/nempulse
CheckedResultHandshake
9 hours agoHandshake completed2.73 s
2 days agoHandshake completed962 ms
4 days agoHandshake completed888 ms
5 days agoHandshake completed834 ms
7 days agoHandshake completed897 ms
8 days agoHandshake completed851 ms
9 days agoHandshake completed933 ms
12 days agoHandshake completed843 ms
14 days agoHandshake completed881 ms
15 days agoHandshake completed951 ms
16 days agoHandshake completed830 ms
18 days agoHandshake completed834 ms
19 days agoHandshake completed849 ms
19 days agoHandshake completed860 ms
20 days agoHandshake completed875 ms
21 days agoHandshake completed2.25 s
23 days agoHandshake completed1.01 s

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with au.com.nempulse/nempulse and makes no claim about it beyond what these checks measured.