Connect AI assistants to Xitoring monitoring: servers, uptime, incidents, metrics, SSL, and alerts.
Connect AI assistants like Claude, Cursor, and ChatGPT to your Xitoring monitoring data. The Xitoring MCP server is a hosted, remote HTTP server - there is nothing to install or run locally. Point your MCP-compatible client at with your Xitoring API key and you're done. Xitoring is an all-in-one monitoring platform: uptime checks (HTTP, TCP, DNS, ICMP), server monitoring via the Xitogent agent…
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Connect AI assistants like Claude, Cursor, and ChatGPT to your Xitoring monitoring data. The Xitoring MCP server is a hosted, remote HTTP server - there is nothing to install or run locally. Point your MCP-compatible client at with your Xitoring API key and you're done. Xitoring is an all-in-one monitoring platform: uptime checks (HTTP, TCP, DNS, ICMP), server monitoring via the Xitogent agent (CPU, memory, disk, network, processes), SSL expiry, heartbeat checks, incident management, status…
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.