io.github.dataraum/dataraum
DataRaum
Is the DataRaum MCP server down? Yes. It has given no valid answer since 2026-10-17: not found.
Pre-computed metadata context engine for AI-driven data analytics
not found down since 2026-10-17 · probed 2026-11-14 · unchanged since 2026-10-31
error: No solution found when resolving dependencies cause: Because dataraum was not found in the package registry and you require dataraum==0.2.1, we can con
- Run it
- uvx dataraum@0.2.1 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/dataraum/dataraum
- Registry
- active, updated 2026-04-17 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- yt-mem-ai io.github.dasein108/yt-mem-ai · crashed on start
- io.github.dashpilot-labs/dashpilot-mcp · needs env
- DataCharter io.github.datacharter/datacharter · needs args
- io.github.datalattice/mcp-chainladder · needs mcp<2
- IterableData io.github.datenoio/iterabledata · crashed on start
- Datris io.github.datris/datris · alive
- Datumline Agent Guard io.github.datumline/agent-guard · alive
- RCA-MCP io.github.dave1362/rca-mcp-connector · alive
Servers that mention analytics or computed.
- JustIdea Agency agency.justidea/justidea-agency · alive
- Alpic ai.alpic.mcp/alpic-mcp · needs auth
- Analytics Legends — SAP AI & Analytics MCP Server ai.analyticslegends/sap-analytics · alive
- AutoRFP.ai ai.autorfp/mcp · needs auth
- AwrAIter — Telegram channels ai.awraiter/telegram · needs auth
- Web Analytics ai.b77/web-analytics · needs auth
- BAMF.ai ai.bamf/bamf · not MCP
- Eevy ai.eevy/mcp · 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
- No valid answer since 2026-10-17, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.