EVS Meter Tools

Name: EVS Meter Tools
Author: nicholasohjj

by nicholasohjjversion 2.0.1i★ –iRuns in the cloud

Registry nameio.github.nicholasohjj/nusaircon

Install

Overview

Description from the maker (original English)

Check NUS and SUTD hostel EVS electricity meters and get top-up links. Unofficial.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiVery new★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
Can do 4 things (tools) get_meter_balance, get_meter_usage, get_recent_topups, get_topup_link
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://nusaircon-production.up.railway.app/mcp

Run this in your terminal

claude mcp add --transport http nusaircon https://nusaircon-production.up.railway.app/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "nusaircon": {
      "url": "https://nusaircon-production.up.railway.app/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "nusaircon": {
      "type": "http",
      "url": "https://nusaircon-production.up.railway.app/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://nusaircon-production.up.railway.app/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

get_meter_balance
Get the current prepaid credit balance of a meter, in SGD.
get_meter_usage
Get up to 7 days of usage for an NUS meter, with spending analysis, month-to-date spending, and how long the balance may last. Amounts are in SGD. Dates are as EVS reports them, with no time zone, and recent days may be missing. Not available for SUTD meters.
get_recent_topups
Get up to 10 recent top-ups for a meter. To confirm a payment, look for a top-up with the same amount dated after the createdAt of its link, and with no status showing it failed. Earlier top-ups can have the same amount, so always check the date. Dates have no time zone and appea
get_topup_link
Create a link to the secure top-up page, for the user to open and pay by card themselves. Creating the link charges nothing. Refuses a meter EVS doesn't recognise. If EVS can't be reached, meterVerified is false, so ask the user to check the meter on the page. NUS allows $6-$50 a

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account nicholasohjj, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 1110 ms (HTTP 200)
– Not applicable
Sign-in with OAuth
No sign-in needed
✓ Pass
No hidden instructions in tool descriptions
Read 4 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

More stars than 0% of the other 18496 servers in this category
Published to the registry more recently than 94% of the other 18496 servers in this category
Basic checks equal to or better than 100% of the other 18496 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is EVS Meter Tools safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.0.1) reached the registry 3 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, MIDAS Gen NX / Civil NX

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

by formulahendryEarly↓ 66/wk★ 440Updated 14 months ago

Runs on your computer

Install

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

by desktop-commanderGrowing★ 211Updated 3 days ago

Runs in the cloud✓ desktopcommander.app

Install

MIDAS Gen NX / Civil NX

Read and carefully change the model open in MIDAS Gen NX or Civil NX on this PC.

by Dennis5882Early↓ 1.9K/wkUpdated today

Runs on your computer

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

EVS Meter Tools

A Telegram bot and web app for supported EVS electricity meters. Supported NUS and SUTD meters can be topped up by credit card, and supported lookup flows show balance, usage, and top-up history where available.

Supported systems

Hostel group	EVS system
NUS hostels, including PGPR, Houses @ PGP, Residential Colleges, NUS College, UTown Residences, RVRC, Valour House	`cp2nus.evs.com.sg`
SUTD	`SUTDMain` / `EVSSUTDWebPOS`

The legacy NUS CP2 fallback (cp2.evs.com.sg) is hidden from the web app and bot. Its backend routes and services are kept but are not linked from any UI; see CP2 — legacy NUS fallback (hidden).

Features

Check meter balance, 7-day usage history, and recent top-ups from within Telegram
Top up supported NUS electricity meters via credit card (SGD $6-$50)
Top up supported SUTD electricity meters via credit card (SGD $10-$50)
RSA-encrypted card entry — card details never leave the browser in plaintext
Works as a Telegram Mini App and as a standalone website
Cross-system guard: cp2nus bootstrap rejects meters that belong to the legacy cp2 system before initiating payment
SUTD balance, top-up history, and top-up support
Analytics tracking and error capture throughout the flow
Opt-in low-balance alerts on Telegram, with a button to start a top-up
Read-only MCP server, so people can connect their own Claude and set their own instructions

Architecture

Telegram Bot (telegraf)          Website (React, /app/)

│ │ ├── /topup └── HomePage ├── /balance └── system selection ├── /usage + meter ID + amount └── /topups │ webhook in production/Railway, │ │ polling in development │ ▼ ▼ Express (server.js) ←──────────────────────────── │ ├── POST /telegram/webhook/* — Telegram webhook receivers ├── GET /webapp — legacy CP2 (hidden from UI): fetches meter summary, redirects to React ├── GET /webapp/bootstrap — runs full payment init, returns token ├── GET /webapp/session — returns session data as JSON for React ├── GET /webapp/pay — redirects to React card entry page ├── POST /webapp/enets_pay — proxies encrypted card data to eNETS ├── POST /webapp/notify — fallback Telegram payment notification └── GET /webapp/result — redirects to React result page

React Frontend (/app/) ├── / — HomePage (system + meter ID + amount) ├── /balance — HomePage opened in balance-check mode ├── /cp2nus — HomePage preselected for primary NUS CP2NUS flow ├── /cp2nus/loading — cp2nus variant ├── /cp2nus/pay — cp2nus variant ├── /cp2nus/result — cp2nus variant ├── /sutd/loading — SUTD variant ├── /sutd/pay — SUTD variant └── /sutd/result — SUTD variant

Payment flows

CP2 — legacy NUS fallback (hidden)

Hidden. This flow is no longer offered in the web app or bot. The /app/cp2, /app/loading, /app/pay, and /app/result React routes are commented out in frontend/src/App.jsx, /app/cp2 is excluded from the sitemap and robots.txt, and the bot no longer shows a hostel picker. The backend routes and services below are kept for reference and possible reinstatement.

Scrapes the legacy EVS WebPOS portal to create a transaction, then proxies through eNETS. It was used only for NUS meters that had not migrated to CP2NUS.

`/webapp` — fetches meter address and balance from ORE, redirects to React loading page with address/balance in query params
Bootstrap (/webapp/bootstrap) — runs runPurchaseFlow and getMeterSummary in parallel:

GET /EVSWebPOS/ → login → POST /loginServlet (meter validation)
POST /selectOfferServlet (amount selection)
GET /paymentServlet → extract merchant_txn_ref
POST creditpayment.jsp → extract eNETS message
POST /enets2/PaymentListener.do → extract RSA public key (n, e), netsMid, netsTxnRef
Creates a payment session (10-min TTL), redirects to React card page

Card page (/app/pay) — React component; fetches session via /webapp/session; encrypts cardNo + cvv with eNETS RSA scripts client-side
Payment proxy (/webapp/enets_pay):

POST https://www.enets.sg/GW2/uCredit/pay
Preferred path: extracts EVS callback form → POST /EVSWebPOS/transSumServlet → parseEvsTransactionSummary
Fallback: parseEnetsResult scrapes the eNETS receipt HTML directly
Writes outcome (status, merchantTxnRef, reason) back to the server-side session

Result page (/app/result) — React component; reads outcome from server session via /webapp/session

CP2NUS — primary NUS hostel flow

Uses the EVS JSON API and the eNETS Payment Page (enetspp) host directly. This is the primary NUS hostel flow for migrated meters.

`/webapp` — same as cp2; fetches meter info, redirects to /app/cp2nus/loading
Bootstrap (/cp2nus/webapp/bootstrap) — runBootstrap runs sequentially:

Meter system check — isCp2Meter() guard: rejects cp2 meters with a WRONG_SYSTEM error; on network failure the check is skipped and flow proceeds
`init_pay` — POST /enets/init_pay → { txn_identifier, req, sign }
`meter_info` — getMeterSummary → buildPayDisplayAddress
`enetspp_pay` — buildEnetsPayUrl → GET enetspp/pay?p=… → extract txnReq, keyId, hmac
`TxnReqListener` — POST /GW2/TxnReqListener → RSA key, netsTxnRef, netsMid, paymtNetsMid, txnRand, keyId, hmac

Card page (/app/cp2nus/pay) — same RSA encryption; paymtNetsMid (acquiring MID) used in panSubmitForm, not top-level netsMid
Payment proxy (/cp2nus/webapp/enets_pay):

GET /GW2/pluginpages/env.jsp → seed JSESSIONID
POST /GW2/credit/init;jsessionid=…
POST /GW2/credit/panSubmitForm
Preferred path: netsTxnStatus in response → preParsed result (no b2s call)
Fallback: POST /enets/b2s → 303 redirect → parsePayResult base64-decodes params

Result page (/app/cp2nus/result) — reads outcome from server session

SUTD

Uses the SUTD EVS WebPOS pages and the SUTD credit payment bridge.

`/sutd/webapp` — fetches SUTD meter credit, redirects to /app/sutd/loading
Bootstrap (/sutd/webapp/bootstrap) — runs the SUTD WebPOS flow:

POST /EVSSUTDWebPOS/loginServlet with the meter ID
POST /EVSSUTDWebPOS/selectOfferServlet with the selected amount
GET /EVSSUTDWebPOS/paymentServlet → extract merchant_txn_ref
POST http://120.50.44.233/payment_sutd_credit/creditpayment.jsp
POST /enets2/PaymentListener.do → extract RSA public key, netsMid, netsTxnRef

Card page (/app/sutd/pay) — same RSA-encrypted card entry as NUS flows
Payment proxy (/sutd/webapp/enets_pay) — posts encrypted card data to eNETS, then posts the callback to /EVSSUTDWebPOS/transSumServlet
Result page (/app/sutd/result) — reads outcome from server session

Setup

Prerequisites

Node.js 20.19+ (22.12+ on Node 22)
A Telegram bot token (from @BotFather)
A publicly accessible HTTPS server (required for Telegram WebApp buttons)

Installation

# Install backend dependencies

npm install

Install and build the frontend

npm run build:frontend

Environment variables

Create a .env file:

TELEGRAM_BOT_TOKEN=your_bot_token_here      # legacy single-bot token

NUS_TELEGRAM_BOT_TOKEN=your_nus_bot_token # optional, for concurrent nusairconbot SUTD_TELEGRAM_BOT_TOKEN=your_sutd_bot_token # optional, for concurrent sutdairconbot PAYMENT_SESSION_SECRET=replace_with_openssl_rand_hex_32 # stable secret for signed payment/result tokens SERVER_URL=https://your-public-server.example.com OWNER_CHAT_ID=your_telegram_chat_id # receives feedback notifications MAINTENANCE_MODE=false # set to "true" to put the app and bot in global maintenance mode MAINTENANCE_MESSAGE= # optional custom global maintenance message OWNER_STATUS_TIMEOUT_MS=4000 # optional timeout for owner /status EVS/eNETS checks TOPUP_DISABLED=false # set to "true" to show maintenance message DB_DIR=. # local SQLite dir; use /data on Railway with a mounted volume TELEGRAM_BOT_MODE= # production/Railway defaults to webhook; dev defaults to polling TELEGRAM_BOT_AUDIENCE=nus # legacy single-bot mode: "nus" or "sutd" LOW_BALANCE_CRON_SECRET= # optional, enables the low-balance check endpoint MCP_ALLOWED_ORIGINS= # optional, comma-separated extra browser origins allowed to call /mcp GOOGLE_SITE_VERIFICATION_FILE= # optional Search Console HTML file name, e.g. googleabc123.html GOOGLE_SITE_VERIFICATION_CONTENT= # optional exact file body if Google provides non-default content

SERVER_URL must be HTTPS for the Telegram WebApp payment button to work. If it is HTTP, the bot falls back to a plain browser link instead. On Railway, set it to https://${{RAILWAY_PUBLIC_DOMAIN}} or leave it unset and the app will derive it from RAILWAY_PUBLIC_DOMAIN.

PAYMENT_SESSION_SECRET should be a stable random value, for example from openssl rand -hex 32. If it is omitted, the app falls back to the configured bot token, which still survives Railway sleeps as long as the bot token does not change.

For Google Search Console URL-prefix verification, use the HTML file method and set GOOGLE_SITE_VERIFICATION_FILE to the downloaded file name. The default response body is google-site-verification: . If Google's downloaded file contains different text, set GOOGLE_SITE_VERIFICATION_CONTENT to the exact file body.

In production, or when RAILWAY_PUBLIC_DOMAIN is present, each configured bot uses a Telegram webhook by default so Railway Serverless can sleep and wake from inbound Telegram requests. Set TELEGRAM_BOT_MODE=polling only for an always-on deployment. Optional webhook variables are TELEGRAM_WEBHOOK_PATH, TELEGRAM_WEBHOOK_SECRET, and TELEGRAM_DROP_PENDING_UPDATES for single-bot mode. For concurrent bots, use NUS_TELEGRAM_WEBHOOK_PATH, NUS_TELEGRAM_WEBHOOK_SECRET, SUTD_TELEGRAM_WEBHOOK_PATH, and SUTD_TELEGRAM_WEBHOOK_SECRET only if you need custom paths; otherwise unique paths are generated automatically.

For concurrent Telegram bots in one deployment, set both NUS_TELEGRAM_BOT_TOKEN and SUTD_TELEGRAM_BOT_TOKEN. The same service starts both nusairconbot and sutdairconbot, with separate command menus, webhook paths, in-memory sessions, and payment notifications. Single-bot deployments can still use TELEGRAM_BOT_TOKEN plus TELEGRAM_BOT_AUDIENCE.

Running

# Development (two terminals)

npm run dev # Express backend on :3000 npm run dev:frontend # Vite dev server on :5173

Production

npm run build:frontend npm start

The frontend is served at /app/ by Express in production. In development, Vite proxies /webapp, /cp2nus, and /sutd to the backend.

For local development, keep DB_DIR=. or omit it. On Railway, set DB_DIR=/data only after attachi

Only the beginning is shown; read the rest in the repo

EVS Meter Tools

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

MIDAS Gen NX / Civil NX

README from the maker

EVS Meter Tools

Supported systems

Features

Architecture

Payment flows

CP2 — legacy NUS fallback (hidden)

CP2NUS — primary NUS hostel flow

SUTD

Setup

Prerequisites

Installation

Install and build the frontend

Environment variables

Running

Production