app.businys/mcp-server
app.businys/mcp-server
Is the app.businys/mcp-server MCP server down? Yes. It has given no valid answer since 2026-10-17: install failed.
221 MCP tools across 26 practices for independent professionals. Clients, invoices, contracts.
install failed down since 2026-10-17 · probed 2026-11-15 · unchanged since 2026-10-31
npm error code EUNSUPPORTEDPROTOCOL npm error Unsupported URL Type "workspace:": workspace:* npm error A complete log of this run can be found in: /root/.npm/_l
- Run it
- npx -y @businys/mcp-server@1.0.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/hiatys/businys-mcp
- Registry
- active, updated 2026-04-02 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Call Grok Bot ai.zens/call-grokbot · needs env
- ZenBrain Memory ai.zensation/zenbrain · crashed on start
- Zils ai.zils/zils · crashed on start
- app.3dstreet/3dstreet · alive
- app.cloudmindmaps/mindmaps · alive
- app.crawlio/crawlio-browser · alive
- DataRunner app.datarunner/datarunner · alive
- devglow app.devglow/devglow · alive
Servers that mention professionals or independent.
- B4 Index ai.benroberts/b4-index · alive
- GroundTruth — subsurface scan QA & trade estimating ai.gtfi/groundtruth · alive
- Fidenta Verify ai.noevant/fidenta-verify · alive
- TutorPing ai.tutorping/tutorping · alive
- VulX Watch ai.vulx/watch · needs auth
- Scope (Claims) - Preview bid.scope/claims · needs auth
- Scope (Legal) bid.scope/legal · needs auth
- Vitena Directory care.vitena/directory · alive
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-17, 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.