io.github.lightnet19/lightbill-mcp-server
io.github.lightnet19/lightbill-mcp-server
Is the io.github.lightnet19/lightbill-mcp-server MCP server down? Yes. It has given no valid answer since 2026-10-16: install failed.
LightBill ISP billing MCP server: 134 tools (customers, routers, OLT, invoices, payment).
install failed down since 2026-10-16 · probed 2026-11-14 · unchanged since 2026-10-30
error: Failed to install entrypoints for `lightbill-mcp-server`
- Run it
- uvx lightbill-mcp-server@0.1.1 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Registry
- active, updated 2026-08-07 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- io.github.les-k/pg-readonly-mcp · needs env
- io.github.les-k/sweep-mcp · needs args
- pgbrake io.github.lexang/pgbrake · alive
- KeyShot io.github.lfoletti/keyshot-mcp · alive
- io.github.lightnet19/pddikti-mcp-server · install failed
- io.github.lightnet19/sinta-mcp-server · install failed
- io.github.lightnet19/stb-mcp-server · install failed
- LightNow MCP Proxy io.github.lightnow-ai/lightnow-proxy · needs args
Servers that mention customers or invoices.
- Atalay ai.atalay/mcp · needs auth
- DeepLedger QuickBooks MCP Server for ChatGPT, Claude & AI ai.deepledger/mcp · needs auth
- ai.diezx/diezx · no DNS
- Doklad.ai ai.doklad/mcp · needs auth
- Dynt ai.dynt.api/dynt · needs auth
- Ekwo OS — open source accounting: ledger, invoices and VAT on your own Supabase or Postgres ai.ekwo/mcp · needs auth
- FinStat ai.finstat/finstat · needs auth
- ai.fugentic/fugentic · error
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-16, in every probe since then.
- npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.