Developer · Remote MCP server
Xplainable MCP Server
Train, explain, optimise and deploy transparent glass-box ML models via workflow tools.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.xplainable/xplainable-mcp-server- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-19
- Updated
- 2026-08-19
- Publisher
- xplainable (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/xplainable) · how
- Repository
- github.com/xplainable/xplainable-mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.xplainable.io/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Xplainable MCP Server
Xplainable MCP Server is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.xplainable.io/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| XitoringConnect AI assistants to Xitoring monitoring: servers, uptime, incidents, metrics, SSL, and alerts. | Remote · HTTPLive check: sign-in required |
| xmp4 - Semantic code knowledge for your stackOSS libs in your stack, really used: source, tests, callers. C#, Java, TS, Python, Rust, PHP+. | Remote · HTTPLive check: ✓ handshake |
| xOmniMarketSearch AI capabilities across AWS Marketplace and the Official MCP Registry. | Remote · HTTPLive check: ✓ handshake |
| xpay DevTools30+ dev tools. Context7, Code Runner, Python Execute, Code Sentinel, NPM Sentinel, PlantUML. | Remote · HTTP |
| XploitScanSecurity scanner for AI-generated code. 30 free rules; all 214 with a paid-plan API key. | Local · stdio |
| xytara MCP ExecutorPublic MCP server for summaries, DNS lookup, catalog, replies, and JSON checks. | Remote · HTTPLive check: ✓ handshake |
| YAACMessaging between concurrent AI coding sessions, across clients, over MCP. Zero infrastructure. | Local · stdio |
| Yaml Ai MCPAI-powered yaml ai MCP server for agents. Supports validate yaml, convert yaml json, lint yaml. By. | Local · stdio |