Back to Browse

Whiteboxxai MCP Server

Developer ToolsModerate5.4MCP RegistryLocalRemote
Free

Server data from the Official MCP Registry

AI observability, explainability and governance: drift, fairness, ISO 42001, risk register.

About

AI observability, explainability and governance: drift, fairness, ISO 42001, risk register.

Remote endpoints: streamable-http: https://api.whiteboxxai.com/mcp/

Security Report

5.4
Moderate5.4Moderate Risk

The WhiteBoxXAI MCP server requires an API key via environment variable for stdio and a bearer token for hosted HTTP, with no hardcoded credentials in the visible code. The visible UI widget code uses a strict CSP, escapes HTML output, and routes actions through the authenticated MCP host, and the network access shown matches its stated observability purpose. The visible code is truncated, so the tool implementations, the rest of the HTML widget, and the asgi.py/HTTP auth handling were not reviewed, which limits confidence in the score. Supply chain analysis found 11 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.

4 files analyzed · 18 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

system_info

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

WhiteBoxXAI API key, generated from the dashboard under Settings > API Keys.Required

Environment variable: WHITEBOXXAI_MCP_API_KEY

Base URL of your WhiteBoxXAI instance.Optional

Environment variable: WHITEBOXXAI_MCP_API_BASE_URL

How to Install & Connect

Available as Local & Remote

This plugin can run on your machine or connect to a hosted endpoint. during install.

Documentation

View on GitHub

From the project's GitHub README.

whiteboxxai-mcp

PyPI version Python versions Test License: MIT

An MCP (Model Context Protocol) server that exposes WhiteBoxXAI observability and explainability capabilities — model registry, Git-backed model diffing, prediction logging, drift detection, bias/fairness auditing, ISO/IEC 42001 readiness and compliance evidence, AI Risk Register / governance review queries, prompt governance, asynchronous SHAP/LIME explanation generation, LLM explainability (attention/token-importance/sensitivity/counterfactual analysis and prompt debugging), LLM call monitoring (token/cost/latency tracking), RAG pipeline monitoring, content safety analysis, alert rules and triage context, alert intelligence, alert management, multi-agent workflow tracking, and model performance metrics (197 tools across 18 domains) — to any MCP-compatible client (Claude Desktop, Claude Code, LangChain, custom agent harnesses, etc.). Supports MCP Apps (ui:// resources) with sandboxed interactive audit cards, stdio transport, and Streamable HTTP transport (hosted at https://api.whiteboxxai.com/mcp/).

See the integration docs for full setup, connection examples, the tool reference, and known v1 limitations. See examples/ for runnable LangChain, Semantic Kernel, and raw-MCP-client integrations.

Install

pip install whiteboxxai-mcp

Run (stdio — local/self-hosted)

Configure a credential via environment variables, then run the console script. Stdio transport authenticates via WHITEBOXXAI_MCP_API_KEY:

# An API key generated from the WhiteBoxXAI dashboard's Settings > API Keys tab.
# Never expires on a fixed schedule -- only when explicitly revoked -- and doesn't require storing a password.
export WHITEBOXXAI_MCP_API_BASE_URL="https://api.whiteboxxai.com"
export WHITEBOXXAI_MCP_API_KEY="wbx_live_..."

whiteboxxai-mcp

Point your MCP client at this command (e.g. in Claude Desktop's mcpServers config, or Claude Code's .mcp.json).

For hosted Streamable HTTP (https://api.whiteboxxai.com/mcp/), pass your API key or personal JWT in the Authorization: Bearer <token> header.

Agent skills

To have a coding agent set this up and call the tools correctly, give it the whitebox-mcp-server skill (and whitebox-governance-rules). They are published at https://whiteboxxai.com/skills/index.md. The tool list they reference is pinned in tests/mcp_inspector_snapshot.json; a rename or removal of a tool shows up as a diff there.

Versioning & support

This package follows Semantic Versioning; see CHANGELOG.md for release history. Self-hosted stdio usage (above) is best-effort supported; the hosted /mcp/ HTTP endpoint is a product surface whose support/SLA follows the caller's underlying Free/Business Cloud plan.

Known v1 limitations

  • Auth: stdio uses WHITEBOXXAI_MCP_API_KEY — a scoped, revocable credential that isn't tied to a human account's password or session lifecycle. Hosted Streamable HTTP (https://api.whiteboxxai.com/mcp/) accepts an API key or personal JWT.
  • Alerts: covers core alert rules and triage context (whitebox_alerts_*), alert intelligence (whitebox_alert_intelligence_*, 20 tools), and alert management (whitebox_alert_management_*, 13 tools).
  • whitebox_agent_workflows_cost_breakdown/_bottlenecks/_timeline: these three can take up to ~30s — the backend blocks server-side on a Celery task before responding, and the SDK client uses an extended (40s) timeout for exactly these calls.
  • Scope: models, predictions, drift, bias/fairness, AI Risk Register / governance queries, prompts, compliance, explanations, LLM explainability, LLM call monitoring, RAG monitoring, content safety, alert intelligence, alert management, multi-agent workflows, and metrics all ship across 18 domains (197 tools total) over both stdio and hosted Streamable HTTP.

MCP Registry

The server is published to the official MCP Registry as io.github.AgentaFlow/whiteboxxai-mcp.

Development

pip install -e ".[dev]"
pytest tests/unit

# MCP Inspector tool-list regression check (needs Node.js); after an intentional
# tool change, regenerate the committed snapshot with --write
python tests/check_mcp_inspector_snapshot.py

Releases are cut from GitHub releases; see RELEASING.md.

License

MIT -- see LICENSE.

Reviews

No reviews yet

Be the first to review this server!