io.github.jkapadia-techsterllc/lumis
Lumis
Is the Lumis MCP server down? No. It is up and needs network, probed 2026-10-26.
Life sciences CRM migration intelligence for module mapping, compliance, and validation.
needs network probed 2026-11-15 · unchanged since 2026-10-26
MCP error -32000: Connection closed FileNotFoundError: [Errno 2] No such file or directory: '/work/uv/lumis-mcp/lib/python3.12/site-packages/lumis_mcp/_server_s
- Run it
- uvx lumis-mcp@1.0.1 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/jkapadia-techsterllc/lumis-mcp
- Registry
- active, updated 2026-10-25 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- jev-ultrafast-mcp io.github.jiawei686/jev-ultrafast-mcp · alive
- MySQL Audit io.github.jimmyjan0824/mysql-audit · alive
- io.github.jinsim/f1verse · alive
- optlens io.github.jjd-lab/optlens · crashed on start
- IAMF Sentinel io.github.jlivingston-Cipher/iamf-sentinel-mcp · alive
- io.github.jlucasmcrell/apify-scrapers · alive
- Kindex io.github.jmcentire/kindex · crashed on start
- Andorra public sources io.github.joalavedra/andorra-fonts-publiques · alive
Servers that mention intelligence or compliance.
- Agentic News ai.agentic-news/mcp · needs auth
- ai.agentberg/agentberg · alive
- ai.astrofabric/mcp · not found
- ai.bassethound/bassethound · needs auth
- BlueNexus Universal MCP ai.bluenexus/universal-mcp · needs auth
- Bezal — Local Business Intelligence for AI Agents ai.bezal/local-commerce · alive
- BidDeed MCP ai.biddeed/biddeed-mcp · needs auth
- China Marketing AI Intelligence MCP ai.chinamarketing/intelligence · needs auth
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
- The server tries to reach the network on start. The probe runs in a container with the network off, so a server that connects lazily, on the first tool call, is measured.