CursorIDE

Normality Test Engine MCP Server

Bring Statistics
to Cursor

Name: Normality Test Engine MCP Server
Price: 29 USD
Availability: InStock
Rating: 5.0 (1 reviews)
Author: Vinkius

Learn how to connect Normality Test Engine to Cursor and start using 1 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

GDPR Free for Subscribers

Test Normality

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

What is the Normality Test Engine MCP Server?

Before running t-tests, ANOVA, or linear regression, you need to verify that your data is normally distributed. LLMs cannot eyeball a distribution from raw numbers — they will guess and often guess wrong.

This MCP uses simple-statistics to compute exact Skewness and Kurtosis coefficients, then applies a Jarque-Bera test to determine normality. The AI gets a definitive pass/fail verdict with the exact test statistic and p-value.

The Superpowers

Zero Hallucination: Exact statistical coefficients computed locally.
Automated Verdict: Returns a clear 'normal' or 'not normal' interpretation.
Descriptive Statistics: Also provides exact Mean, Std Dev, Skewness, and Kurtosis.
Data Privacy: Your research data stays entirely on your local machine.

Built-in capabilities (1)

test_normality

Perform an exact deterministic Jarque-Bera normality test on numeric data without LLM math hallucinations

Why Cursor?

Cursor's Agent mode turns Normality Test Engine into an in-editor superpower. Ask Cursor to generate code using live data from Normality Test Engine and it fetches, processes, and writes. all in a single agentic loop. 1 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

—
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
—
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
—
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
—
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

See it in action

Normality Test Engine in Cursor

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Why Vinkius

Normality Test Engine and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Normality Test Engine to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready

<40msCold start

60%Token savings

	Raw MCP	Vinkius
Server catalog	Find and host yourself	4,000+ managed
Infrastructure	Self-hosted	Sandboxed V8 isolates
Credential handling	Plaintext in config	Vault + runtime injection
Data loss prevention	None	Configurable DLP policies
Kill switch	None	Global instant shutdown
Financial circuit breakers	None	Per-server limits + alerts
Audit trail	None	Ed25519 signed logs
SIEM log streaming	None	Splunk, Datadog, Webhook
Honeytokens	None	Canary alerts on leak
Custom domains	Not applicable	DNS challenge verified
GDPR compliance	Manual effort	Automated purge + export

Unlock for AI Agents View step-by-step setup guide for Cursor →

Enterprise Security

Why teams choose Vinkius for Normality Test Engine in Cursor

The Normality Test Engine MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 1 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Unlock for AI Agents View full Normality Test Engine details →

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures
Normality Test Engine for Cursor

Every tool call from Cursor to the Normality Test Engine MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start

Ed25519Signed audit chain

60%Token savings

FAQ

Frequently asked questions

Is this the Shapiro-Wilk test?

This engine implements the Jarque-Bera normality test, which uses Skewness and Kurtosis. It is highly effective for medium-to-large samples and avoids the Shapiro-Wilk implementation gaps in JavaScript.

How many data points do I need?

The Jarque-Bera test works best with 30 or more samples. For very small samples (n < 20), consider using visual QQ-plot analysis as a complement.

What does a 'not normal' result mean for my analysis?

If your data is not normally distributed, parametric tests like t-tests and ANOVA may be unreliable. Consider using non-parametric alternatives like Spearman correlation or Mann-Whitney U tests.

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.