hypothesis_test
Run a statistical significance test and get the statistic, p-value, effect size, confidence interval and a plain-English verdict — results match scipy.stats. Tests: Welch / Student two-sample t, paired t, one-sample t, one-proportion z, A/B test of two conversion rates (pooled z, lift, CI of the ...
This record as markdown: /tools/com-it-scorptech-x402/hypothesis-test.md
What hypothesis_test does on ScorpTech x402 API
AI agents call hypothesis_test to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
a | array | — | Sample A (or x for correlations, or the differences for wilcoxon) |
b | array | — | Sample B (or y) |
mu | number | — | Hypothesised mean (one-sample t) |
p0 | number | — | |
test | string | Yes | |
alpha | number | — | |
table | array | — | Contingency table (rows of counts) for chi-square-independence / fisher-exact (2×2) |
yates | boolean | — | chi-square-independence: Yates continuity correction for 2×2 tables |
groups | array | — | anova / kruskal-wallis: array of samples, or an object of named samples |
trials | integer | — | |
trialsA | integer | — | |
trialsB | integer | — |
Parameters from the server's own tool schema.
Why hypothesis_test is rated Low
Even though hypothesis_test only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (19 properties)
Attacks that exploit this kind of access
The rule that runs hypothesis_test safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hypothesis_test, this is the rule to start with:
hypothesis_test is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every hypothesis_test call is checked against it from then on.
Questions about hypothesis_test
Run a statistical significance test and get the statistic, p-value, effect size, confidence interval and a plain-English verdict — results match scipy.stats. Tests: Welch / Student two-sample t, paired t, one-sample t, one-proportion z, A/B test of two conversion rates (pooled z, lift, CI of the difference), chi-square goodness of fit and independence (Yates for 2×2, Cramér's V), one-way ANOVA (η²), Kruskal–Wallis, Mann–Whitney U (exact for small samples, rank-biserial r), Wilcoxon signed-rank (exact / permutation / normal), Pearson and Spearman correlation (Fisher-z CI) and Fisher's exact test. Two-sided or one-sided alternatives. Price: $0.003 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/hypothesis-test. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
hypothesis_test accepts 12 parameters: a, b, mu, p0, test, alpha, table, yates, groups, trials, trialsA, trialsB. Required: test. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for hypothesis_test: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches ScorpTech x402 API. Nothing to install.
hypothesis_test is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hypothesis_test rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for hypothesis_test. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
hypothesis_test is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue