whiteboxxai-mcp
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.
Metadata
Release files for whiteboxxai-mcp 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| whiteboxxai_mcp-0.3.0.tar.gz | 122.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| whiteboxxai_mcp-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 194.2 kB
Release files / whiteboxxai_mcp-0.3.0.tar.gz
| Download URL | whiteboxxai_mcp-0.3.0.tar.gz |
|---|---|
| Size | 122.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
131bd519ad254d4bbfc03bc7070ca2e2526812b4f8fc4404dcba2dcafcc0d35c
|
|
BLAKE2b-256 checksum How to use checksums |
d7cf931fe1d9f0b9fca1945c654d390d8eb92f4552e64bb337b6aa5c6d815373
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / whiteboxxai_mcp-0.3.0-py3-none-any.whl
| Download URL | whiteboxxai_mcp-0.3.0-py3-none-any.whl |
|---|---|
| Size | 72.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
074246b11861d5a68b2abfe094aa5d51d13b917275ea59f2e804ebd0680351b0
|
|
BLAKE2b-256 checksum How to use checksums |
0cefb8b65a53cb680fecaf17324f7175e56d75fb21ae38bff64e785c98b6ba58
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logSecurity for whiteboxxai-mcp 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for whiteboxxai_mcp-0.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.