Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Check NUS and SUTD hostel EVS electricity meters and get top-up links. Unofficial.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Funciona en Claude para web, escritorio y móvil:
https://nusaircon-production.up.railway.app/mcpEjecuta esto en tu terminal
claude mcp add --transport http nusaircon https://nusaircon-production.up.railway.app/mcpPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"nusaircon": {
"url": "https://nusaircon-production.up.railway.app/mcp"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"nusaircon": {
"type": "http",
"url": "https://nusaircon-production.up.railway.app/mcp"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
ChatGPT solo se conecta a servidores en internet:
https://nusaircon-production.up.railway.app/mcpLos nombres de los menús pueden variar un poco según el plan y con el tiempo.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Nombres y descripciones de las herramientas tal como los informó el servidor el 6 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.
get_meter_balanceGet the current prepaid credit balance of a meter, in SGD.
get_meter_usageGet 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_topupsGet 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_linkCreate 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
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 8 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub nicholasohjj, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Respondió en 1110 ms (HTTP 200)
No hace falta iniciar sesión
Leímos 4 descripciones de herramientas y no encontramos instrucciones ocultas para la IA
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 3 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.
El repo de GitHub cambió por última vez –, y la última versión (2.0.1) llegó al registro anteayer.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Tethered Trust
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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.
| 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).
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
Hidden. This flow is no longer offered in the web app or bot. The
/app/cp2,/app/loading,/app/pay, and/app/resultReact routes are commented out infrontend/src/App.jsx,/app/cp2is 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/bootstrap) — runs runPurchaseFlow and getMeterSummary in parallel:GET /EVSWebPOS/ → login → POST /loginServlet (meter validation)POST /selectOfferServlet (amount selection)GET /paymentServlet → extract merchant_txn_refPOST creditpayment.jsp → extract eNETS messagePOST /enets2/PaymentListener.do → extract RSA public key (n, e), netsMid, netsTxnRef/app/pay) — React component; fetches session via /webapp/session; encrypts cardNo + cvv with eNETS RSA scripts client-side/webapp/enets_pay):POST https://www.enets.sg/GW2/uCredit/payPOST /EVSWebPOS/transSumServlet → parseEvsTransactionSummaryparseEnetsResult scrapes the eNETS receipt HTML directlystatus, merchantTxnRef, reason) back to the server-side session/app/result) — React component; reads outcome from server session via /webapp/sessionUses the EVS JSON API and the eNETS Payment Page (enetspp) host directly. This is the primary NUS hostel flow for migrated meters.
/app/cp2nus/loading/cp2nus/webapp/bootstrap) — runBootstrap runs sequentially:isCp2Meter() guard: rejects cp2 meters with a WRONG_SYSTEM error; on network failure the check is skipped and flow proceedsPOST /enets/init_pay → { txn_identifier, req, sign }getMeterSummary → buildPayDisplayAddressbuildEnetsPayUrl → GET enetspp/pay?p=… → extract txnReq, keyId, hmacPOST /GW2/TxnReqListener → RSA key, netsTxnRef, netsMid, paymtNetsMid, txnRand, keyId, hmac/app/cp2nus/pay) — same RSA encryption; paymtNetsMid (acquiring MID) used in panSubmitForm, not top-level netsMid/cp2nus/webapp/enets_pay):GET /GW2/pluginpages/env.jsp → seed JSESSIONIDPOST /GW2/credit/init;jsessionid=…POST /GW2/credit/panSubmitFormnetsTxnStatus in response → preParsed result (no b2s call)POST /enets/b2s → 303 redirect → parsePayResult base64-decodes params/app/cp2nus/result) — reads outcome from server sessionUses the SUTD EVS WebPOS pages and the SUTD credit payment bridge.
/app/sutd/loading/sutd/webapp/bootstrap) — runs the SUTD WebPOS flow:POST /EVSSUTDWebPOS/loginServlet with the meter IDPOST /EVSSUTDWebPOS/selectOfferServlet with the selected amountGET /EVSSUTDWebPOS/paymentServlet → extract merchant_txn_refPOST http://120.50.44.233/payment_sutd_credit/creditpayment.jspPOST /enets2/PaymentListener.do → extract RSA public key, netsMid, netsTxnRef/app/sutd/pay) — same RSA-encrypted card entry as NUS flows/sutd/webapp/enets_pay) — posts encrypted card data to eNETS, then posts the callback to /EVSSUTDWebPOS/transSumServlet/app/sutd/result) — reads outcome from server session# Install backend dependencies
npm install
npm run build:frontend
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.
# Development (two terminals)
npm run dev # Express backend on :3000 npm run dev:frontend # Vite dev server on :5173
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
Solo se muestra el principio; lee el resto en el repo