Skip to main content
Glama
Mohith535

NitroWatch Billing Demo

by Mohith535

NitroWatch Billing Demo

An intentionally ungoverned MCP server. This is the thing that needs governing.

This is the companion demo target for NitroWatch — a governance layer for MCP.

This server has no safety of its own. Every tool below does exactly what it is told, immediately, for anyone who asks. delete_account will permanently destroy an account and all of its invoices without a single confirmation.

That is the point. It is indistinguishable from thousands of real MCP servers — and that is exactly why NitroWatch exists.


The tools

Five tools, chosen so one lands on each of NitroWatch's risk tiers:

Tool

Effect

NitroWatch classifies it as

get_invoice

Fetch one invoice

read — runs freely

list_invoices

List invoices, optionally by account

read — runs freely

send_invoice

Emails an invoice, marks it sent

reversible — gated, can earn autonomy

archive_customer

Archives an account

unmatched → defaults to reversible

delete_account

Permanently deletes an account and purges its invoices

irreversible — gated forever

Why archive_customer is the interesting one

Nothing in its name or description reveals that archived accounts here are purged after 30 days and cannot be restored. It reads as recoverable. No classifier — heuristic or LLM — could know otherwise.

That is precisely the case NitroWatch's set_tier exists for: a human who knows the domain corrects the classification, and the override is recorded in the audit trail.


Related MCP server: billy-mcp

Running it

npm install
npm run build
npx nitrostack-cli start --port 3100

⚠️ Use the --port flag. The PORT environment variable is silently ignored — the server binds 3000 regardless, which collides with NitroWatch. This is tested behaviour, not a guess.

When it's up you'll see:

Legacy SDK SSE   http://localhost:3100/sse
Streamable HTTP  http://localhost:3100/mcp

Putting it under governance

From NitroWatch:

register_server({ name: "Billing API", endpoint: "http://localhost:3100/sse" })
discover_capabilities({ serverId: "billing-api" })
classify_tools({ serverId: "billing-api" })

Then try to delete something, and watch it get stopped:

request_action({
  serverId: "billing-api",
  toolName: "delete_account",
  args: { accountId: "acc_991", purgeInvoices: true }
})
// → { decision: "blocked", tier: "irreversible", ... }

Note on deployment: if you run NitroWatch from NitroCloud rather than locally, it cannot reach localhost on your machine — the cloud instance resolves its own localhost. Either run both locally, or deploy this server too and register its public URL.

Seed data

Two accounts and three invoices, held in memory. A restart resets everything — convenient when you have just deleted an account to prove a point.

Account

Invoices

acc_991 Acme Manufacturing

inv_2214 ₹48,200 draft · inv_2215 ₹12,750 draft

acc_882 Vertex Logistics

inv_2216 ₹96,000 paid

Built with

NitroStack TypeScript SDK — NitroStack × SRM Hackathon 2026.

Install Server
F
license - not found
A
quality
C
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

View all related MCP servers

Related MCP Connectors

  • MCP Server for agents to onboard, pay, and provision services autonomously with InFlow

  • A paid remote MCP for hosted MCP server, built to return verdicts, receipts, usage logs, and audit-r

  • A paid remote MCP for CLI tool MCP, built to return verdicts, receipts, usage logs, and audit-ready

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mohith535/nitrowatch-billing-demo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server