NitroWatch Billing Demo
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@NitroWatch Billing Demo send invoice inv_2215 to the customer"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 |
| Fetch one invoice |
|
| List invoices, optionally by account |
|
| Emails an invoice, marks it sent |
|
| Archives an account | unmatched → defaults to |
| Permanently deletes an account and purges its invoices |
|
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: mcp-trust-demo
Running it
npm install
npm run build
npx nitrostack-cli start --port 3100⚠️ Use the
--portflag. ThePORTenvironment 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/mcpPutting 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
localhoston 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 |
|
|
|
|
Built with
NitroStack TypeScript SDK — NitroStack × SRM Hackathon 2026.
Available Tools
5 toolsarchive_customerA
Archive a customer account so it no longer appears in active listings
Inputs: accountId (required).
delete_accountA
Permanently delete a customer account and all associated invoices. Cannot be undone.
Inputs: accountId (required), purgeInvoices.
get_invoiceA
Fetch a single invoice by id
Inputs: invoiceId (required).
list_invoicesA
List all invoices, optionally filtered by account
Inputs: account.
send_invoiceB
Email an invoice to the customer. Can be voided and re-sent.
Inputs: invoiceId (required), email.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool targets a distinct resource and action: get_invoice retrieves a single invoice, list_invoices retrieves multiple, send_invoice emails an invoice, and archive_customer vs delete_account clearly separate soft from permanent customer removal. No two tools overlap in purpose.
All tool names follow a consistent verb_noun pattern (get/list/send/archive/delete + resource). The use of 'get' for singular and 'list' for plural is conventional, and there is no mixing of styles.
With 5 tools, the server is well-scoped for a billing demo. It covers the essential operations without unnecessary bloat, and the count feels appropriate for its purpose.
The set covers invoice retrieval, emailing, and customer lifecycle (archive/delete), but lacks invoice creation, updating, or voiding. This is a minor gap for a billing system, but core workflows are still represented.
Maintenance
Related MCP Connectors
Demo banking MCP server: accounts, transactions and payments. OAuth 2.1 with DPoP.
MCP server for Codat — companies, connections, invoices, bills and financial statements.
MCP server for Quaderno — tax-rate calculation, invoices, contacts, products, receipts & expenses.
MCP server for Autumn — read customers, plans, balances & invoices; track usage and attach plans.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceDemo MCP server that exposes order and customer data as read-only tools for AI assistants, simulating a business API or internal data source.-
- FlicenseNot gradedqualityDmaintenanceAn intentionally vulnerable MCP server designed as a live demo target for the MCP Trust security scanner. It contains deliberate insecure patterns to demonstrate scanning capabilities.-
- AlicenseNot gradedqualityBmaintenanceMCP server for Askell's payment and subscription API, allowing users to discover API operations, make raw API calls with approval for mutations, and analyze customers, contracts, billing runs, and webhooks.257 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to generate audit reports and query financial ledger data via MCP. This demo version contains intentional security vulnerabilities for security testing and should not be used in production.-