io.github.AgentaFlow/whiteboxxai-mcp
WhiteBoxXAI
Is the WhiteBoxXAI MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-15.
AI observability, explainability and governance: drift, fairness, ISO 42001, risk register.
needs auth probed 2026-11-15 · HTTP 401 · Bearer
The server needs auth, so these tool definitions were read from the publisher's open-source package pypi:whiteboxxai-mcp, started in a container with placeholder values and the network off, on 2026-11-15. Tool definitions do not depend on the token, so this is what an authorized user loads, unless the server hides tools by plan or role.
Streamable HTTP error: Error POSTing to endpoint: {"error":"Unauthorized","detail":"Missing or malformed Authorization header. The WhiteBoxXAI MCP HTTP transpor- Endpoint
- https://api.whiteboxxai.com/mcp/ (streamable-http)
- Host
- api.whiteboxxai.com
- Of a 1M window
- 5.3 % of a 1M context window
- Getting access
- A key or token from the publisher, sent in the Authorization header (Bearer). The server publishes no OAuth metadata. Store the key once: npx mcpcost auth https://api.whiteboxxai.com/mcp/ --header "Authorization: Bearer …".
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/AgentaFlow/whiteboxxai-mcp
- Website
- https://whiteboxxai.com
- Registry
- active, updated 2026-10-27 · registry entry
Compare this server with others.
More servers
Servers that mention explainability or observability.
- AnomalyArmor ai.anomalyarmor/armor-mcp · needs auth
- ai.diezx/diezx · no DNS
- ai.getvda/llm-observability-orchestration · newer protocol
- ai.getvda/llm-observability-orchestration-agent-langchain · newer protocol
- ai.getvda/llm-observability-orchestration-agent-langchain-community · newer protocol
- ai.getvda/llm-orchestration-observability-agent · newer protocol
- ai.noveum/noveum · needs auth
- Mengi Cloud cloud.mengi/mengi-cloud · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.