MCP Uptime Kuma vs Qtcl MCP Server
A side-by-side look at the MCP Uptime Kuma and Qtcl MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Uptime Kuma for monitoring work as a local process; choose Qtcl MCP Server for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Uptime Kuma when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME, UPTIME_KUMA_PASSWORD, UPTIME_KUMA_2FA_TOKEN, UPTIME_KUMA_JWT_TOKEN, UPTIME_KUMA_HEADERS. - You want tools like
getMonitorSummary, listMonitors, listMonitorTypes.
Choose Qtcl MCP Server when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
qtcl_create_wallet, qtcl_get_balance, qtcl_send_transaction.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 60/100 · Good | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | UPTIME_KUMA_URLUPTIME_KUMA_USERNAMEUPTIME_KUMA_PASSWORDUPTIME_KUMA_2FA_TOKENUPTIME_KUMA_JWT_TOKENUPTIME_KUMA_HEADERS | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 55 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 26 | 11 |
| Full listing | View MCP Uptime Kuma | View Qtcl MCP Server |
Tools & capabilities
MCP Uptime Kuma tools 26
getMonitorSummaryGet a quick overview of all monitors with their current status. Supports filtering.listMonitorsGet the full list of all monitors with configurations. Supports filtering.listMonitorTypesGet all available monitor types supported by Uptime Kuma.getMonitorGet detailed configuration for a specific monitor by ID.createMonitorCreate a new monitor (requires name and type at minimum).updateMonitorUpdate an existing monitor's configuration.deleteMonitorPermanently delete a monitor and all its heartbeat history.pauseMonitorPause a monitor to stop performing checks.resumeMonitorResume a paused monitor to restart checks.listHeartbeatsGet status check history for all monitors.getHeartbeatsGet status check history for a specific monitor.listNotificationsList all configured notification channels (Slack, Discord, email, webhooks, etc.).- +14 more on the listing page
Qtcl MCP Server tools 11
qtcl_create_walletGenerate a new post-quantum wallet address + keypairqtcl_get_balanceCheck confirmed + pending balance for any addressqtcl_send_transactionSend QTCL with flat 1-qsat fee. Supports 256-char memoqtcl_get_transactionLook up any transaction by hashqtcl_get_chain_infoBlock height, mempool depth, oracle consensus statusqtcl_get_blockBlock by height or hash with quantum coherence metricsqtcl_get_recent_transactionsLast 50 txs, filterable by addressqtcl_get_quantum_metricsLive W-state fidelity, entanglement witness, lattice coherenceqtcl_get_oracle_registry5 Byzantine consensus oracles — stake, uptime, heartbeatqtcl_get_peersActive P2P peers and topology dataqtcl_get_priceLive QTCL/USD from Pyth Network oracle feed
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Uptime Kuma
{
"mcpServers": {
"mcp-uptime-kuma": {
"command": "npx",
"args": [
"-y",
"-p",
"@davidfuchs/mcp-uptime-kuma",
"mcp-uptime-kuma-get-jwt"
],
"env": {
"UPTIME_KUMA_URL": "YOUR_UPTIME_KUMA_URL_HERE",
"UPTIME_KUMA_USERNAME": "YOUR_UPTIME_KUMA_USERNAME_HERE",
"UPTIME_KUMA_PASSWORD": "YOUR_UPTIME_KUMA_PASSWORD_HERE",
"UPTIME_KUMA_2FA_TOKEN": "YOUR_UPTIME_KUMA_2FA_TOKEN_HERE",
"UPTIME_KUMA_JWT_TOKEN": "YOUR_UPTIME_KUMA_JWT_TOKEN_HERE",
"UPTIME_KUMA_HEADERS": "YOUR_UPTIME_KUMA_HEADERS_HERE"
}
}
}
}
Qtcl MCP Server
{
"mcpServers": {
"qtcl-mcp-server": {
"url": "https://qtcl-blockchain.koyeb.app/mcp/sse"
}
}
}
Frequently asked questions
MCP Uptime Kuma is categorized under Monitoring and uses a local stdio subprocess. Qtcl MCP Server belongs to Monitoring and uses a remote HTTP/SSE transport. Pick MCP Uptime Kuma for monitoring work and Qtcl MCP Server for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Uptime Kuma has no declared pricing — check the project's own site. Qtcl MCP Server has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-uptime-kuma and qtcl-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Uptime Kuma has a quality signal of 60/100 (Good) with 1 views, 0 installs and 55 GitHub stars. Qtcl MCP Server has 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.