LeashIndex Get the report

Index / devtools

io.github.barangaroo/crosstabs

io-github-barangaroo-crosstabs declares 39 capabilities across 39 tools, with 2 critical issues.

90/100 exposureHigh exposure

Manifest recorded 2026-10-15 from tools/list answered by the PyPI package crosstabs==1.1.4 (published to PyPI as crosstabs, listed in the official MCP registry as io.github.barangaroo/crosstabs 1.1.4), run in an isolated container with no network access and no credentials. The date changes only when the manifest does. Not verified by a maintainer.

Note. Installed with the MCP Python SDK held below version 2.0. With the newest SDK this version of the package stopped before it could list its tools.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 39 tools

39 of 39 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 1 of 39 tools

1 tool is classified as irreversible and declares no limit.

high · no-expiry · All 39 tools

39 of 39 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 39 tools

39 of 39 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 34 of 39 tools

34 tools can modify data and declare no limit.

low · uncapped-read · 4 of 39 tools

4 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
chi_square_testwrite assumed
fishers_exactwrite assumed
mcnemar_testwrite assumed
g_testwrite assumed
odds_ratioread inferred
relative_riskread inferred
risk_differencewrite assumed
cramers_vwrite assumed
phi_coefficientwrite assumed
spearmans_rhowrite assumed
kendalls_tauwrite assumed
goodman_kruskal_gammawrite assumed
cohens_kappawrite assumed
weighted_kappawrite assumed
cmh_testwrite assumed
linear_trend_testwrite assumed
power_analysiswrite assumed
bonferroni_correctionwrite assumed
fdr_correctionwrite assumed
standardized_residualswrite assumed
post_hoc_chi_squaresend inferred
proportion_ciwrite assumed
mosaic_plot_datawrite assumed
stacked_bar_datawrite assumed
check_assumptionsread inferred
recommend_testwrite assumed
crosstab_from_datawrite assumed
crosstab_from_csvwrite assumed
somers_dwrite assumed
tau_cwrite assumed
lambda_coefficientwrite assumed
uncertainty_coefficientwrite assumed
breslow_day_testwrite assumed
monte_carlo_chi_squarewrite assumed
correspondence_analysiswrite assumed
chi_square_yateswrite assumed
attributable_riskread inferred
detect_outlierswrite assumed
effect_sizewrite assumed
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.