mcpField
W
WhiteBoxXAI

WhiteBoxXAI

Remote
whiteboxxai.comData & Analytics0Updated 1d ago

About WhiteBoxXAI

WhiteBoxXAI is an AI observability, explainability, and governance service for MCP clients, covering models, predictions, drift, fairness, compliance, LLMs, and RAG. It offers tools across 18 domains and supports interactive audit cards.

Key features

  1. 01Model registry and Git diffs
  2. 02Prediction logs and drift detection
  3. 03Bias and fairness audits
  4. 04ISO/IEC 42001 compliance evidence
  5. 05LLM, RAG, and safety monitoring
  6. 06Alerts and multi-agent workflow tracking

Use cases

  1. 01Inspect model changes, performance, and drift
  2. 02Audit model bias, fairness, and compliance readiness
  3. 03Analyze LLM call costs, latency, and explanations
  4. 04Monitor RAG, content safety, and alerts

MCP support

It exposes tools across 18 domains to MCP-compatible clients over stdio and Streamable HTTP. MCP Apps resources support interactive audit cards.

Configuration

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

Endpointhttps://api.whiteboxxai.com/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.

All endpoints
Streamable HTTPhttps://api.whiteboxxai.com/mcp/Auth required
Packages
pypiwhiteboxxai-mcp0.3.2

Tools

Details

From the project 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.

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.