mcpField
S
Statistical Process Control & Anomaly Alerts

Statistical Process Control & Anomaly Alerts

Remote
saifs.aiOther4Updated today

About Statistical Process Control & Anomaly Alerts

An MCP server for statistical monitoring of metric streams, intended for teams tracking quality, reliability, or service performance. It combines Shewhart charts and run rules with CUSUM and EWMA to detect both rule violations and small sustained shifts; decisions remain with operators.

Key features

  1. 01Shewhart control charts
  2. 02Western Electric and Nelson rules
  3. 03CUSUM and EWMA drift detection
  4. 04Control limits from a stable baseline
  5. 05Signal explanations
  6. 06Continuous monitoring and alerts

Use cases

  1. 01Monitor defect rates for process shifts
  2. 02Track support response times against control rules
  3. 03Alert on sustained small metric drifts
  4. 04Review which rule triggered an out-of-control signal

MCP support

Exposes process-monitoring and alert tools to MCP clients over Streamable HTTP. OAuth 2.1 is used for client sign-in.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://process-monitor-mcp-microsoft.saifs.ai/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

Statistical Process Control & Anomaly Alerts

Continuous statistical monitoring of any metric stream — support response time, error rates, delivery SLAs, defect rates, conversion — alerting only on genuine out-of-control signals. Shewhart charts plus Western Electric / Nelson run rules, with CUSUM and EWMA for small sustained drifts that a 3σ chart misses. Decision support only; operators own stop/go.

Registry nameai.saifs/process-control
Endpointhttps://process-monitor-mcp-microsoft.saifs.ai/mcp
TransportStreamable HTTP (remote, nothing to install)
AuthOAuth 2.1 — PKCE (S256) and dynamic client registration; your client opens a sign-in page on first use
PublisherSAIFS AI

Install

VS Code / GitHub Copilot

Add to .vscode/mcp.json (workspace) or your user mcp.json:

{
  "servers": {
    "saifs-process-control": {
      "type": "http",
      "url": "https://process-monitor-mcp-microsoft.saifs.ai/mcp"
    }
  }
}

Then start the server from the MCP view and sign in when prompted.

Claude (claude.ai, Desktop)

Settings → Connectors → Add custom connector, and paste:

https://process-monitor-mcp-microsoft.saifs.ai/mcp
Claude Code
claude mcp add --transport http saifs-process-control https://process-monitor-mcp-microsoft.saifs.ai/mcp
Any other MCP client

Point it at https://process-monitor-mcp-microsoft.saifs.ai/mcp using the Streamable HTTP transport. The server returns 401 with a WWW-Authenticate: Bearer … resource_metadata=… challenge, so OAuth-aware clients sign in automatically.

Tools

ToolWhat it does
detect_shiftCUSUM / EWMA for small sustained drifts that Shewhart charts miss.
explain_signalWhich rule fired, how many sigma, and what it means.
monitor_metricIn-control / out-of-control verdict plus which rule fired.
set_control_limitsCompute ±3σ limits from a stable baseline.
watch_processContinuous watch; alert on rule violations.

Example prompts

  • “Is line 3 drifting out of spec?”
  • “Alert me when defect rate shifts”
  • “Calculate Cpk for this process”

Support

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.