io.github.barangaroo/crosstabs-mcp
io.github.barangaroo/crosstabs-mcp
Is the io.github.barangaroo/crosstabs-mcp MCP server down? Yes. It has given no valid answer since 2026-10-16: not found.
Statistical crosstab analysis: chi-square, Fisher's exact, odds ratio, effect sizes
not found down since 2026-10-16 · probed 2026-11-14 · unchanged since 2026-10-29
error: No solution found when resolving dependencies cause: Because there is no version of crosstabs-mcp==1.0.0 and you require crosstabs-mcp==1.0.0, we can c
- Run it
- uvx crosstabs-mcp@1.0.0 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/barangaroo/crosstabs-lite
- Registry
- deprecated, updated 2026-10-28 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- Beget Hosting io.github.badigit/beget-mcp · alive
- OwnMetrics io.github.badisbenhamida/ownmetrics-mcp · alive
- ask-fable io.github.baggybin/ask-fable · alive
- io.github.barangaroo/crosstabs · needs mcp<2
- io.github.barateza/mcp-plesk-dev-docs · crashed on start
- io.github.base76-research-lab/cognos-session-memory · crashed on start
- io.github.base76-research-lab/conductor-graph-mcp · crashed on start
- io.github.base76-research-lab/token-compressor · needs env
Servers that mention crosstabs.
- Likerts io.github.crosstabs/likerts · needs your URL
- io.github.crosstabs/crosstabs · alive
- Talk2Data InsightGenius io.github.quack2025/talk2data-insightgenius · needs your URL
- SurveyCoder io.github.quack2025/surveycoder · 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-16, 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.